#occultism — Public Fediverse posts

“Graphy of the cosmic Od.” (1913) by Hippolyte Baraduc, from The Human Soul.

Source: Boston Public Library / Internet Archive

https://pdimagearchive.org/images/88872994-86da-4d7d-8a83-32986bfb3d30

#abstract #electricity #spirituality #soul #spirits #occultism #electromagnetism #auras #photography #art #publicdomain

“Graphy of the cosmic Od.” (1913) by Hippolyte Baraduc, from The Human Soul.

Source: Boston Public Library / Internet Archive

https://pdimagearchive.org/images/88872994-86da-4d7d-8a83-32986bfb3d30

#abstract #electricity #spirituality #soul #spirits #occultism #electromagnetism #auras #photography #art #publicdomain

“Graphy of the cosmic Od.” (1913) by Hippolyte Baraduc, from The Human Soul.

Source: Boston Public Library / Internet Archive

https://pdimagearchive.org/images/88872994-86da-4d7d-8a83-32986bfb3d30

#abstract #electricity #spirituality #soul #spirits #occultism #electromagnetism #auras #photography #art #publicdomain

“Graphy of the cosmic Od.” (1913) by Hippolyte Baraduc, from The Human Soul.

Source: Boston Public Library / Internet Archive

https://pdimagearchive.org/images/88872994-86da-4d7d-8a83-32986bfb3d30

#abstract #electricity #spirituality #soul #spirits #occultism #electromagnetism #auras #photography #art #publicdomain

“Graphy of the cosmic Od.” (1913) by Hippolyte Baraduc, from The Human Soul.

Source: Boston Public Library / Internet Archive

https://pdimagearchive.org/images/88872994-86da-4d7d-8a83-32986bfb3d30

#abstract #electricity #spirituality #soul #spirits #occultism #electromagnetism #auras #photography #art #publicdomain

@cloudskater wrote:

Some instances are run by bad people. Hell, a few projects like Lemmy and Matrix are DEVELOPED by assholes, but the FLOSS and federated nature of these platforms allows us to bypass/fork them and create healthy spaces outside their reach.

Nope, that is actually what is killing the fediverse. I just explained here:

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.

https://neon-blue-demon-wyrm.x10.network/archives/16932

FYI, I’m not doing culture wars or political debates. I’m just saying this idea of “forking away” from them is literally breaking the fediverse’s distributed network and creating all kinds of issues with semantic interoperability. Yes, federation is still happening at the delivery level, but the semantic issues are out of fucking control. You are a federation by the very sheer skin of your teeth.

The reason why developers are leaving the fediverse is because you folks don’t take criticism. You respond to criticism with — I’m being so serious right now — political manifestos and harassing developers. ActivityPub developers and authors oversold you folks on the capabilities of ActivityStreams. They flat-out lied to y’all.

↬bark.lgbt/@cloudskater/116080965694723006

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.

Arcanvm Podcast

#AntennaPod

https://antennapod.org/deeplink/subscribe/?url=%68%74%74ps%3A%2F%2Fanchor.fm%2Fs%2Fd941c6c8%2Fpodcast%2Frss&title=Arcanvm+Podcast

> Arcanvm Podcast sets the table for real discussions with practitioners, scholars, and researchers in the fields of spirituality, ceremonial magic, occultism, and more. Practitioner and author Ike Baker hosts discussions spanning the spectrum of the occult, and esoteric. For more visit: ikebaker.com

https://anchor.fm/s/d941c6c8/podcast/rss
#spirituality #CeremonialMagic, #occultism #occult #esoteric

We really need to stop calling obvious schizophrenia, manic delusions, and psychosis ‘unverified personal gnosis.’ A person whom I knew 15 years ago has persistent beliefs, regardless of facts, that they knew me in a past life and we made some pact to alter the future to save the world from Nazis. It’s insane, but everyone in the occult Discord is nodding their heads and validating it.

A delusion is a persistent belief regardless of facts. This person has dreams and hallucinations that they believe are gods, spirits, and telepathy. In these hallucinations and delusions, the spirits tell them who random strangers were in a past life. A lot of these delusions are obviously paranoid and inevitably roll into a conspiracy theory about Nazis. This is very terrifying. This means, based on a random occurrence with a person, they will create a parasocial narrative that manifests as them knowing this person.

Most schizophrenia delusions emerge from noise and thus have no actual information. You can uncover that it is a delusion by asking the person for details. For example, if they make a claim about remembering a past life in Egypt, you can do the equivalent of asking them who the President of the United States is now. I did that with this person. They were claiming to have known me and other people in a past life in Egypt 3000 years ago, so I looked up what was going on around that time. I asked them who the high priest was, who the pharaoh was, and what they remember happening around that time. All of it was wrong.

That caused most of that Discord to jump all over me and imply that it was fine because it was their personal gnosis. To be clear, this person is creating parasocial relationships and narratives based on delusional narratives that they are applying to random people they meet.

Phrasing things as they happened in a different reality or a past life is a way to avoid the falsification of and is a way to rationalize the delusion. Claiming that you knew a person in a past life is a way to justify the parasocial relationship. It is not unverified personal gnosis. It’s mental illness. There is nothing magical about mental illness. If I had a nickel for every time a schizophrenic occultist spun up a delusional narrative to justify an adversarial parasocial relationship with me, I’d be rich. This is a major problem.

#anarchism #anarchists #anarchy #animistic #Astral #astrological #Bipolar #BipolarDisorder #ceremonialMagic #ceremonialMagick #chaosMagic #chaosMagick #conspiracyTheories #conspiracyTheory #cult #cults #Discord #divination #DKMU #Egypt #fascism #gnosis #magic #magick #Nazi #Nazis #occult #occultism #occulture #pagan #paganism #paranormal #pastLife #pastLives #polytheism #psychic #psychosis #Reddit #reincarnation #schizophrenia #schizophrenic #spirits #spiritual #Spirituality #Theism #Thelema #thelemites #Threads #Twitter #UnverifiedPersonalGnosis #UPG #witch #witchcraft

@MalignusCeles https://youtu.be/kEDZZin4_eM

#DawnOfTheMachineElves #chaosmagic #Discordianism #dkmu #Hexorian #SigilBomb #chaosmagick #magick #divination #tarot #tarotcards #occult #pagan #paganism #sigils #sigilmagick #ceremonialmagic #ceremonialmagick #occultism #occulture

[a metabolic apparatus for cosmogenesis]

thinking-with. chance operations & #weird irruptions. found/stolen gems (& found/forged keys). misreads/misoverheards. ritual relics.

riffs, amplifications, collaborations. rearranging debris. playing past the edge of thought.

#transdisciplinary: #ExpressiveArts, #theory, #speculative. #posthuman & #nonhuman -ism. #occultism/s. #SiteSpecific. #narrative.

[explore • experiment • express]