• 3 Posts
  • 20 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle




  • You should see some of the pushback I get for daring to post popculture or feminist news.

    Can you please share this with me so I can see this? I may end up running into similar challenges as you, so it would be helpful to foresee them.

    The way we get more diverse topics is by gaining a more diverse user base.

    I partly agree, and I think this initiative is partly aimed at making the fediverse more attractive to users who are interested in these topics that we will target.

    Generally speaking, the existing members are very resistant to any topic outside of technology, politics, and gaming.

    I personally have seen a lot of appetite from many users here for topics outside of these. I think the problem is that, those topics tend to be more scattered and there is less consensus. But the beauty of the fediverse, and this reddit-like format we have, is that topic-specific communities can thrive independently and we do not all have to like them.

    I may end up being wrong and this ends up being a failed project, but I think it is worth trying. And I am happy and thankful that you are interested despite your skepticism!














  • The first issue you bring up would be resolved with the idea of separating identity and authentication as separate providers from instance providers. In fact, it’s much better than just relying on a small difficulty, as that is more likely to discourage a well meaning non-technical person than a malicious actor.

    Wktn separate identity providers, your instance can trust the identity providers that have good reputation. And if I want to be seen by your instance, then I have to have one of those identity providers approve me.

    Different identity providers will have different standards and requirements.


  • The downside is that if you’re new to the fediverse, you have no way of knowing whose lists you should follow.

    Isn’t the whole idea that you choose a trans-friendly instance and you naturally adopt the instance wide blocklist? Same thing here, except you choose the block list similar to choosing an instance in the old flow.

    And if you disagree, this could still easily be mediated. For example, the instance could have a default block list. As long as one can opt out, that would respect user choice.

    Or choosing the blocklists can be part of the account creation flow.

    There’s others ways to go about it.

    Beyond that though, on an instance like blahaj, it would be largely irrelevant, because there is no scenario where I let transphobes federate to the instance

    What I suggest isn’t meant to take away the instance owner ability to defederate or moderate. But this makes it such that you don’t have to modify your moderation strategy when your users can adopt different moderation in addition to what you have. (example: maybe a large group of your users want to block US-centric content, or political content, etc.) and people not on your instance could possibly adopt your moderation as well!