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.
But wouldn’t a case do exactly what you want? It would make the damn thing thicker and flat on the back.
If he’s being a putin stooge because it’s good for his business, he’s still being a putin stooge.
He’s certainly popular but not necessarily liked.
It certainly sounds like you have a strong preference how to split preferences into two groups. ;)
Isn’t every rule just a preference of someone influential enough to make it into a rule?
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
Just because the gameplay was very simple doesn’t make it crap. The details (movement speed, the gap between the obstacles) were pretty much on point and that’s something that makes or breaks this kind of game.
Last but not least, it had little to none anti-user “features” that plague the modern games. I would choose Flappy Bird over most current games any time of the day. Actually there is no “would” in there as I still have it installed.
So… iPhone?
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!