• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle





  • I’m not super familiar with the right terminology, but in short I think users should be able to follow whoever they want, but restrictions on how it is interacted with is fair game. I think following and replying to threads accounts is sort of a must, even if boosting and other functions are disabled. Also on favor of preventing non-replies from being sent to threads.

    The real issue issue is interop with Threads means surveillance of users. Limiting the info going from here to there is essential. However a read-only mode that lets us get some value out of it is fine








  • Pointing out flaws in the country shouldn’t be seen as a personal attack or critique. Many of the victims of America are it’s citizens (e.g., the incarcerated).

    Nationalism just twists the government into our personal identity to manipulate us. Making fun of the government/system is healthy.

    This isn’t “Americans dumb” content, which attacks the actual citizens and understandably may weigh on someone.




  • I’m not sure blocking Meta is worthwhile in the long term. Say what you will about email, you still have some degree of choice over your host. I want better for the fediverse, but that’s still a marked improvement over mainstream social media.

    In the short term, Meta wants to kill Twitter by collecting all its A-level users. I think this would be good for the fediverse, these are news outlets and poltiicians and etc making posts most people want the option to see in their feed. These are also users who want no-fuss platforms with some amount of “customer service”, and mastodon.social is simply not ready to provide that.

    The issues it poses to re-centralization are an inevitable threat as the Fediverse grows. Unless there is a concrete plan to build protections and this is a stop-gap effort, I’m not yet convinced it’s worthwhile.


  • It’s really an issue with how the fediverse handles communities. On Reddit each sub had its own moderation/governance structure which I think fits the role of an “instance” best. Here, each instance has a variety of communities which may overlap with other instance.

    I.e. banning an instance for having community X impacts community Z who may also dislike X.

    Without ripping up the floorboards, I suspect the answer is instances having community-level granularity in blocking. So one can block: The_Donald@*, *@sh.itjust.works, or most narrowly The_Donald@sh.itjust.works