I’m not suggesting anything, just want to know what do you think.
Here is a link if someone don’t know what Meta’s Threads is: https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
I’m not suggesting anything, just want to know what do you think.
Here is a link if someone don’t know what Meta’s Threads is: https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
Yea, though I don’t know about the implementation details, which is why I meantioned “It seems a little early to completely reject the idea before knowing more about the implementation details.”
I don’t really know how facebook intends to implement this. If it’s an “All or nothing” kind of situation, or if they’re are going to separate the instances and groups a bit.
I also don’t know about the options for “federating” - if we could do something like a “readonly” mode for specific (facebook) instances. That way this instance would get exposure to facebook, and if people see that the community is interesting they could make an actual account or something.
Of course there’s no value if we just get a horde of 12 year old trolls and their grandmas as shitposting users
Read only mode might not be too bad, as long as Facebook is diligent in minimizing their environmental impact. If they cached heavily, like API calls and content delivery, that could avoid crushing local instances with drive-by or viral traffic.
However, I think that would be counter to Facebook’s own monetary incentives in bolstering their own user engagement and account retention. This may also impact our instance’s own sustainability outlook, as users hosted on this instance have the greatest incentive to donate to keep the lights on. If the majority of users are remote, then that incentive to donate is one step further removed.