TheEntity

You cannot let or forbid a 16yo to use stuff. You can only decide whether they will do it in the open or in hiding. Personally I’d rather have them talk to me about it than hide it from me.

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!

The source got pulled off Github already.

The only thing we know without a proof is that they might be doing it. We don’t have a proof they do it but we also don’t have any proof they are incapable of doing so. A reasonable course of action would be to take precautions against it while not condemning them either, until they are either proven actually guilty or actively unwilling to up their security, which would also strongly imply the former.

Until it’s proven the data is E2E encrypted, it’s a fair assumption it can be read by a 3rd party, either now or in the future. E2EE is the only proof that matters, everything else is just a corporate “trust me bro”.

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.

If you’re asking about a personal opinion: any policy purely based on tradition is worthless. Tradition is just peer pressure from dead people. Just like any peer pressure, it’s highly unlikely to produce anything but grief. If something is based purely on tradition without any other reason to exist, it’s unlikely to be an optimal policy.

Back to the initial question. I don’t think we can get infinitely progressive but we can keep subtracting the cruft of tradition until there is no necromantic peer pressure left at all. Mind that if something happens to be a tradition but still has a good reason to exist, it should be evaluated like any other idea in terms of being good or bad. I mean removing just one of the reasons to keep this idea. If it is left with zero reasons, it’s out. Otherwise it’s fair game.

Just more PTO won’t help either, unless you consider sitting at home a holiday. I live in Europe and my last proper holiday was in the 00s.

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.

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

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.