ARTICLE of Techwireasia
this post was submitted on 13 Jul 2023
545 points (96.6% liked)
Technology
59329 readers
5071 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, that's not what I'm saying. I'm saying that because federation is a two-way street and can ben enabled or disabled between any two instances, it will always be possible to have instances that are unaffected by threads. Certainly, some instances will choose not to federate with threads - and so there will always be the possibility to join a community (or create one) that shuts itself off from that influence. Take beehaw.org for example - they didn't like the influence lemmy.world had on their community so they defederated. They are no longer influenced by lemmy.world. The point I am trying to make is that because of that fact (that possibility), there is no reason at all to desire to limit the total scope (userbase) of all of lemmy. If you want a private/closed community, then make one or join one - you don't need to suppress everyone just to achieve your own personal goals for a community.
There was an article not long ago about how blocking threads won't make the problem go away. Not sure how to find it again here, I tried searching for it but there are so many articles about Threads so it's hard to find. Either way it made a very good case why blocking won't make a difference.