#fediblockdiscussion — Public Fediverse posts

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

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

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

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

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

mastodon.social having another bout with spammers? Honestly, they have to do something to sort this out, they're arguably the largest instance, perma-suspending them isn't really feasible but like this is the second? time in as many weeks. #fediblockmeta #fediblockdiscussion

mastodon.social having another bout with spammers? Honestly, they have to do something to sort this out, they're arguably the largest instance, perma-suspending them isn't really feasible but like this is the second? time in as many weeks. #fediblockmeta #fediblockdiscussion

mastodon.social having another bout with spammers? Honestly, they have to do something to sort this out, they're arguably the largest instance, perma-suspending them isn't really feasible but like this is the second? time in as many weeks. #fediblockmeta #fediblockdiscussion

I'm a bit fatigued atm, so I haven't replied to a thread I'm in with some of the #calckey .social mods about moderation and safety tools, but here a snippet of what I did have prepared to say:

So here's the rub, the fediverse will not let calckey.social get away with the same crap that they begrudgingly let mastodon.social get away with. You will be silenced and Fediblocked long before you get their leverage.

I'm a bit fatigued atm, so I haven't replied to a thread I'm in with some of the #calckey .social mods about moderation and safety tools, but here a snippet of what I did have prepared to say:

So here's the rub, the fediverse will not let calckey.social get away with the same crap that they begrudgingly let mastodon.social get away with. You will be silenced and Fediblocked long before you get their leverage.

I'm a bit fatigued atm, so I haven't replied to a thread I'm in with some of the #calckey .social mods about moderation and safety tools, but here a snippet of what I did have prepared to say:

So here's the rub, the fediverse will not let calckey.social get away with the same crap that they begrudgingly let mastodon.social get away with. You will be silenced and Fediblocked long before you get their leverage.

I'm a bit fatigued atm, so I haven't replied to a thread I'm in with some of the #calckey .social mods about moderation and safety tools, but here a snippet of what I did have prepared to say:

So here's the rub, the fediverse will not let calckey.social get away with the same crap that they begrudgingly let mastodon.social get away with. You will be silenced and Fediblocked long before you get their leverage.

I'm a bit fatigued atm, so I haven't replied to a thread I'm in with some of the #calckey .social mods about moderation and safety tools, but here a snippet of what I did have prepared to say:

So here's the rub, the fediverse will not let calckey.social get away with the same crap that they begrudgingly let mastodon.social get away with. You will be silenced and Fediblocked long before you get their leverage.

I'm quite disappointed to see that solarpunk.moe has decided to unilaterally limit or defed notable #calckey instances. The largest of which has a users count around 2000. I'm particularly sad that our #queer #trans instance of 220 users at blahaj.zone is included.

Let me state I'm not an admin or mod at blahaj.zone It really sucks to find out after the blocks and limits are in place through a public post, and the first opportunity our admins get to publicly reply won't be seen or engaged with.

It feels like they're not looking to solve anything, rather to stir up shit as they've effectively shut out everyone who could take their concerns seriously AND change things in order to make things better for them and everyone in general. Also, they are spreading the message that noone working within #Calckey or #Misskey is interested in making things better, effectively spreading the (mis)information that there's no interest in the community for improvement and therefore one does not even need to try to attempt to resolve the problems by contacting anyone and therefore they frame it as a "done thing" rather than acknowledging that everything is a work in progress and people are invested in doing the work and making things better for everyone - if they can.

It's particularly galling when there are folks here on #Calckey, and those who are new to it who are pushing for much of the #fediverse culture that prevailed prior to the Great Migration, that has been overtaken by birdsite culture colonisers on many large #Mastodon instances. And many of us who want to see more safety tools built into our protocols & platforms.

Yes, I think there's some issues with the promotion of #Calckey features rather than devs working on safety tools, but that's a widespread fediverse issue that affects all platforms and third-party apps. I've done a bit of my own turn around about that and I've been pushing quite strongly in public and private conversations with the devs & flagship instance mods, raising many of the issues that @[email protected] and have others have been raising in the large, public conversations about the lack of built-in safety tools on Mastodon. I've been encouraging them to look at these conversations and challenging them how they really do need to be thinking about safety tools much more. Check my posts for receipts.

1/2
#fediblockmeta #fediblockdiscussion

I'm quite disappointed to see that solarpunk.moe has decided to unilaterally limit or defed notable #calckey instances. The largest of which has a users count around 2000. I'm particularly sad that our #queer #trans instance of 220 users at blahaj.zone is included.

Let me state I'm not an admin or mod at blahaj.zone It really sucks to find out after the blocks and limits are in place through a public post, and the first opportunity our admins get to publicly reply won't be seen or engaged with.

It feels like they're not looking to solve anything, rather to stir up shit as they've effectively shut out everyone who could take their concerns seriously AND change things in order to make things better for them and everyone in general. Also, they are spreading the message that noone working within #Calckey or #Misskey is interested in making things better, effectively spreading the (mis)information that there's no interest in the community for improvement and therefore one does not even need to try to attempt to resolve the problems by contacting anyone and therefore they frame it as a "done thing" rather than acknowledging that everything is a work in progress and people are invested in doing the work and making things better for everyone - if they can.

It's particularly galling when there are folks here on #Calckey, and those who are new to it who are pushing for much of the #fediverse culture that prevailed prior to the Great Migration, that has been overtaken by birdsite culture colonisers on many large #Mastodon instances. And many of us who want to see more safety tools built into our protocols & platforms.

Yes, I think there's some issues with the promotion of #Calckey features rather than devs working on safety tools, but that's a widespread fediverse issue that affects all platforms and third-party apps. I've done a bit of my own turn around about that and I've been pushing quite strongly in public and private conversations with the devs & flagship instance mods, raising many of the issues that @[email protected] and have others have been raising in the large, public conversations about the lack of built-in safety tools on Mastodon. I've been encouraging them to look at these conversations and challenging them how they really do need to be thinking about safety tools much more. Check my posts for receipts.

1/2
#fediblockmeta #fediblockdiscussion

I'm quite disappointed to see that solarpunk.moe has decided to unilaterally limit or defed notable #calckey instances. The largest of which has a users count around 2000. I'm particularly sad that our #queer #trans instance of 220 users at blahaj.zone is included.

Let me state I'm not an admin or mod at blahaj.zone It really sucks to find out after the blocks and limits are in place through a public post, and the first opportunity our admins get to publicly reply won't be seen or engaged with.

It feels like they're not looking to solve anything, rather to stir up shit as they've effectively shut out everyone who could take their concerns seriously AND change things in order to make things better for them and everyone in general. Also, they are spreading the message that noone working within #Calckey or #Misskey is interested in making things better, effectively spreading the (mis)information that there's no interest in the community for improvement and therefore one does not even need to try to attempt to resolve the problems by contacting anyone and therefore they frame it as a "done thing" rather than acknowledging that everything is a work in progress and people are invested in doing the work and making things better for everyone - if they can.

It's particularly galling when there are folks here on #Calckey, and those who are new to it who are pushing for much of the #fediverse culture that prevailed prior to the Great Migration, that has been overtaken by birdsite culture colonisers on many large #Mastodon instances. And many of us who want to see more safety tools built into our protocols & platforms.

Yes, I think there's some issues with the promotion of #Calckey features rather than devs working on safety tools, but that's a widespread fediverse issue that affects all platforms and third-party apps. I've done a bit of my own turn around about that and I've been pushing quite strongly in public and private conversations with the devs & flagship instance mods, raising many of the issues that @[email protected] and have others have been raising in the large, public conversations about the lack of built-in safety tools on Mastodon. I've been encouraging them to look at these conversations and challenging them how they really do need to be thinking about safety tools much more. Check my posts for receipts.

1/2
#fediblockmeta #fediblockdiscussion

I'm quite disappointed to see that solarpunk.moe has decided to unilaterally limit or defed notable #calckey instances. The largest of which has a users count around 2000. I'm particularly sad that our #queer #trans instance of 220 users at blahaj.zone is included.

Let me state I'm not an admin or mod at blahaj.zone It really sucks to find out after the blocks and limits are in place through a public post, and the first opportunity our admins get to publicly reply won't be seen or engaged with.

It feels like they're not looking to solve anything, rather to stir up shit as they've effectively shut out everyone who could take their concerns seriously AND change things in order to make things better for them and everyone in general. Also, they are spreading the message that noone working within #Calckey or #Misskey is interested in making things better, effectively spreading the (mis)information that there's no interest in the community for improvement and therefore one does not even need to try to attempt to resolve the problems by contacting anyone and therefore they frame it as a "done thing" rather than acknowledging that everything is a work in progress and people are invested in doing the work and making things better for everyone - if they can.

It's particularly galling when there are folks here on #Calckey, and those who are new to it who are pushing for much of the #fediverse culture that prevailed prior to the Great Migration, that has been overtaken by birdsite culture colonisers on many large #Mastodon instances. And many of us who want to see more safety tools built into our protocols & platforms.

Yes, I think there's some issues with the promotion of #Calckey features rather than devs working on safety tools, but that's a widespread fediverse issue that affects all platforms and third-party apps. I've done a bit of my own turn around about that and I've been pushing quite strongly in public and private conversations with the devs & flagship instance mods, raising many of the issues that @[email protected] and have others have been raising in the large, public conversations about the lack of built-in safety tools on Mastodon. I've been encouraging them to look at these conversations and challenging them how they really do need to be thinking about safety tools much more. Check my posts for receipts.

1/2
#fediblockmeta #fediblockdiscussion

I'm quite disappointed to see that solarpunk.moe has decided to unilaterally limit or defed notable #calckey instances. The largest of which has a users count around 2000. I'm particularly sad that our #queer #trans instance of 220 users at blahaj.zone is included.

Let me state I'm not an admin or mod at blahaj.zone It really sucks to find out after the blocks and limits are in place through a public post, and the first opportunity our admins get to publicly reply won't be seen or engaged with.

It feels like they're not looking to solve anything, rather to stir up shit as they've effectively shut out everyone who could take their concerns seriously AND change things in order to make things better for them and everyone in general. Also, they are spreading the message that noone working within #Calckey or #Misskey is interested in making things better, effectively spreading the (mis)information that there's no interest in the community for improvement and therefore one does not even need to try to attempt to resolve the problems by contacting anyone and therefore they frame it as a "done thing" rather than acknowledging that everything is a work in progress and people are invested in doing the work and making things better for everyone - if they can.

It's particularly galling when there are folks here on #Calckey, and those who are new to it who are pushing for much of the #fediverse culture that prevailed prior to the Great Migration, that has been overtaken by birdsite culture colonisers on many large #Mastodon instances. And many of us who want to see more safety tools built into our protocols & platforms.

Yes, I think there's some issues with the promotion of #Calckey features rather than devs working on safety tools, but that's a widespread fediverse issue that affects all platforms and third-party apps. I've done a bit of my own turn around about that and I've been pushing quite strongly in public and private conversations with the devs & flagship instance mods, raising many of the issues that @[email protected] and have others have been raising in the large, public conversations about the lack of built-in safety tools on Mastodon. I've been encouraging them to look at these conversations and challenging them how they really do need to be thinking about safety tools much more. Check my posts for receipts.

1/2
#fediblockmeta #fediblockdiscussion