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).

Thanks for understanding.

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.

It has to be added to the command when you want to launch it, or added to the .desktop file so it does so automatically. On KDE, it should be as easy as right clicking it on the start menu and clicking “edit application” on the second tab there should be a command field, where you can add the variable at the beginning.

In case this doesn’t fix it, your alternatives are copying and pasting passwords or, if your main use for it is in a browser, using the official extension.

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.

Dude, the 1080 came out in 2016, that was just… oh.

deleted by creator

That’s not all the context, though. GamersNexus made a video detailing it further. and a follow-up.

Are you on NVIDIA?

Interesting, it seems to address some of the security flaws F-Droid has; it would be nice to see where this project goes once it’s a bit more mature

XMPP is a protocol for decentralised chats, allowing people registered on different servers to chat with people on other servers, kind of similar to how email works (and Lemmy of course).

Google Talk was a service by Google which started with XMPP support, letting users from other XMPP servers chat with Google Talk users. Google Talk was always slightly different from the XMPP standard, due to having proprietary code in its backend, leading to chats between Talk users working flawlessly but not between XMPP and Talk users. Slowly, Google Talk became more popular than the other servers.

Eventually, XMPP server-to-server support was removed as part of their transition to Hangouts, meaning once Talk users switched to it, XMPP users would no longer be able to chat with them and would have to switch to Hangouts. While XMPP still exists today, it’s definitely a niche nowadays, and this is part of the reason.

Edit: proper paragraphs

That’s how people thought it would have gone with XMPP and Google Talk, but that’s not how it went at all