TheEntity

I’m still confused why people are so hell bent on using a single window exclusively. It’s a natural way to group the tabs and it was there from day one!

Looks like a boring update but being boring is kinda the thing I appreciate in GNOME. It’s all about expectations.

I’m sure we can compromise on a mandatory database of registered AI-generated content that only the corporations can read from but everyone using AI-generated content is required by law to write to, with hefty fines (but only for regular people).

Single tweets are rarely useful without being able to read some context that isn’t visible without logging in.

It still needs a phone number for registration. You just don’t need to share it with people you want to talk with.

A mixture of NixOS and Debian, depending on the machine. NixOS is trivial to maintain and to keep predictable and tidy. When its weirdness is a problem, Debian is my answer. It doesn’t get more normal than Debian.

It doesn’t use the system libraries, unless the system in question is NixOS. It still provides its own dependencies. Arguably in a more elegant and less wasteful manner, but they are still distinct from the ones used by the rest of the system.

EDIT: typo

In terms of the memory usage, it’s a reasonable approach these days. It gets hairy when we consider security vulnerabilities. It’s far easier to patch one system-wide shared library than to hunt down every single application still bundling a vulnerable version.

If you can’t take an obvious joke, I’d rather stay here and you can take reddit, thank you.

If these are hard requirements for her hardware and she’s not willing to search herself with such ridiculous constraints, I’d suggest replacing gf.

And so the enshittification continues. This time not for the consumers. Not yet.

It certainly feels dangerous if forced upon users not aware of the trade-offs. For people already accustomed to using hardware keys, it’s very much an improvement, as more services will support them too. The problem is in the awareness. On the other hand, people already treat regular passwords as throwaway data and expect services to just let them in, or even never log them out. In this scenario, maybe passkeys can still be an improvement: roughly just as much as enforcing using a password manager.

With all due respect, that sounds very much like what something unsupported would do.

Federation combined with keeping the historical federated data consistent is certainly a bitch. We can’t have it all. It could be like email that only handles delivery at any point in time and history is purely local, but Mastodon specifically keeps the federated data public. Propagating the change on the historical data to the federated instances would be nearly impossible. I don’t see how it could have been done better without sacrificing something else.

I don’t think they could do anything about it. As far as I know, Mastodon doesn’t support any kind of instance renaming, so the hostname is one thing you cannot change. You can only spin up a completely new instance.

Not exactly a surprise. It was known it will happen ahead of time: https://archive.is/EaSjE

You can already use Tesseract to run OCR on any image. It’s a matter of tying it together with a screenshot tool with cropping capabilities and it should be very easy to use.

So… iPhone?

Obtaining it legally is one thing. Using it according to the license is at least just as important. Specifically if they trained it on content under GNU GPL or Creative Commons SA licenses, I’d like the result published under these licenses too.