Quixoticgeek
boosted
That about sums up MAGA vs everybody else.
That about sums up MAGA vs everybody else.
@reiver ⊼ (Charles) :batman:
and 1 other
boosted
ActivityPub Server’s Custom Reply‑Control Extensions Undermine Federation
It seems like Activitbypub developers are extending ActivityPub with optional metadata to fix a lot of its issues, but that is still problematic. Trying to add moderation tools and user control to threads seems to be the ongoing battle. I am fascinated by dumpster fires, so I’ve started looking at the ActivityPub protocol in detail. I tend to become fascinated with things that are going down in flames.
As a brief recap of the problem:
So, one of the very popular features on Bluesky—also popular on Twitter—is the ability to select who can reply to a post. A major issue in the Fediverse is the inability to decide who can reply, and once you block someone, their harassing reply is still there. I honestly thought it was simply a case of them choosing not to add or address it for cultural reasons. What is clear from that thread is that they were always aware that the ActivityPub protocol and most Fediverse implementations don’t provide a universal way to control reply visibility or enforce blocks across instances.
An ActivityPub server that has reply control is GoToSocial. ActivityPub, as defined by the W3C specification, standardizes how servers federate activities. It defines actors, inboxes, outboxes, and activity types (Create, Follow, Like, Announce, etc.) expressed using ActivityStreams 2.0. It also specifies delivery mechanics (including how a Create activity reaches another server’s inbox) and how collections behave.
The specification does not include interaction policy semantics such as “only followers may reply” or “replies require manual approval.” There is no field in the normative vocabulary requiring conforming servers to enforce reply permissions. That category of rule is outside the protocol’s defined contract.
GoToSocial implements reply controls through what it calls interaction policies. These appear as additional properties on ActivityStreams objects using a custom JSON-LD namespace controlled by the GoToSocial project.
JSON-LD permits additional namespaced terms. This means the document remains structurally valid ActivityStreams and federates normally. The meaning of those custom fields, however, comes from GoToSocial’s own documentation and implementation. Other servers can ignore them without violating ActivityPub because they are not part of the interoperable core vocabulary.
Enforcement occurs locally. When a remote server sends a reply—a Create activity whose object references another via inReplyTo—ActivityPub governs delivery, not acceptance criteria. Whether the receiving server checks a reply policy, rejects the activity, queues it, or displays it is determined in the server’s inbox-processing code. The decision to accept, display, or require approval happens after successful protocol-level delivery. This behavior belongs to the application layer.
These are server-side features layered on top of ActivityPub’s transport and data model that are not actually part of ActivityPub. The protocol ensures standardized delivery of activities; however, the server implementation defines additional constraints and user-facing behavior. Two GoToSocial instances may both recognize and act on the same extension fields. However, a different implementation, such as Mastodon, has no obligation under the specification to interpret or enforce GoToSocial’s interactionPolicy properties. These fields function as extension metadata rather than protocol requirements.
The semantics of GoToSocial are not part of the specification’s defined vocabulary and processing rules for ActivityPub. They no longer operate purely at the protocol layer; it has become an application-layer contract implemented by specific servers.
Let’s use the AT Protocol as an example. Bluesky’s direct messages (DMs) are not currently part of the AT Protocol (ATProto). The AT Protocol has nothing that specifies anything for DMs, so DMs are not part of the AT Protocol. The AT Protocol was designed to handle public social interactions, but it does not define private or encrypted messaging. Bluesky implemented DMs at the application level, outside of the core protocol. DMs are centralized and stored on Bluesky’s servers. What is happening with servers like GoToSocial is sort of like that. The difference is that the AT Protocol was designed for different app views; ActivityPub was not.
The issue is the divergence in semantic interpretation that emerges at the interpretation layer. ActivityPub standardizes message delivery and defines common activity types. However, it leaves extension semantics and application-layer policy decisions to individual implementations. Servers may introduce custom JSON-LD namespaces and enforce local behaviors, such as reply restrictions, while remaining protocol-compliant. But, the noise created by divergences are problematic, because it creates unexpected, unintended, and unpredictable behavior.
Divergence appears when implementations rely on non-normative metadata and assume reciprocal handling to preserve a consistent user experience. Behavioral alignment then varies. Syntactic exchange succeeds, but behavioral consistency is not guaranteed. Though instances continue to federate at the transport level, policy semantics and processing logic differ across deployments. Those differences produce inconsistent experiences and results between implementations.
That leads to fragmentation, specifically semantic or behavioral fragmentation and an inconsistent user experiences. ActivityPub ensures syntactic interoperability, but semantic interoperability (everyone interprets and enforces rules the same way) varies. This creates a system that is federated at the transport level yet fragmented in behavior and expectations across implementations. It is funny how the thing that the fediverse touted has made the entire thing very brittle. ActivityPub technically federates correctly, but semantically falls apart once servers start adding their own behavioral rules.
ActivityPub Server’s Custom Reply‑Control Extensions Undermine Federation
It seems like Activitbypub developers are extending ActivityPub with optional metadata to fix a lot of its issues, but that is still problematic. Trying to add moderation tools and user control to threads seems to be the ongoing battle. I am fascinated by dumpster fires, so I’ve started looking at the ActivityPub protocol in detail. I tend to become fascinated with things that are going down in flames.
As a brief recap of the problem:
So, one of the very popular features on Bluesky—also popular on Twitter—is the ability to select who can reply to a post. A major issue in the Fediverse is the inability to decide who can reply, and once you block someone, their harassing reply is still there. I honestly thought it was simply a case of them choosing not to add or address it for cultural reasons. What is clear from that thread is that they were always aware that the ActivityPub protocol and most Fediverse implementations don’t provide a universal way to control reply visibility or enforce blocks across instances.
An ActivityPub server that has reply control is GoToSocial. ActivityPub, as defined by the W3C specification, standardizes how servers federate activities. It defines actors, inboxes, outboxes, and activity types (Create, Follow, Like, Announce, etc.) expressed using ActivityStreams 2.0. It also specifies delivery mechanics (including how a Create activity reaches another server’s inbox) and how collections behave.
The specification does not include interaction policy semantics such as “only followers may reply” or “replies require manual approval.” There is no field in the normative vocabulary requiring conforming servers to enforce reply permissions. That category of rule is outside the protocol’s defined contract.
GoToSocial implements reply controls through what it calls interaction policies. These appear as additional properties on ActivityStreams objects using a custom JSON-LD namespace controlled by the GoToSocial project.
JSON-LD permits additional namespaced terms. This means the document remains structurally valid ActivityStreams and federates normally. The meaning of those custom fields, however, comes from GoToSocial’s own documentation and implementation. Other servers can ignore them without violating ActivityPub because they are not part of the interoperable core vocabulary.
Enforcement occurs locally. When a remote server sends a reply—a Create activity whose object references another via inReplyTo—ActivityPub governs delivery, not acceptance criteria. Whether the receiving server checks a reply policy, rejects the activity, queues it, or displays it is determined in the server’s inbox-processing code. The decision to accept, display, or require approval happens after successful protocol-level delivery. This behavior belongs to the application layer.
These are server-side features layered on top of ActivityPub’s transport and data model that are not actually part of ActivityPub. The protocol ensures standardized delivery of activities; however, the server implementation defines additional constraints and user-facing behavior. Two GoToSocial instances may both recognize and act on the same extension fields. However, a different implementation, such as Mastodon, has no obligation under the specification to interpret or enforce GoToSocial’s interactionPolicy properties. These fields function as extension metadata rather than protocol requirements.
The semantics of GoToSocial are not part of the specification’s defined vocabulary and processing rules for ActivityPub. They no longer operate purely at the protocol layer; it has become an application-layer contract implemented by specific servers.
Let’s use the AT Protocol as an example. Bluesky’s direct messages (DMs) are not currently part of the AT Protocol (ATProto). The AT Protocol has nothing that specifies anything for DMs, so DMs are not part of the AT Protocol. The AT Protocol was designed to handle public social interactions, but it does not define private or encrypted messaging. Bluesky implemented DMs at the application level, outside of the core protocol. DMs are centralized and stored on Bluesky’s servers. What is happening with servers like GoToSocial is sort of like that. The difference is that the AT Protocol was designed for different app views; ActivityPub was not.
The issue is the divergence in semantic interpretation that emerges at the interpretation layer. ActivityPub standardizes message delivery and defines common activity types. However, it leaves extension semantics and application-layer policy decisions to individual implementations. Servers may introduce custom JSON-LD namespaces and enforce local behaviors, such as reply restrictions, while remaining protocol-compliant. But, the noise created by divergences are problematic, because it creates unexpected, unintended, and unpredictable behavior.
Divergence appears when implementations rely on non-normative metadata and assume reciprocal handling to preserve a consistent user experience. Behavioral alignment then varies. Syntactic exchange succeeds, but behavioral consistency is not guaranteed. Though instances continue to federate at the transport level, policy semantics and processing logic differ across deployments. Those differences produce inconsistent experiences and results between implementations.
That leads to fragmentation, specifically semantic or behavioral fragmentation and an inconsistent user experiences. ActivityPub ensures syntactic interoperability, but semantic interoperability (everyone interprets and enforces rules the same way) varies. This creates a system that is federated at the transport level yet fragmented in behavior and expectations across implementations. It is funny how the thing that the fediverse touted has made the entire thing very brittle. ActivityPub technically federates correctly, but semantically falls apart once servers start adding their own behavioral rules.
Jess Mahler
boosted
RE: https://zirk.us/@StingrayBadger/116051712358302193
UK folks in the mood for a little bit of armchair activism, search online for your local library and check if the catalogue contains this book.
If it does, contact your library and ask them to remove it. The article below has some talking points.
If you're in the UK please write to your local library & ask them to remove this #Transphobic book which encourages parents to invalidate gender exploring kids. Mention safeguarding children in your email.
I wrote to my local library and got a personalised response, to thank me for highlighting this, and they are taking action.
CW for article which outlines some transphobic content in the book
RE: https://zirk.us/@StingrayBadger/116051712358302193
UK folks in the mood for a little bit of armchair activism, search online for your local library and check if the catalogue contains this book.
If it does, contact your library and ask them to remove it. The article below has some talking points.
If you're in the UK please write to your local library & ask them to remove this #Transphobic book which encourages parents to invalidate gender exploring kids. Mention safeguarding children in your email.
I wrote to my local library and got a personalised response, to thank me for highlighting this, and they are taking action.
CW for article which outlines some transphobic content in the book
n8chz 🩎
boosted
Deactivated.
Had a conversation with a pinside mod who affirmed that transphobia is acceptable because "it's not political", and saying anything against transphobia IS political and needs to be deleted for the sake of the #pinside community.
#pinball #transphobia #longestsighever
Deactivated.
Had a conversation with a pinside mod who affirmed that transphobia is acceptable because "it's not political", and saying anything against transphobia IS political and needs to be deleted for the sake of the #pinside community.
#pinball #transphobia #longestsighever
Looks like Anas Sarwar is going full transhpobe in an effort to win in Holyrood. Time to stand up against hate.
Anyone have a good guide on how to get the most pro indy and actually left leaning people into Holyrood this May? (I'm thinking it might be SNP in the constituency and@ScottishGreens@mastodon.scot on the regional list)
ClickBen(t)
boosted
You cannot debate these cunts. They will gnash and wail and claim victimhood over your very existence.
Cut them off, push them away, delete X, live a life without caring what those bastards think.
And note, once again, that the TERFS and the fascists are walking in lockstep. #transphobia
Worth noting that one of the two writers of Six is non-binary, and it has always had a diverse cast of women and non-binary people of various races and body types, the wives’ characters and songs being inspired by various singers such as Beyoncé, Rihanna and Nicki Minaj. The programme lists their pronouns
So whilst this is not a big deal, it *especially* should not be a big deal in that context.
It is not like Six has suddenly Gone Woke, having always been Woke As Fuck.
AND YET:
You cannot debate these cunts. They will gnash and wail and claim victimhood over your very existence.
Cut them off, push them away, delete X, live a life without caring what those bastards think.
And note, once again, that the TERFS and the fascists are walking in lockstep. #transphobia
100% agree. This is the distinction between what most Black folk see as Trump's impact, vs most white folk.
Many Black folk see it as a "mask off" moment. Many white folk see it as a "People's underlying feelings have been swayed by Trump/social media/algorithms!" But no.
The difference is important. Because without Trump, the underlying feelings and actions, were still there.
And as a Black person, I have to say that I much prefer the mask off racists to the mask on racists. My view is: "If you don't like me, just say that, and we can get right into it."
This is also the reason why the supposed logical dilemma of "Would you go back in time and kill baby Hitler?" is not a dilemma at all.🤷🏿♂️ The answer is "No. Don't kill babies. What's wrong with you?" And also, "No, because you wouldn't be preventing anything."
Hitler was not a good writer, or a powerful speaker, or even particularly persuasive. It's not how he was saying it. It's that what he was saying already resonated with fascists and antisemites. If it weren't him, it would have just been someone else. The problem wasn't Hitler. The problem was about 30 million of the 80 million Germans.
This. I'm white and disabled. Not the same space, but a similar one. It's easier to deal with the devil in the light than the devil in the dark.
In the case of my ex, I hadn't known I'd married a racist because we were privileged to live where the racism was not in view. MAGA 1.0 was when I learned. It was the motivating factor in my decision to end the marriage.
I can't really describe this well, but it's also part of why I'm not in any hurry to haul my #transgender ass out of #Texas. Because I know how to survive here, where the bigotry is overt.
It's like the difference between concealed carry and open carry. In #TX, people openly carry their #transphobia and #homophobia. I don't know how to live where this bigotry is concealed carry.
Freedom News: **Have you SEEN workplace transphobia?**
https://freedomnews.org.uk/2026/01/15/have-you-seen-workplace-transphobia/
SolFed investigates 21 groups pushing “fake feminism and liberal civility” across sectors ~ Scott Harris ~ Solidarity Federation has …
The post Have you SEEN workplace transphobia? appeared first on Freedom News.
#News #Solfed #TERFs #Transphobia #Workplace
For the longest time I have been puzzled by the fact that so many women in the MAGA movement are so overly obsessed with their looks — to the point where surgery is involved.
This ex-MAGA woman explains why. I recommend looking past the fact that the video is somewhat unpolished, because her points are solid.
Welcome to the botox MAGA prison, where women have zero value and being a sex doll status symbol for men is all that matters:
https://youtu.be/6dbF5eub05o?si=VxTyGfgpexcZTTS0
Thanks for sharing @macberg
Wow. Yes. Oh man.
This young woman absolutely nails the #MAGA + #patriarchy + #mysoginy + #religiosity + #capitalism + #TransPhobia + #HyperMasculinity
Old white guy here .. raised in #evangelical #fundamentalism
I have spent the bulk of my life recovering from that background.
Billy Smith
boosted
They're erasing us Queers from public life again and the Oligarchs are behind it.
How many Straight allies are there? Are there enough? Palestine has plenty of allies around the world, yet they're still being erased....
#Pride #Homophobia #Queerphobia #Transphobia #Oligarchs #LGBTQIA #Fascism
They're erasing us Queers from public life again and the Oligarchs are behind it.
How many Straight allies are there? Are there enough? Palestine has plenty of allies around the world, yet they're still being erased....
#Pride #Homophobia #Queerphobia #Transphobia #Oligarchs #LGBTQIA #Fascism
Chip Butty
boosted
kinda crazy that we had an entire nationwide panic over fake "satanic ritual abuse" but it's a known fact that christian families regularly bully their queer / neurodivergent / etc kids to suicide and we all just collectively shrug our shoulders whenever it's brought up
Your disabled PoC admin is in need of a computer Please assist if you're able ❤️ Deets in the comments #meme #memes #queer #rowling #jkrowling #transphobia
tools for commensality 🧿
boosted
If you're not familiar with the 1965 Moynihan Report and how the literal U.S. government was like "the actual problem of the Black community is that the women emasculate the men,"
if you're not familiar with how this antiblack settler colonial nation used the concept of "emasculation" to gaslight Black Americans about the source of our oppression being Black women rather than the white cishet patriarchy,
I don't wanna hear a defense of the term "transemasculation." Cause you're facilitating some antiblack genocidal logics with the use of that term and your cavalier engagement with Black feminism and Black history is the root cause.