Instance admins can setup a slur filter for their instance, which automatically removes that word from ever appearing on that particular instance.
users won’t want to use an instance that can’t view content from threads (since that where’s most content would be), but they’ll be much more open to joining an open source instance that federated and views stuff from there as well.
I’m totally willing to discuss my thoughts since it seems I’m in the minority on this threads mania-
Once Threads launches it’ll obviously have a lot more users than the whole fediverse combined, maybe even 90% of all users. Now let’s say some instances with barely 1-2% users and small content feed defederate from it. Do people think a new user who does not care about things like open source or privacy will join the niche instance? No, people will go where the content is. Big social media giants will jump on fediverse bandwagon and instances who dont fetch their data will become extremely niche communtites (some might like that but it’s not good for overall fediverse health).
Instead let’s say we keep federated with threads, and make posts like how YSK: other instances don’t track your data, other instances are free from corpo greed, other instances are run by normal people etc etc and make users aware and let them naturally migrate. Ideally, meta will bring the eyeballs which we can help to make fediverse as a whole grow.
imo it’s naive to think that us 100k users defederating will put even a dent on threads. Insta tik-tok people will join the new trendy social media and generate content. The only solution is to make people constantly aware that better alternatives to view the same content exist.
Password managers are as important as adblockers in this day and age imo
Was with you until the money point. It’s extremely easy to get this data and there will be many open source versions doing this thing.
But I agree that who upvoted a post shouldn’t be federated.
for personal use, main reasons are you won’t have to worry about instance admins making arbitrary decisions that you don’t agree with, and no worries about server overload or downtime.
for making an instance for public, helping fediverse become a more viable alternative by spreading the load over more instances and helping it grow.
The beehaw and world defederation (which I assume you are referencing) is temporary because beehaw believes the increased traffic cannot be moderated without proper mod tools.
And while you’re right about mainstream things like gaming or technology won’t have a single main community, I feel more niche communities will be able to setup their main communities. Obviouly that’s just my opinion, but there are some signs of that happening already. (c/piracy for example)
As time goes one community will emerge as the main one while other would dry up and naturally become obsolete (until people get angry with the mods of main one and start looking for alternative community, similar to how there are r/truegaming, r/true(x) etc for popular subreddits.)
There are many open PRs on lemmy github on how to aggregate similar communities. For example there is a suggestion of making an auto multireddit like thing, m/gaming for example, that would merge posts from every c/gaming community (not sure how this would work with defederation and stuff). With enough demand, something like that can be added to lemmy by an experienced dev.
Right now the best way is to search from inside a lemmy instance itself. lemmy search finds much better results than what native reddit search used to give.
I made a collection of guide in this post.
I’ll try to keep it updated as more guides are created.
Making links agnostic is an open PR which will be implemented eventually.
This seems like a much better explanation for Lemmy compared to the email analogy everyone writes for non-tech savvy people.
In case people missed it, lemmy devs reponded to this post here https://github.com/LemmyNet/lemmy/issues/2977
That’s true, duplicate copies of the same book is perhaps the main pain on bookwyrm right now. On the other hand it also feels like a problem that devs must be aware of and are actively trying to figure out a solution for.