thehellrocc
Using the environment variable QT_QPA_PLATFORM=xcb should do the same thing, but it likely won’t fix your problem. These two methods allow KeepassXC to run on X11, which lets it access other X11 apps (running on XWayland), meaning native Wayland apps still won’t be able to use auto-complete.
There’s probably no way around this for now, as this is due to Wayland’s design, which has stricter keyboard access safety, as opposed to X11 which just let all apps read/use the keyboard all the time.
That’s not all the context, though. GamersNexus made a video detailing it further. and a follow-up.
Unravel 2 is awesome
Definitely nice to have, thanks. I have gotten used to Lemmy’s UI, which, honestly, isn’t that bad, especially when compared to the other site’s new UI. But I’m gonna give this one a try either way, as I might find myself reminiscent of it.
They don’t seem to have a lecturing tone in their comment. The only part which you might have a point about is where they say “objectively”, but throughout the whole comment they’re really just expressing their opinion and showing their experience with smart TVs, which they’re entitled to have and might be different from yours.
No aggressiveness intended. Just trying to keep the niceness around.
TL;DR: F-Droid isn’t referring to that, but yes, the app requires an API key for a paid service to perform unlimited requests.
Long answer:
When using the expression “non-free”, F-Droid refers to something not being free software, where the term “free” doesn’t refer to its price (free as in beer), but to it giving its users freedom to do what they want to with it (free as in speech).
However, this application in particular relies on a service called AudD, which is a paid service based on the number of API requests done. So while the F-Droid “anti-feature” list doesn’t refer to its price, this app still relies on a paid service and requires an API key upon launch (although it seems you can do a limited number of requests without one).