I don’t understand why someone would want to rent their car. Maintenance is not that hard, and companies always make you pay way more for their subscription models. By owning the car, you can pick who does maintenance. Meaning there can be competition, so prices/quality remains good.

For some, this subscription model is great. But do you agree, that is it a bad thing if they force it on us?

Should a dedicated search not use/index ActivityPub instead of the html interface?

If so, instances can simply defederate from search engine instances. So the point you are trying to make still holds.

1. Threads federates
2. Threads hosts 99% of all content and all users.
3. Threads releases and update that allows a new feature. Example: they add buyable threads gold, that you can reward to a post or comment.
4. The rest of the fediverse can’t implement this feature, and is inherently left behind in terms of features.
5. Threads releases an update that breaks federation. 99% of the users do not notice.
6. It takes Threads 3 months to fix the issue.
7. Go back to step 5.

Every non-Threads participant will have less features, and is constantly struggling to keep up with the changes and bugs of Threads. Result: the fediverse cannot grow. Only the most stubborn anti-Meta users will accept the objectively worse experience, just to avoid using Threads. But the average user will just use Threads, instead of joining Mastodon, Kbin, Lemmy, or any of the many other fediverse instances that Threads can federate with.

New users will look at lemmy.world before they create an account. They will choose to join after seeing threads posts and comments on the front page. The default settings will keep them looking at threads untill they figure out they can block it. But when they do, they realise that 90% of all posts and comments came from threads, and they just disabled most of the content.

I would be ok with an opt-in mechanism, where the default settings and the anonymous settings disable threads content, but you can unblock them.

More like “fediverse” instead of “social”. Facebook is also a “social”, but it does not communicate with other fediverse instances. The fact that you are federated and share content is what should be in the name.

And behold: many instances DO use fediverse over lemmy in their name.

But Lemmy is not perfectly compatible with Mastodon and kbin. At the time some of the instances were made, Lemmy could not even federate with Mastodon at all. So it makes sense that instaces explicitly picked a name with Lemmy in it.