TheEntity

joined 1 year ago
[–] [email protected] 3 points 7 months ago

It doesn't use the system libraries, unless the system on 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.

[–] [email protected] 13 points 7 months ago (1 children)

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.

[–] [email protected] 12 points 7 months ago (3 children)

Are screenshots even still considered evidence? They should be absolutely trivial to manipulate.

[–] [email protected] 3 points 7 months ago

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

[–] [email protected] 37 points 7 months ago
[–] [email protected] 7 points 7 months ago

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.

[–] [email protected] 13 points 7 months ago (1 children)

I guess this is one area that AI can actually improve in our lives: https://www.summarize.tech/youtube.com/watch?v=jzQS9MmlEy8

[–] [email protected] 19 points 7 months ago* (last edited 7 months ago)

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

[–] [email protected] 2 points 7 months ago

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.

[–] [email protected] 5 points 7 months ago (1 children)

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.

view more: ‹ prev next ›