Like robots by Boston Dynamics, it starts with wheels, and now it can parkour. So maybe next iteration will be using legs

But it has better performance

It seems lemmy way to show hot and active kinda broken. I’ve changed my default to TopDay or Top - SixHours, to get new contents

Even Supernatural has actual ending after 15 seasons

Why is there no lemmy.world community at all? I’m pretty sure it has a lot of big communities

It’s great, but the act 3 kinda ruined it

At that point why not just using Samsung phone and sideload the OS? Seems weird to do that on Pixel which has inferior hardware and good software (like its camera apps), and then remove the software

I also use Connect and just realize there’s an AMOLED theme

“Great men are forged in fire. It is the privilege of lesser men to light the flame.”

Maybe try to open your setting page via browser, and disable nsfw from there. It will stop all nsfw posts whatever apps you use

They don’t even have same cables on their laptop

Until your instance defederated from big instances

That’s why you should use JS

Does your instance updated to latest version of Lemmy? Afaik, since 0.18 active and hot mostly work as intended

Do you realize that fediverse is not one single project? For example Lemmy and Mastodon has different implementation and developers. The only thing that connecting them is ActivityPub, which is owned by W3C, not the community. So basically Meta created their own implementation for Threads (so it’s already propertiary), and theoretically already able to pressure W3C to change the ActivityPub without even joining fediverse

So they have already reaching OP’s first point without doing anything

I think I miss something, the ActivityPub protocol is not owned or maintained by Mastodon devs. Isn’t this just standard communication like an extension of HTTP? something like GraphQL (that created by Facebook itself). Quick google mentioned that ActivityPub is maintained by W3C.

So Meta can (and I think currently uses) ActivityPub, and all of your points already been possible without needing to federates with any other instances. For example, they already can say that ActivityPub doesn’t work on some cases, and push W3C to do some changes on the standard

All of your points only considers the community itself, which is not my argument.

I’m mostly approach this from technical standpoint. It’s impossible to have 100% uptime if there’s no horizontal scaling capability. For example on updating version, currently the instance will need to shut down for maintenance until it’s finished and usually there’s still some issue to fix. If horizontal scaling exist, the instance can update server (or add additional one), move the traffic a bit to test it, and then fully rollout if everything going well.

Let’s say all of mastodon instances not federating Threads. What stopping Meta to do EEE on ActivityPub? That protocol is not owned by mastodon creator or other devs. It’s handled by W3C afaik

Why not? I don’t see the drawback to develop ability to do horizontal scaling. If the instance owner doesn’t want to add additional servers, it’s up to them. Obviously they paid for it if they decide to add.

Just to be clear, horizontal scaling means multiple servers handling same instance, it can be the backend service to allow handling more traffics, or multiple db to reduce database loads.

Additionally it allows high availabilities, so if one of the backend service is down (either unexpectedly or do rolling update) the other service can still active so the instance can still be accessed by users