home.social

#fediversesafety — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fediversesafety, aggregated by home.social.

fetched live
  1. 🔎 Fediverse Safety & Accountability

    I’ve been reflecting on how different Fediverse instances are run, and how much power admins and moderators have over users. With that power comes responsibility.

    From now on, I intend to scrutinize and document harmful or unsafe moderation practices across the Fediverse. This is not about targeting individuals, but about protecting community members and raising awareness.

    Every instance should be accountable for how it treats its users. Cyberbullying, abuse of authority, and dismissive behavior must not be ignored.

    Transparency and accountability are not optional — they are essential for a healthier and safer Fediverse.

    #Fediverse #Accountability #DigitalSafety #ModerationMatters #AdminPower #TransparencyNow #SafeCommunities #UserRights #EthicalModeration #OnlineAccountability #FediverseSafety #StopAbuse #CommunityHealth #OpenWebEthics #DigitalResponsibility #ProtectUsers #SaferFediverse #EthicalWeb

  2. CW: Behaviour in the Fediverse, especially non-Mastodon behaviour, of which you probably don't know that it's inherently racist; CW: long (over 4,200 characters), Fediverse meta, Fediverse beyond Mastodon meta, mansplaining, reply guys, racism, sexism, homophobia, transphobia, queerphobia, ableism, Islamophobia, anti-Semitism, anti-Judaism, xenophobia
    So I've just learned the other day that curating your timeline/stream according to your personal interests and/or the topic of your account/channel is utterly racist. No matter how specialised your account/channel is.

    Everyone in the Fediverse is basically required to follow a substantial amount of Black users, especially Black activists. If you're on Hubzilla or (streams), you must actually follow them, i.e. you must give them full permissions to send you anything and everything unhindered and unlimited. You must not use account/channel-wide or per-contact filters on them. Even if each one of them boosts 100 posts per day, you must not filter or disallow their boosts.

    Also, if you're on Friendica, Hubzilla or (streams), all of which count and list unread messages, you must not simply mark what has come in from them as read. You must read it all and be interested in it all. This includes all comments on these posts. And yes, you must re-read everything whenever it tries to catch your attention again, e.g. if someone has liked/faved or boosted/reposted/renoted/repeated it.

    But even if you receive thousands of comments along with those hundreds of extra posts, you must not comment on these comments. Not unless either a comment mentions you explicitly, or you're mutually connected to whoever wrote the comment. As you wouldn't even receive that comment on Mastodon, replying to it counts as reply-guying and mansplaining on Mastodon, completely regardless of how you comment. It's highly disrespectful, and if Black people are involved, it's racist.

    It doesn't matter if this has allegedly been perfectly normal, the standard and part of the culture since five and a half years before Mastodon was launched. Mastodon rules supreme over the whole Fediverse, and only Mastodon's culture has any validity anywhere in the Fediverse. Any culture that differs from Mastodon's is toxic and evil and must be abolished.

    Speaking of which, let's suppose you come across one of these many threads in which Black Mastodon users talk with other Black Mastodon users and Mastodon-using allies about how the Fediverse needs to be made safer. In this case, no matter how blatantly obvious it is that all people involved in this thread have no idea of the Fediverse outside Mastodon, you are not allowed to chime in and tell them about places which are safer due to their technological design and how they work.

    First of all, it'd be mansplaining and reply-guying. Second, there's a tendency for Black Mastodon users to trust the rest of the Fediverse even less than Mastodon, what with e.g. Nazi instances on Pleroma. And third, your suggestion is likely to be taken for an attempt at nudging them into moving to one specific place, essentially trying to hoard them in a ghetto and segregate them from the rest of the Fediverse. In short, there's letting them wait for the Mastodon instances they're on to improve, and there's racism.

    While we're at it: Even if you're on Friendica, Hubzilla or (streams), and you hate Mastodon with a burning passion for very good reasons, you must support Black-led Mastodon instances. Otherwise you're a racist.

    Lastly, while I don't have proof for it, I'm pretty sure that everything that counts as racism towards Black users may also count as
    • racist towards everyone else who isn't white
    • sexist towards everyone who isn't cis-male
    • homophobic towards everyone who isn't heterosexual
    • transphobic towards trans people
    • generally queerphobic towards everyone who isn't cisgender
    • ableist towards disabled people, no matter what else you do to include them
    • Islamophobic towards Muslims
    • anti-Semitic/anti-Judaist towards Jews
    • and generally hostile and xenophobic towards all marginalised minorities anywhere in the Fediverse.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #FediverseSafety #Mansplaining #ReplyGuy #ReplyGuys #Racist #Racism #Sexist #Sexism #Homophobic #Homophobia #Transphobic #Transphobia #Queerphobic #Queerphobia #Ableist #Ableism #Islamophobic #Islamophobia #AntiSemitic #AntiSemitism #Xenophobic #Xenophobia
  3. @The Nexus of Privacy

    About point 4


    No can do, at least not support for Black instances. That's because all Black instances are Mastodon instances.

    I do not support Mastodon. I hate Mastodon with a burning passion, and I hate the wide-spread notion that Mastodon is absolutely the bee's knees even more. My support for Mastodon is limited to filing bugs on its GitHub repository when it misbehaves in interaction with Hubzilla or (streams).

    I will so much not support anyone's stay on this utter piece of crud.

    Don't get me wrong. The reason why I won't support them is not because they're Black. It's because they're Mastodon.

    And besides, you've written yourself that a Black instance is a ghetto. The kind of ghetto that Black people don't want anyone to tell them to move to. Even if they've chosen themselves to have their Fediverse homes there, it's a ghetto all right.

    This is also one of the reasons I will no longer suggest (streams) to the Black community, regardless of whether it might actually be a solution for parts of their imminent problems. I'm not going to tell anyone where to move. Even an unsolicited suggestion, even as little as mentioning the existence of a potential Mastodon alternative and its advantages over Mastodon is passive-aggressive.

    Even if someone wished "the Fediverse", read, Mastodon to have a certain feature that'd greatly improve safety and privacy, and Hubzilla and (streams) had this feature readily available right now (and this has happened in this very thread), I would no longer mention them unless maybe in a purely white cis-het discussion. Mentioning them to Black people would be like trying to nudge them into a ghetto. And supporting ghettos in any way or other is racist.

    Seeing as how much damage any attempt by a non-Mastodon user at helping can deal, it's safer for all involved to not do anything and let people continue believing the Fediverse is only Mastodon.

    (5/7)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Hubzilla #Streams #(streams) #Safety #FediSafety #FediverseSafety #Privacy #FediPrivacy #FediversePrivacy #BlackFedi #BlackFediverse #Racist #Racism
  4. CW: Another discussion on Mastodon about how racism and harassment could be beaten; CW: long (over 1,000 characters), Fediverse meta, Fediverse beyond Mastodon meta, link to racism, link to harassment, quote-post
    Looks like a purely Mastodon solution for racism and harassment on Mastodon is being sought in this thread.

    On the one hand, I think such threads need some more insight from outside Mastodon.

    On the other hand, I think nobody in this thread really wants to know how things are outside Mastodon. Or, in fact, outside their own instance. They want solutions for Mastodon, for the instances they are on right now themselves. Without having to take the rest of the Fediverse into consideration.

    Paul Cantrell wrote the following post Tue, 30 Jul 2024 00:10:38 +0200 Just to state the obvious:

    Any moderation system like Mastodon’s that regularly lets through the kind of sewage that @KimCrayton1 has been highlighting is a moderation system that is failing.

    Failing.

    Full stop. https://dair-community.social/@KimCrayton1/112872020308883967

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Racism #CWRacism #Harassment #CWHarassment #QuotePost #QuoteToot #QuoteBoost #FediverseSafety
  5. @Stefan Bohacek @Jon Such safety improvements cannot and must not come from within Mastodon.

    For if they did, it would be non-standard, proprietary, undocumented, Mastodon-exclusive solutions that anything that isn't vanilla Mastodon or a soft fork would hardly be able to adopt themselves and oftentimes not willing either. Fediverse devs are turning away from allowing Mastodon to take control over the development of the Fediverse by introducing more and more non-standard, Mastodon-exclusive stuff.

    Even worse: If these were Mastodon-only solutions, they might lead to two possible outcomes. One, since the rest of the Fediverse won't support them, the rest of the Fediverse would easily be able to circumvent them. Routinely even. See "quote-toot opt-in". Remember that almost everything in the Fediverse that's an alternative to Twitter and/or Facebook has quote-posts readily available and can quote-post any Mastodon toot right now.

    Two, an unbridgeable rift through the Fediverse as Mastodon splits everything that isn't Mastodon itself off. This could be because Mastodon makes itself incompatible with everything else in the Fediverse by introducing new mandatory features that everything else doesn't support. Or it could be because new rules come with new features that demand the use of these features at instance level, and instances that don't use these features will be Fediblocked. Only that nothing that isn't vanilla Mastodon is even able to use these features.

    For these reasons, such safety advancements must never be Mastodon developments.

    Instead, they must come from the ActivityPub side. And there are things in development right now which, if actually implemented, will increase security in the Fediverse tremendously.

    Specifically, what I mean is what @Mike Macgirvin 🖥️ is working on right now, the guy who invented Friendica, nomadic identity and Hubzilla, and who has created and is maintaining [#^https://codeberg.org/streams/streams]the streams repository[/url] which contains the probably most advanced Fediverse server application of all.

    He wants to bring not only nomadic identity to native ActivityPub, but also (streams)' extensive, fine-grained, powerful system of permissions which would then be understood not only amongst (streams) and Hubzilla, but all across the Fediverse amongst those projects that implement them.

    Imagine being able to post only to the members of a specific list. Imagine these posts being unable to ever leave the list, save for copy-pasting or screenshots.

    Imagine being able to choose which ones of your connections shall be allowed to see your posts. Or send you posts. Or reply to your posts. Or send you DMs. Or see your followers and followeds.

    Imagine being able to define permission roles, pre-configured sets of permissions, and assign one of these to each one of your connections.

    Imagine being able to set your entire account to post only to your followers by default.

    Imagine being able to deny everyone the permission to reply to a certain post of yours. Imagine being able to only allow your connections to reply to a certain post of yours. Imagine being able to limit the timespan within which a post of yours can be replied to. Only if that post isn't a reply itself, but still.

    Imagine being able to wall up your account, but without walling it up against everyone by only walling it up against certain people.

    Sounds like utter science-fiction. But all this is available on (streams) right now.

    Granted, it does not provide absolute, 100% water-tight safety against everything. Like comparable with a shielding that wouldn't even let one neutrino through in ten billion years. But as much such perfect security is desired, as impossible it is. Not unless e.g. the Black community creates an exclusive, walled-garden safe space whose aspiring members must be validated by meeting an admin or moderator in real life, eye to eye, to prove that they're actually Black. Sorry, but everything else can and will be circumvented to attack and harass them.

    Also, yes, this permission system is not as easy-peasy to handle as the official Twitter mobile app. And it currently comes with a fairly cumbersome UI. That's because, as of now, it only works with (streams)' Nomad protocol and, within certain limitations, the Zot6 protocol used by Hubzilla which has a similar set of permission controls.

    I mean, I'd love to see a "Black (streams)" come into existence with a bunch of instances of its own and flourish. For one, (streams) has better chances to be a (fairly) safe haven than Mastodon. Besides, this would give (streams) the publicity it so much needs, especially if Black (streams) started thriving after Black Mastodon has failed so spectacularly.

    But let's face it, it's more cumbersome to use in comparison with Mastodon than Mastodon is in comparison with Twitter, also because (streams) is the descendant of a Facebook alternative rather than a Twitter clone. And if you're on a phone, it's either a PWA or a Web browser because there's no (streams) app.

    Good news, however: As far as I can see, Mike's goal is to implement all this in ActivityPub with FEPs so that any pure ActivityPub project can adopt it. Friendica can adopt it, fairly easily even because Friendica is (streams)' earliest predecessor. Misskey and its forks can adopt it, and these projects are chock-full of LGBTQIA+ people. Everything can adopt it.

    Unfortunately, implementing it in ActivityPub so it works nearly the same as on (streams) will be easier than pressuring Mastodon into implementing that stuff.

    Lastly, there's one feature of Hubzilla and (streams) that won't make it to ActivityPub because it can't. And that's the ability to turn ActivityPub support off altogether, both for users at channel level and for admins at instance level.

    One flick of a switch, and the entirety of Mastodon is blocked. All of it. As is Threads. As are the various Mastodon forks, Pleroma, Akkoma, Misskey, the various Misskey forks, Mitra, micro.blog, Socialhome, Pixelfed, the entire Threadiverse etc. etc., and if you're on (streams), even Friendica and GoToSocial.

    But if you are on ActivityPub, that wouldn't make any sense to be able to do.

    CC, FYI because you've participated in the thread: @Ericka Simone @Stu @Leon Cowle

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #Streams #(streams) #ActivityPub #Permissions #FediverseSafety
  6. @The Nexus of Privacy And why fork Mastodon, the most lack-lustre, underwhelming, underequipped and out-dated of all Fediverse projects, if the Fediverse already offers what you're looking for?

    Because it does.

    Imagine something that gives you the power to adjust things like
    • who can see your posts
    • who can send you their posts
    • who can see your profile
    • who can see your connections
    • who can comment on or fave your posts
    • who can send you DMs (yes, this is a separate setting)
    • who can quote or boost your posts
    • and many more

    Now imagine these permissions can be given to, depending on the setting, seven or eight different subsets of users, including but not limited to:
    • only yourself
    • only your own confirmed connections (yes, their logins will be recognised)
    • only those of your connections whom you explicitly grant that permission by adding them to a privacy group which grants that permission

    It gets even better: If something is not allowed, it isn't just deleted from your timeline. It is rejected at server level.

    Mind-blowing? Maybe.

    Utter science-fiction? No. Fediverse reality since 2012, almost four years longer than Mastodon has existed.

    Okay, let me add some more stuff on top.

    How about a character limit of not 500, not a few thousand, but infinite?

    How about the option of being safe from instance shutdowns because all your content, your posts, your contacts in both directions, your files, your settings, your everything simultaneously exists on multiple independent server instances?

    Now this has to be a fever dream, right?

    Nope. Reality since 2012 when @Mike Macgirvin 🖥️, already creator of the Facebook alternative Friendica, started developing more and more advanced and powerful Fediverse server applications, from 2013's Red Matrix to 2015's Hubzilla (which still exists, which I'm using) to 2018's Zap and finally to the most recent and most advanced incarnation, established in October, 2021 and still advancing ever since.

    The streams repository.

    Whatever you may want to add to Mastodon, (streams) very likely already has it implemented right now.

    Whatever marginalised, harassed groups may wish the Fediverse to have, (streams) very likely already has it implemented right now. Plus stuff they wouldn't even dare to dream of.

    It has been developed, improved and advanced for 14 years, longer than any other Fediverse project, by someone who, in these 16 years, created three Fediverse protocols and about a dozen Fediverse projects, every last one of them vastly more powerful than Mastodon or any of its forks would ever dare to be.

    I'll let Mike speak for himself:

    Mike Macgirvin 🖥️ schrieb den folgenden Beitrag Fri, 12 Jan 2024 23:38:02 +0100

    A brief overview of the streams repository.

    The streams repository is a fediverse server with a long history. It began in 2010 as a decentralised Facebook alternative called Mistpark. It has gone through a number of twists and turns in its long journey of providing federated communications. The fediverse servers Friendica and Hubzilla are early branches of this repository.

    The first thing to be aware of when discussing the streams repository is that it has no brand or brand identity. None. The name is the name of a code repository. Hence "the streams repository". It isn't a product. It's just a collection of code which implements a fediverse server that does some really cool stuff. There is no flagship instance. There is no mascot. In fact all brand information has been removed. You are free to release it under your own brand. Whatever you decide to call your instance of the software is the only brand you'll see. The software is in the public domain to the extent permissable by law.  There is no license.

    If you look for the streams repository in a list of popular fediverse servers, you won't find it. We're not big on tracking and other spyware. Nobody knows how many instances there are or how many Monthly Active Users there are. These things are probably important to corporations considering takeover targets. They aren't so important to people sharing things with friends and family.

    Due to its origins as a Facebook alternative, the software has a completely different focus than those fediverse projects modelled after Twitter/X. Everything is built around the use of permissions and the resulting online safety that permissions-based systems provide. Comment controls are built-in. Uploaded media and document libraries are built-in and media access can be restricted with fine-grained permissions - as can your posts. Groups are built-in. "Circles" are built-in. Events are built-in. Search and search permissions? Yup. Built-in also. It's based on Opensearch. You can even search from your browser and find anything you have permission to search for.  Spam is practically non-existent. Online harrassment and abuse are likewise almost non-existent. Moderation is a built-in capability. If you're not sure about a new contact, set them to moderated, and you'll have a chance to approve all of their comments to your posts before those comments are shared with your true friends and family. For many fediverse projects, the only way to control this kind of abusive behaviour is through blocking individuals or entire websites. The streams repository offers this ability as well. You'll just find that you hardly ever need to use it.

    Because federated social media is a different model of communications based on decentralisation, cross-domain single sign-on is also built-in. All of the streams instances interact cooperatively to provide what looks like one huge instance to anybody using it - even though it consists of hundreds of instances of all sizes.

    Nomadic identity is built-in. You can clone your identity to another instance and we will keep them in sync to the best of our ability. If one server goes down, no big deal. Use the other. If it comes back up again, you can go back. If it stays down forever, no big deal. All of your friends and all your content are available on any of your cloned instances.  So are your photos and videos, and so are your permission settings. If you made a video of the kids to share with grandma (and nobody else), grandma can still see the video no matter what instance she accesses it from. Nobody else can.

    Choose from our library of custom filters and algorithms if you need better control of the stuff that lands in your stream. By default, your conversations are restricted to your friends and are not public. You can change this if you want, but this is the most sensible default for a safe online experience.

    There are no inherent limits to the length of posts or the number of photos/videos you can attach or really any limits at all. You can just share stuff without concerning yourself with any of these arbitrary limitations.

    Need an app? Just visit a website running the streams repository code and and install it from your browser.  

    Nobody is trying to sell you this software or aggressively convince you to use it. What we're trying to do is show you through our own actions and example that there are more sensible ways to create federated social networks than what you've probably experienced.

    You can find us at https://codeberg.org/streams/streams

    A support group is provided at @Streams

    Have a wonderful day.

    Mike Macgirvin 🖥️ schrieb den folgenden Beitrag Sun, 14 Apr 2024 23:13:02 +0200 Here is what we've created:

    Conversations: communicate directly with the people in the conversation, not have completely isolated conversations with your followers and their followers shouting at each other -- and neither audience seeing the responses of the others.

    Permissions: If you haven't been given permission to speak, you aren't part of the conversation.  If you have not been granted permission to view a photo or video, you won't see it.

    Audience: Your choices go far beyond public and not public. Yes, we have groups. We also have circles. You can also just select a dozen people right now and have a conversation only with them.

    Nomadic identity, amalgamated identities and single sign-on: Site and project/product boundaries don't exist. It's one big space and you are you - no matter what service or services you use.

    Post limits, photo limits, poll limits: None.

    Rich content: Use markdown, bbcode, or HTML. Any of them or all of them.

    Rules: You make them.

    Algorithms: You can install them if you want. You can remove them. You control them and can tweak them.

    And much more.

    We are the streams repository.

    https://codeberg.org/streams/streams


    So why does it absolutely have to be Mastodon if the Fediverse has something so much better to offer, readily available in a stable release right now?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseSafety #Permission #Permissions #NomadicIdentity #Streams #(streams)
  7. @[email protected] It's weird how folks miss that it's literally one or two people doing most of the day-to-day on #Iceshrimp and #Sharkey. Folks keep wanting the feature set of something much bigger. Kind of sad to see how many folks keep wanting fedi bling but BIPOC efforts to increase fedi safety get silence from same kind of folks willing to silence Sharkey over their technical peeve.

    Make it make sense.

    #sharkey #misskey #FediverseSafety #fediadmins #fediverse

  8. Good points made by Jon in linked thread.
    Sad that the fediverse is both a generally safe platform for queer folk and a generally unsafe one for black folk.

    Also sad that the fedi software has a lot of talented queer developers creating some great stuff, but technological solutions that might make fedi safety more a thing keep failing to get taken seriously and implemented. Our culture drives what we do & don't focus on. More uwu bling on your Misskey or whatever fork, yes; but ensuring that black folks can onboard without finding themselves on shitty instances, copping racist pile-ons from dark fedi AND queer fedi, and having software shipped with adequate user-level safety controls, uh not so much.

    #FediverseSafety

    RE:
    https://indieweb.social/users/jdp23/statuses/111841420211814156

  9. Eugen, Evan, and the nominally liberal tech bros looking for pay day don't care about queers as much as they say they do.

    It's time to decenter them and their control of the fediverse.

    #BlockMeta #Transphobia #whitefediverse #FediverseSafety #Fediverse #Safety

  10. If you want a history of anti-Blackness on the Fediverse take a read of Mastodon: a partial history. There's a section on the four years of harassment that #PlayVicious (Ro, Artist Marcia X et al) endured.

    Then there's
    Black Twitter, quoting, and white views of toxicity on Mastodon about how the Fediverse embraced the arrival of Black Twitter, or didn't.

    These two articles are by
    @jdp23 @[email protected]

    Artist Marcia X wrote some initial thoughts about the Play Vicious experience in
    Ecosystems of Abuse & Ro started to write their early history of PV on their site. It's down atm so link to the first post is here on his Fedi account.

    Please also check out the audio conversation & transcript of
    The Whiteness of Mastodon where Dr. Johnathan Flowers focuses on Mastodon's long history of whiteness and racism, and how the very positive contributions of queer people are used as a shield against critiques or discussions of the platform racism and overwhelming whiteness.

    #Mastodon #Fediverse #FediverseSafety #Racism

  11. One of the plusses of #fulltextsearch on an instance that federates broadly, is being able to see the amount of chatter by folks that want to hard fork #Mastodon, and folks who want to see more cross-pollination of features between existing forks, and new forks that take #FediverseSafety seriously, Folks who generally can't get a wider feel for what the vibe is like unless they stumble across a Discord channel or Reddit sub. #fediverse

  12. I'm so fucking over the cis men who keep telling us that the #fediverse needs to mainstream. Same dudes who are fawned by the usual tech bro crying about instance blocks crowd. Same dudes who'll scream that any reticence is HOA racism. Same dudes who stan fediverse devs who can find ways to implement more bling here but can't go out of their fucking way to implement #FediverseSafety features so black folks can onboard and exist here without all the racist BS they cop and have few tools to combat it with.

    I came here to escape the dogpiling, queer- and transphobia, chasers and bots, the gender crits & Nazis that brigade so many of us across all major platforms. So far, the only two relatively 'safe' platforms that remain useable for me are the
    actively moderated parts of the #fediverse, and #Bluesky with appropriate mutes and block lists enabled.

    Threads is full of the same creepy follower bots that Instagram has. Unfortunately it is also much more unusable in private mode than Instagram is, so I have to fall back on obscurity as security. If I don't post much there it keeps the bots down, but like IG they build up and bulk delete needs to be a thing. Oh and Byron (thank goodness you're gone and can't reply-guy this post) IG was never coming here, Threads was, and I'd be way surprised if the Threads demographic was younger by much that your kids would have wanted to join so you could have followed them from here. My Threads crowd are basically all former bird site folk. The trolls are basically the same folk who follow us everywhere.

    Please fellas, next time you tell us how amazing the fediverse is because queer and trans folk were once a bigger part of setting the vibe for this place, you take a look at how you keep eroding that vibe away - while you're getting moist at the thought of being kings of bigger kingdoms and can't even use your power and capital to make the changes folks here now absolutely need.

    RE:
    https://mastodon.social/users/troll5/statuses/110885083470406867

  13. CW: What can the person I blocked and muted see of my posts and profile?

    If I #block and mute a user on a #Mastodon instance from this #Calckey #Hajkey instance where we have #AuthorizedFetch turned on, what can that user see wrt my profile and posts?

    I still see their post displayed in my timeline as the parent post when someone I follow replies to them. What can they see of me?
    #fediverse #block #FediverseSafety

  14. @[email protected] I think copies of fedi posts generally are stored on federating servers. Cached at the very least, as I have seen folks find a post in the cache and share it after an OP dirty deleted it. I think this needs more thought cos it being seen and indexed via the federated timeline of a #microblogging software like Masto or Firefish and then generally hidden until browsed with keywords or hashtags seems like a different discoverability profile than being displayed in a #Threadiverse sub. Again, when folks join up to a microblogging instance do we ever explain that cos it's the #fediverse that their post might end up being displayed in a bunch of contexts they hadn't yet imagined or would be comfortable sharing it to? @[email protected] @[email protected] @[email protected] @[email protected] #kbin #Lemmy #FediverseSafety #privacy

  15. CW: My profile picture is for safety; blocks don't hide my friend's abuser; mental breakdown

    I used to have my face as my pfp until the day that I saw another user here replying to someone I knew - a close friend's abuser whose psychological abuse caused them a series of mental breakdowns and hospitalisations.

    I have them blocked and muted and yet I still see them occasionally being replied to by folks that I follow who are unaware of this person's background. I guess they might be able to see me too, so I took my profile pic down (and all selfies are behind a NSFW tag or CW) and removed some things about me from my profile description. Hopefully they don't remember me, even though I remember them and how they tortured my friend.
    #FediverseSafety

  16. Yeah good point by @[email protected] about permissions (or lack thereabouts) for #kbin et al to scrape the #fediverse and put posts/toots into magazines. It feels like so many #Mastodon admins are blind to how the fediverse beyond Masto software & the Masto API actually works.

    Seeing such folks write lengthy posts about defederating Masto instances running Vyr's search patch while the rest of the fedi has
    #FullTextSearch and the #Threadiverse scrapes it with next to no backlash. It's like folks don't know that there's a bigger problem with #ActivityPub re #privacy and #safety than Website Boy's latest antics, and we need to push for #FediverseSafety and privacy flags at a ActivityPub protocol level. Until then, everything is just a non-binding, non-enforceable agreement about cultural norms that there's seems no consensus on; and definitely no focus on minority safety, rather features some will claim are wanted by a majority.

    #MastoDev #FediDev

    RE:
    https://mefi.social/users/cendawanita/statuses/110863987878810727

  17. It's interesting sitting here on an old version of #Calckey seeing someone on #Mastodon server telling their fellow user that posting to unlisted will opt-out of #search when I can see Unlisted posts in my antennas quite easily [though I believe this has been rightly rectified in the newest versions of #Firefish / #Iceshrimp but need to confirm]. Being hidden from the Explore tab on Mastodon is not the same as being unsearchable across the fediverse. Frankly, there's little understanding even among admins across the #fediverse about what's a Mastodon / Mastodon API function that is federated to other Mastodon servers but doesn't translate well outside of Mastodon on other #ActivityPub connected platforms like #Misskey and it's forks, #Hubzilla and #Friendica, or rapidly growing platforms like #Lemmy and #Kbin. Kbin also scrapes posts from across the fediverse and puts them into its own magazines.

    Unfortunately simple, up-to-date documentation doesn't really exist to explain the
    realities of federation vs what your admin said was the reality. AP was not built with privacy in mind, and 'security through obscurity' was mostly a Mastodon thing from when folks thought either the Mastoverse was almost the dark web, or the whole fediverse [which has never been the case], and Google et al weren't interested in scraping it.

    Unfortunately we have a cadre of devs across all fedi platforms who'll give glowing lip-service to both the fedi and ActivityPub histories of being built by queer or other minority identities but still won't work on giving folks the granular
    #privacy and #safety controls that weren't included in those protocols, and whose feature roadmaps now just look like bird site 2.0 funded by the milquetoast liberals in political tech who provide their seed money.

    Beyond Mastodon and GoToSocial, every other fediverse project treats posting to public as opting in to search and indexing. Indeed, this is pretty much how the ActivityPub protocol handles such too.

    #FediverseSafety #Mastodev #Fedidev

  18. Tbh, I now think much of the Threadiverse can be characterised the same way. It's sad to think that there's plenty of Mastodon/*key server owners who allow and tolerate so much more bigoted nonsense on the #fediverse when it has #Lemmy on the tin they're using. The same fucks who haven't pushed for #FediverseSafety have onboarded thousands of more users on software fraught with even less moderation tools.

    RE:
    https://blahaj.zone/notes/9gu8zho9ir

  19. ❤️‍🩹
    'Ultimately, dear reader, what I want for you, is what I want for everyone in this world. I want you to know that you are right: “Anti-racist action is likely to result in further rejection, alienation and victimisation” and that this makes it all the more important to nurture in yourself a sense of ambition for dismantling racism.'
    #FediverseSafety

    RE:
    https://mastodon.au/users/26pglt/statuses/110834481256165607

  20. Tbh, I'm on a proactively moderated server that has preemptively kept a lot of the worst folks from being able to reach us queers here, and the feedback from a handful of black users here is that #blahajzone has also been generally been harassment free in comparison to other servers they've been on.

    Imo, it's actually not to hard as a queer or trans person to find
    #servers on the #fediverse that will protect you from harassment, but that it is harder to find servers that will also protect indigenous, black, Asian users from racist harassment. And too many queer white folks get a free pass for ignorance tbh, a privilege that many of us have had for far too long.

    It's much the same on
    #Bluesky where I haven't been harassed for being #queer and trans - again there's large communities and plenty of allies - but anti-black racism has been in the spotlight again recently and the devs called out for lagging behind on safety and moderation features that bigots exploit for harassment campaigns.

    Far too many fediverse projects are led by men, mostly white men, who are lionised, promoted and financed by another layer of mostly white men. They ultimately get the veto on minority protections.

    #Mastodon #Firefish #Iceshrimp #FindAServer #FediverseSafety

    RE:
    https://firefish.social/notes/9hs7vrern5ptmu66

  21. I hope #Hajkey keeps developing for blahaj.zone and similar communities, particularly the long sought after #FediverseSafety features that never seem to arrive on the #Fediverse and become more important as greater adoption occurs and user culture changes - like the amount of transphobic users that Lemmy has brought here and the dev bros think this is progress. #Firefish #Calckey #IceShrimp @[email protected]

    RE:
    https://hachyderm.io/users/maegul/statuses/110767208159622462

  22. ok at least one of the troll servers has a block bot? which auto-posts the public profile of anyone who blocks someone on that server so be aware of this possibility; worth checking their home server to get a feel of the vibes before you block or check the box to also report there. i got a handful of more trolls after blocking someone because they were clicking on the bot post and now i know! / #fediverse #fediversesafety

  23. And now we're nearly at 1000 accounts and it still feels like an oasis from hate. I love that this place exists, our safety is paramount, and that won't change regardless of what other servers do. #trans #fediverse #fediversesafety #calckey #hajkey #findaserver

    RE:
    https://blahaj.zone/notes/9b72q4atv4

  24. Some thoughts about #fullsearch of federated-with instances. 🧵 1/2

    1. Conflating any ill will you have with Supernovae at
    #Universeodon, with the issue of search indexing on the Fediverse to justify your fediblock won't help resolve the issues around search.

    2. It isn't global search. While we shout, lock down, and don't participate in building the additions to our protocols that the
    #Fediverse needs, we've been letting #Google index the Fediverse. It's already searchable and Google's new Perspectives tab is going to make it even easier. Maybe we could fight that rather than keep thinking it doesn't exist and continuing to write ineffective Facebook-viral style "I do not give permission..." copypasta?

    3. The
    #Fediverse does not respect your do-not-index-my-posts flag. It never has. It can't. It's not supported by the #Mastodon API, as @[email protected] explains, and nor is it supported at #ActivityPub level and will need to be added into a new AP protocol.

    Every instance server from the #Misskey (#Calckey, #Foundkey), #Pleroma (#Akkoma), and #Friendica (#Hubzilla, #Streams) lineages has full search of federated-with instances as default. All these services actually pre-date the creation of Mastodon in 2016 you can read @[email protected] 's post for their commentary on such. Fediblock all of them to create your very own #Mastoverse or you could become part of building a better, safer, Fediverse? Perhaps through participating in the Fediverse Enhancement Proposals? #FEP


    #FediblockMeta #meta #FediblockDiscussion #nosearch #fullTextSearch #FediverseSafety

  25. @[email protected] I think whatever we become we'll really only have 'succeeded' if #Calckey leads the way with #FediverseSafety ahead of features and scale.

    The Calckey I see would
    - have a diverse team of folks that has the time to listen to the safety discourses, and the lived experience to know why safety matters, and informs their
    #development decisions.
    - make importing
    #blocklists or integrating third party #moderation tools easypeasy, so no user finds themselves on an new server that's open to dogpiled by the worst elements of the #Fediverse.
    - have robust
    #accessibility features that are as important to promote as #quoteposts and #MFM.
    - have granular user controls for
    #safety - opt-in & opt-out; and features - like turning down/off MFM when it's overwhelming without a user needing to resort to CSS scripts.
    - not really care to be a birdsite or
    #Mastodon alternative. Let's work to be a better secret third thing, or fourth, or fifth thing.

    If we really have to duplicate the big influencer account thing, I'd like to see more non-White, autistic, disabled, queers, and women voices. They're here, but they're often forced to be critics of a newer hegemony. Let's be listening for how can Calckey become the main service of choice for Black, POC and Indigenous women to join, spin up servers, become developers, and have prominent voices on. The rest of the good stuff will follow that.

    I think we can do that, but only if we prioritise, and promote minority voices, and do the structural work to support them coming to the service.

    #FindAServer #Disability #DisabilityMastodon #Queer #structuralbarriers #structural

  26. If you need to hear one thing about the future of the #Fediverse , this is it:

    platforms prioritizing growth over safety are toxic to everyone else who doesn't present as white, straight, and a man.
    the missing link to rehumanizing social media spaces is safety for the most marginalized people that have historically been ignored.
    - @[email protected]

    Devs,
    this is where your eyes & heart have to be if you don't want to repeat the past.

    #FediverseSafety

    RE:
    https://ubiqueros.com/notes/9elt199l02

  27. Really pissed to find out that a block means nothing on #calckey or #mastodon. Feeling ick being able to see the former partner of a friend who I have blocked, because someone on blahaj.zone has replied to them and there they are now sitting in the local timeline. They really fucked my friend up for years with their sociopathic manipulation.

    Now I find out that she can see me if I'm not set to private. Why can't a block be an
    actual fucking block?

    This is the basic shit many folks have been asking for while devs just fuck around with their basic bro stuff.

    I really don't want to leave the
    #Fediverse, but how the fuck is this safe??? How can I feel safe knowing that she can potentially see me? I'd be safer back on the bird site.

    This is not good.
    #safety #fediversesafety #blocked