If you have an API key, using Opus with a 3rd party UI like typingmind.com solves all of the problems you mentioned (disclaimer: I'm the app developer)
Yes, we have an API and a way of accessing it with a generated API key which you can find in the admin panel.
Two things to note though.
The APIs are intended for serving the Danswer frontend. The functionality is generally complete for similar use cases but it's not documented so you have to look at the code.
If you're overusing the API on the cloud without providing your own OpenAI key, we will likely have to shut down the instance to prevent losing too much on inference fees.
Maybe I'm old, but I can't see any reasons why this is better after looking at the before/after example. This is adding unnecessary complexity with very little benefit (if at all).
If anything, the "try...catch" example actually look clearer and better than "!user.ok".
I see that you already submitted this story yourself but, unfortunately, didn't get much traction like this one. This is one of the weirdest parts of Hacker News, where a submission may go totally unnoticed but could go viral and even hit #1 after being resubmitted a few hours later.
Hi, it's Tony here. Sorry about the experience with support.
I remember this issue, it's about making the screenshot background transparent without getting the drop shadow getting cut off, right?
The app is not designed well for using with transparent background. So if you prefer transparent background, it's best to make the shadow smaller, or remove the shadow completely, or… increase the padding.
I considered to supporting this but in the end I removed the ticket out of the backlog because I didn't want to turn Xnapper into a photo editor, sorry!
If this isn't about the transparent background, can you send me another email to support? I’ll take a look, thanks for using Xnapper! :)
It's not related to transparent backgrounds or drop shadows.
After taking a rectangular screenshot that is longer in width but shorter in height (such as the dimensions of this HN comment input box on desktop)... then adding an annotation arrow, Xnapper suddenly cuts off the top n pixels, cutting off its own generated backdrop, and the arrow is placed not where the user selected, but n pixels below that point.
I've given up on trying to resolve it and for shorter screenshots I now use the built-in macOS option again instead of Xnapper.
Ah got it. This is a known issue, usually I workaround this by first putting the arrow elsewhere in the middle of the pic and dragging it to where I want it later (not great, I know…). I haven't been putting a lot of time on Xnapper lately, sorry about that. I'll prioritize this and push out an update soon.
[1]: https://github.com/trungdq88/summer