quortez

Congratulations, you’ve sufficiently annoyed me enough to log in to my local instances to type this out.

There is no ”one” way to speak and write English — we don’t have an “”“official”“” institute of our language like Spanish or French does (and even if we did, they would not have a monopoly on English). We don’t speak in Received Pronunciation or keep the superfluous ‘u’ next to every ‘o.’
Like every language, English has multiple dialects with their own vocabulary, and even some with their own specific grammar. The sentence in the OP was likely written in one of them - African-American Vernacular English. This dialect codifies double negatives, the habitual be, and words like ‘finna.’ Many of its aspects are already integrated into ‘standard’ American English.

This is part of the process of language in general. Many of the rules in ‘proper form’ come from shorthand, slang, and and crude versions of other languages and forms. Being aware of the rules shifting and changing as people shift and change how they speak will probably get you further than turning your nose up at rules you don’t recognize.

Macabre. Why do you need two silent letters?

You can even file an issue (or upvote similar ones) here: https://github.com/LemmyNet/lemmy-ui

I’ve had it fail with most SAF locations I tried after Android 11, especially pCloud. After the database locks and KDX leaves the RAM, it often cannot find the database it literally just saved, and will often just generate a merge conflict to the location it attempted to save. As a result, after you unlock once, it can no longer unlock the database and you have to bring up DocumentsUI again.

KeepassDX is the modern one I’m referring to. Because of the whole Android 11 SAF/scoped storage issue, syncing to databases and clouds that use DocumentsUI (the special folders you see when your Files manager window opens) fails all the time. I’ve repeatedly lost data due to KDX not properly saving or syncing, causing file conflicts and the passwords I literally just saved to vanish the next time I unlock the database.

The developer’s response is that it’s everyone else’s fault that their apps’ SAF implementation is bad, not KDX.

I absolutely cannot recommend using it.

I would be happier with KeePass if the Android situation wasn’t so bad. The most reliable app still uses UI elements from goddamn Froyo and the more sleek, modern, auto fill aware app can’t deal with cloud sync to save its life. I hate it here.

Fuck, I really hope this doesn’t turn the tides for other Red Hat projects.

Not even my Linux distros can escape the enshittiness. WTF man.