![](/static/be9a2c79/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
it means that you have to manually reposition every single window, every single time. for any and all apps, by design
it means that you have to manually reposition every single window, every single time. for any and all apps, by design
more like "move glacially and declare things as "will not support’ so technically we had nothing TO fix!"
it’s when devs of a graphics stack just suddenly feel the need to protect your own computer from itself, so they say fuck you to any features that they deem “insecure”, including accessibility features (they will claim they fixed this, but it’s opt-in per app. old apps will just be completely unusable for some people with special needs.)
But they eliminated tearing on the desktop! woo!!!
followed by “worcestershire sauce”
so, you have gigabytesper second of disk io, and the game relies on the couple of megaBITS of internet bandwidth most people have to stream textures? As opposed to downloading and installing them once as an update…
This does not pass the smell test.
you mean it doesn’t work when the device is turned off? weird! /s
the results are random therefore the dataset is useless.
tell that to any fpga toolchain
you released it under a non open source license. So very clearly: no it is not
it is only open source if i can build it myself. Which I can’t if you just give me the weights.
The weights are the “compiled” version of the dataset. It’s the dataset that’s the source, not the weights
no, there hasn’t. What games called ai has nothing to do with the generative ai bullshit of today
by issues I mean breaking existing users’ workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).
There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That’s it, everybody is happy.
So yes, he is the one causing issues. Because the issue isn’t in the features he removed, but by breaking the users’expectation that the package they installed yesterday, is the same one they’re updating today.
well it is that one person causing issues
when in need, cry out for mommy!
there is the keepassxc-cli command. And it also supports ssh keys with integration with ssh-agent. So yeah
one of the extensions has the description: “an easy flow to update passwords”
If that has to be an extension, then this sucks
markdown is standardized? I haven’t found two parsers that parse the same file the same for any but the most trivial documents
the fact that it was found by luck, not methodically, to me implies that there probably are other backdoors we didn’t get lucky with.
nah man, gotta be more specific. When those stuff work on every application.
A screen reader protocol for blind people that requires the app to be recompiled and opt-in to being accessible to accessibility tools, is not a replacement for one that worked for every application. Old apps will become impossible to use for some people with accessibility issues. Though wayland fanboys would tell you to shut up and be happy that a protocol exists, while failing to acknowledge that the protocol is literally fucking useless by design.
deleted by creator
it’s opt-in, per app. Meaning unless old apps are patched and recompiled, they will be inaccessible.