#streamofconsciousness — Public Fediverse posts

✮ Fear ✮

Subscribe to keep reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

✮ Fear ✮

Subscribe to keep reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

✮ Fear ✮

Subscribe to keep reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

✮ Fear ✮

Subscribe to keep reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

✮ Fear ✮

Subscribe to keep reading

Become a paid subscriber to get access to the rest of this post and other exclusive content.

Nessuno che scrive qui?

Ad esempio in un posto pulito come questo, mi piacerebbe scrivere una #poesia a catena, #versiliberi dettati da puro #StreamOfConsciousness. Chi vuole partecipare ? Lascio il post qui, poi chi ne prende parte, commenta, 𝐫𝐚𝐜𝐜𝐨𝐥𝐠𝐨 𝐥𝐞 𝐚𝐝𝐞𝐬𝐢𝐨𝐧𝐢* e si comincia raggiunto un 5-6 persone che dite ? 👀

#scritturacreativa #flussodicoscienza

Nessuno che scrive qui?

Ad esempio in un posto pulito come questo, mi piacerebbe scrivere una #poesia a catena, #versiliberi dettati da puro #StreamOfConsciousness. Chi vuole partecipare ? Lascio il post qui, poi chi ne prende parte, commenta, 𝐫𝐚𝐜𝐜𝐨𝐥𝐠𝐨 𝐥𝐞 𝐚𝐝𝐞𝐬𝐢𝐨𝐧𝐢* e si comincia raggiunto un 5-6 persone che dite ? 👀

#scritturacreativa #flussodicoscienza

Is sugar a vegetable? This an other perennial questions anwered:

Show 884: Misdemeanour Gang Tattoos And The Trolley Problem -Into Your Head #podcast

https://intoyourhead.ie/2026/06/09/show-884-misdemeanour-gang-tattoos-and-the-trolley-problem/

#absurdist #humour #Irish #comedy #podcasters #streamofconsciousness

Is sugar a vegetable? This an other perennial questions anwered:

Show 884: Misdemeanour Gang Tattoos And The Trolley Problem -Into Your Head #podcast

https://intoyourhead.ie/2026/06/09/show-884-misdemeanour-gang-tattoos-and-the-trolley-problem/

#absurdist #humour #Irish #comedy #podcasters #streamofconsciousness

Is sugar a vegetable? This and other perennial questions answered:

Show 884: Misdemeanour Gang Tattoos And The Trolley Problem -Into Your Head #podcast

https://intoyourhead.ie/2026/06/09/show-884-misdemeanour-gang-tattoos-and-the-trolley-problem/

#absurdist #humour #Irish #comedy #podcasters #streamofconsciousness

https://goblackcat.com/working-second-shift/

#journal #writing #streamofconsciousness

https://goblackcat.com/working-second-shift/

#journal #writing #streamofconsciousness

The Shorts Omnibus Volume 6

Another non-stop omnibus for people who don't like video shorts. From Into Your Head #podcast #streamofconsciousness #humour #comedypodcasts #shorts #humor

https://intoyourhead.ie/2026/04/18/the-shorts-omnibus-volume-6/

The Shorts Omnibus Volume 6

Another non-stop omnibus for people who don't like video shorts. From Into Your Head #podcast #streamofconsciousness #humour #comedypodcasts #shorts #humor

https://intoyourhead.ie/2026/04/18/the-shorts-omnibus-volume-6/

idle brain – the sin of being born

https://ridiculousbharath.wordpress.com/2026/04/18/idle-brain-the-sin-of-being-born/

Video Shorts 222: Excessive Control of Prison Yards and Imaginary Baseball

Excessive Control of Prison Yards and Imaginary Baseball (Video Shorts 222) from Into Your Head podcast - IntoYourHead.ie #comedypodcasts #streamofconsciousness #humour #prisonlife #basketball #prison

https://intoyourhead.ie/2026/04/16/video-shorts-222-excessive-control-of-prison-yards-and-imaginary-baseball/

Video Shorts 222: Excessive Control of Prison Yards and Imaginary Baseball

Excessive Control of Prison Yards and Imaginary Baseball (Video Shorts 222) from Into Your Head podcast - IntoYourHead.ie #comedypodcasts #streamofconsciousness #humour #prisonlife #basketball #prison

https://intoyourhead.ie/2026/04/16/video-shorts-222-excessive-control-of-prison-yards-and-imaginary-baseball/

Video Shorts 222: Excessive Control of Prison Yards and Imaginary Baseball

Excessive Control of Prison Yards and Imaginary Baseball (Video Shorts 222) from Into Your Head podcast - IntoYourHead.ie #comedypodcasts #streamofconsciousness #humour #prisonlife #basketball #prison

https://intoyourhead.ie/2026/04/16/video-shorts-222-excessive-control-of-prison-yards-and-imaginary-baseball/

Video Shorts 222: Excessive Control of Prison Yards and Imaginary Baseball

Excessive Control of Prison Yards and Imaginary Baseball (Video Shorts 222) from Into Your Head podcast - IntoYourHead.ie #comedypodcasts #streamofconsciousness #humour #prisonlife #basketball #prison

https://intoyourhead.ie/2026/04/16/video-shorts-222-excessive-control-of-prison-yards-and-imaginary-baseball/

Video Shorts 221: What the Hell Does Society WANT, Anyway?

What the Hell Does Society WANT, Anyway? from Into Your Head podcast - IntoYourHead.ie #comedypodcasts #streamofconsciousness #philosophy mindblown #absurdist

https://intoyourhead.ie/2026/04/14/video-shorts-221-what-the-hell-does-society-want-anyway/

Video Shorts 219: Stubbing Your Toe Won’t Necessarily Ruin Your Life Permanently.

Hear me out. from Into Your Head podcast - IntoYourHead.ie #IrishPodcasts #humour #podcastclips #positivity #feet #streamofconsciousness

https://intoyourhead.ie/2026/04/10/video-shorts-219-stop-worrying-stubbing-your-toe-will-not-neccessarily-ruin-your-life-permanently-from-into/

Video Shorts 219: Stubbing Your Toe Won’t Necessarily Ruin Your Life Permanently.

Hear me out. from Into Your Head podcast - IntoYourHead.ie #IrishPodcasts #humour #podcastclips #positivity #feet #streamofconsciousness

https://intoyourhead.ie/2026/04/10/video-shorts-219-stop-worrying-stubbing-your-toe-will-not-neccessarily-ruin-your-life-permanently-from-into/

Spring Stream-of-Consciousness: Emerging from the Quiet

https://jaimedavid.blog/2026/04/01/08/28/00/short-story/jaimedavid27/3327/spring-stream-of-consciousness-emerging-from-the-quiet/

#UntiltedComicStrip 118 is available at:

1. #BuyMeACoffee
https://buymeacoffee.com/untilted/gallery/4595900

2. #ComicFury
https://untilted.webcomic.ws/comics/118/

Yeah.

Untilted © 2026 by Cam R. is licensed under CC BY-ND 4.0 :cc_cc: :cc_by: :cc_nd: and #NoAI is used ever! :noAI:

:boost_ok: and/or ⭐, maybe even comment! Follow me for updates if you want - no pressure. (I shouldn't have to say that last part :BlobCat_NervousSweating: )

#Webcomic #ComicStrip #Comics #Abstract #Cartoon #StreamOfConsciousness

A raw report in accountability

Will admitting my lie    receiver of pain  I’m not finding inspiration in the creased skin of a chance any longer… Memory of love arrives in the desert   …

There is where   a care and not   such a dare    just  down the road  past hells painted face paces  faintly  bland boring foursome  fantasy

All is consumed that which was craved and most likely killed.  One simple statement…

I am here and in fear of where I’ve been. Fuck my writing panic sin incisions floss crutch skinless demons color for a queen finally fades behind the curtain  that seems like eyelid code   yell a bloated ‘yahoo!’ into the void  implodes and my espionage parade begins

A raw report in accountability

Will admitting my lie    receiver of pain  I’m not finding inspiration in the creased skin of a chance any longer… Memory of love arrives in the desert   …

There is where   a care and not   such a dare    just  down the road  past hells painted face paces  faintly  bland boring foursome  fantasy

All is consumed that which was craved and most likely killed.  One simple statement…

I am here and in fear of where I’ve been. Fuck my writing panic sin incisions floss crutch skinless demons color for a queen finally fades behind the curtain  that seems like eyelid code   yell a bloated ‘yahoo!’ into the void  implodes and my espionage parade begins

#UntiltedComicStrip 117 is available at:

1. #BuyMeACoffee
https://buymeacoffee.com/untilted/gallery/4586273

2. #ComicFury
https://untilted.webcomic.ws/comics/117/

Untilted © 2026 by Cam R. is licensed under CC BY-ND 4.0 :cc_cc: :cc_by: :cc_nd: and #NoAI is used ever! :noAI:

:boost_ok: and/or ⭐, maybe even comment! Follow me for updates if you want - no pressure. (I shouldn't have to say that last part :BlobCat_NervousSweating: )

Contains a very bad pun.

#Webcomic #ComicStrip #Comics #Abstract #Cartoon #StreamOfConsciousness

@comics
@webcomics

#UntiltedComicStrip 116 is available at:

1. #BuyMeACoffee
https://buymeacoffee.com/untilted/gallery/4577883

2. #ComicFury
https://untilted.webcomic.ws/comics/116/

See alt text for details.

Untilted © 2026 by Cam R. is licensed under CC BY-ND 4.0 :cc_cc: :cc_by: :cc_nd: and #NoAI is used ever! :noAI:

:boost_ok: and/or ⭐, maybe even comment! (and maybe follow me for updates - I could use some support)

#Webcomic #ComicStrip #Comics #Abstract #Cartoon #StreamOfConsciousness #Beach #Waves #Water

Touched one of my OSS issue trackers and suffered some psychic damage as a result. Oops.

Doesn't help that I am a bit sensitive rn; I've been able to work out a switch to a devops role at work, which is more my speed than feature development has been. But we've got a dedicated developer-experience person starting in a monthish, and like. insofar as that's even a role that exists, it's /my jam/.

I'm terrified he'll be all "wow, what's this shitty bespoke CLI tool you're using, you should switch to $alternative".

Anyway BTW I PROBABLY HAVE A THERAPIST NOW so maybe that will help. Unless she recommends I just quit OSS for my mental health 😬

#Oversharing #TMI #StreamOfConsciousness #Hashtags

Touched one of my OSS issue trackers and suffered some psychic damage as a result. Oops.

Doesn't help that I am a bit sensitive rn; I've been able to work out a switch to a devops role at work, which is more my speed than feature development has been. But we've got a dedicated developer-experience person starting in a monthish, and like. insofar as that's even a role that exists, it's /my jam/.

I'm terrified he'll be all "wow, what's this shitty bespoke CLI tool you're using, you should switch to $alternative".

Anyway BTW I PROBABLY HAVE A THERAPIST NOW so maybe that will help. Unless she recommends I just quit OSS for my mental health 😬

#Oversharing #TMI #StreamOfConsciousness #Hashtags

Touched one of my OSS issue trackers and suffered some psychic damage as a result. Oops.

Doesn't help that I am a bit sensitive rn; I've been able to work out a switch to a devops role at work, which is more my speed than feature development has been. But we've got a dedicated developer-experience person starting in a monthish, and like. insofar as that's even a role that exists, it's /my jam/.

I'm terrified he'll be all "wow, what's this shitty bespoke CLI tool you're using, you should switch to $alternative".

Anyway BTW I PROBABLY HAVE A THERAPIST NOW so maybe that will help. Unless she recommends I just quit OSS for my mental health 😬

#Oversharing #TMI #StreamOfConsciousness #Hashtags

Touched one of my OSS issue trackers and suffered some psychic damage as a result. Oops.

Doesn't help that I am a bit sensitive rn; I've been able to work out a switch to a devops role at work, which is more my speed than feature development has been. But we've got a dedicated developer-experience person starting in a monthish, and like. insofar as that's even a role that exists, it's /my jam/.

I'm terrified he'll be all "wow, what's this shitty bespoke CLI tool you're using, you should switch to $alternative".

Anyway BTW I PROBABLY HAVE A THERAPIST NOW so maybe that will help. Unless she recommends I just quit OSS for my mental health 😬

#Oversharing #TMI #StreamOfConsciousness #Hashtags

Touched one of my OSS issue trackers and suffered some psychic damage as a result. Oops.

Doesn't help that I am a bit sensitive rn; I've been able to work out a switch to a devops role at work, which is more my speed than feature development has been. But we've got a dedicated developer-experience person starting in a monthish, and like. insofar as that's even a role that exists, it's /my jam/.

I'm terrified he'll be all "wow, what's this shitty bespoke CLI tool you're using, you should switch to $alternative".

Anyway BTW I PROBABLY HAVE A THERAPIST NOW so maybe that will help. Unless she recommends I just quit OSS for my mental health 😬

#Oversharing #TMI #StreamOfConsciousness #Hashtags

What to write in a bio about myself? I’m this, I’m that, BLA BLA BLA — this is how I used to write about myself. I have many hobbies that change all the time. I’m curious. I get obsessed with things. I’m this, I’m that.

But maybe I’m none of these things. Maybe I’m just me — Brett, a human who loves to experience and try on different things. Maybe I’m not any of these things. Maybe I’m just an idea.

#Identity
#SelfReflection
#HumanExperience
#StreamOfConsciousness
#WritingCommunity

What to write in a bio about myself? I’m this, I’m that, BLA BLA BLA — this is how I used to write about myself. I have many hobbies that change all the time. I’m curious. I get obsessed with things. I’m this, I’m that.

But maybe I’m none of these things. Maybe I’m just me — Brett, a human who loves to experience and try on different things. Maybe I’m not any of these things. Maybe I’m just an idea.

#Identity
#SelfReflection
#HumanExperience
#StreamOfConsciousness
#WritingCommunity

What to write in a bio about myself? I’m this, I’m that, BLA BLA BLA — this is how I used to write about myself. I have many hobbies that change all the time. I’m curious. I get obsessed with things. I’m this, I’m that.

But maybe I’m none of these things. Maybe I’m just me — Brett, a human who loves to experience and try on different things. Maybe I’m not any of these things. Maybe I’m just an idea.

#Identity
#SelfReflection
#HumanExperience
#StreamOfConsciousness
#WritingCommunity

What to write in a bio about myself? I’m this, I’m that, BLA BLA BLA — this is how I used to write about myself. I have many hobbies that change all the time. I’m curious. I get obsessed with things. I’m this, I’m that.

But maybe I’m none of these things. Maybe I’m just me — Brett, a human who loves to experience and try on different things. Maybe I’m not any of these things. Maybe I’m just an idea.

#Identity
#SelfReflection
#HumanExperience
#StreamOfConsciousness
#WritingCommunity

What to write in a bio about myself? I’m this, I’m that, BLA BLA BLA — this is how I used to write about myself. I have many hobbies that change all the time. I’m curious. I get obsessed with things. I’m this, I’m that.

But maybe I’m none of these things. Maybe I’m just me — Brett, a human who loves to experience and try on different things. Maybe I’m not any of these things. Maybe I’m just an idea.

#Identity
#SelfReflection
#HumanExperience
#StreamOfConsciousness
#WritingCommunity

My PDS Doesn’t Participate in Bluesky’s Age-Verification Flow

So, apparently, with the last few updates Bluesky has done, they have expanded the regions that need to be age-verified to Ohio, and they are preparing to expand it to Australia. They have also made it so that people don’t have access to DMs or material labeled by Bluesky’s moderation services. I’ve been looking into the age verification system that Bluesky uses as I configure my own PDS. app.bsky.ageassurance.begin is an explicit API call that a client or PDS must intentionally call to start the age-verification process, hand the user off to the verification provider, and receive an updated age-assurance state.

Check here for the official Bluesky documentation:

This endpoint is part of the Bluesky application Lexicon APIs (app.bsky.*). Public endpoints which don’t require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user’s PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.

https://docs.bsky.app/docs/api/app-bsky-ageassurance-begin

If a PDS does not call app.bsky.ageassurance.begin, the age-verification flow does not start. Age verification occurs on the client side, not the server side. If a PDS does not implement the app.bsky.ageassurance.* endpoints, it cannot interact with Bluesky’s age verification flow.

Georgia—where I currently live as of writing this post—does have age restriction and verification laws; however, they are weak, so Bluesky has not had to do much in my state. As a result, I’ve just been using Bluesky’s PDS. However, I have been setting up my own PDS. Since my PDS does not call app.bsky.ageassurance.begin, does not check getState, and does not read getConfig, it has no way to initiate age verification, determine whether a user is verified, or enforce or reflect any age-based restrictions. My PDS does not participate in Bluesky’s age-assurance system at all. That’s just one part of Bluesky’s moderation structure. Bluesky’s moderation services use labelers.

Labels and moderation

https://docs.bsky.app/docs/advanced-guides/moderation

Labelers are services or accounts that apply moderation labels. My PDS does not declare default app labelers, so it does not automatically trust any labelers. I have max user control with the minimum level of automated moderation.

If you do not want to through all of this trouble and want to keep using the native bsky.app, see here:

Bluesky’s age assurance sucks, here’s how to work around it.

https://gist.github.com/mary-ext/6e27b24a83838202908808ad528b3318

I am going to be honest. I hate Bluesky’s political, philosophical, and ideological values, think its moderation is heavily flawed, and am more closely aligned politically with the Fediverse. But… the Fediverse is not fun. It’s essentially people constantly commiserating, with no interesting or entertaining content, peppered with manifestos and “this bad thing happened in the news—be enraged by it” posts. I really wanted to love the Fediverse, but there’s nothing to do over there.

My PDS Doesn’t Participate in Bluesky’s Age-Verification Flow

So, apparently, with the last few updates Bluesky has done, they have expanded the regions that need to be age-verified to Ohio, and they are preparing to expand it to Australia. They have also made it so that people don’t have access to DMs or material labeled by Bluesky’s moderation services. I’ve been looking into the age verification system that Bluesky uses as I configure my own PDS. app.bsky.ageassurance.begin is an explicit API call that a client or PDS must intentionally call to start the age-verification process, hand the user off to the verification provider, and receive an updated age-assurance state.

Check here for the official Bluesky documentation:

This endpoint is part of the Bluesky application Lexicon APIs (app.bsky.*). Public endpoints which don’t require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user’s PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.

https://docs.bsky.app/docs/api/app-bsky-ageassurance-begin

If a PDS does not call app.bsky.ageassurance.begin, the age-verification flow does not start. Age verification occurs on the client side, not the server side. If a PDS does not implement the app.bsky.ageassurance.* endpoints, it cannot interact with Bluesky’s age verification flow.

Georgia—where I currently live as of writing this post—does have age restriction and verification laws; however, they are weak, so Bluesky has not had to do much in my state. As a result, I’ve just been using Bluesky’s PDS. However, I have been setting up my own PDS. Since my PDS does not call app.bsky.ageassurance.begin, does not check getState, and does not read getConfig, it has no way to initiate age verification, determine whether a user is verified, or enforce or reflect any age-based restrictions. My PDS does not participate in Bluesky’s age-assurance system at all. That’s just one part of Bluesky’s moderation structure. Bluesky’s moderation services use labelers.

Labels and moderation

https://docs.bsky.app/docs/advanced-guides/moderation

Labelers are services or accounts that apply moderation labels. My PDS does not declare default app labelers, so it does not automatically trust any labelers. I have max user control with the minimum level of automated moderation.

If you do not want to through all of this trouble and want to keep using the native bsky.app, see here:

Bluesky’s age assurance sucks, here’s how to work around it.

https://gist.github.com/mary-ext/6e27b24a83838202908808ad528b3318

I am going to be honest. I hate Bluesky’s political, philosophical, and ideological values, think its moderation is heavily flawed, and am more closely aligned politically with the Fediverse. But… the Fediverse is not fun. It’s essentially people constantly commiserating, with no interesting or entertaining content, peppered with manifestos and “this bad thing happened in the news—be enraged by it” posts. I really wanted to love the Fediverse, but there’s nothing to do over there.

My PDS Doesn’t Participate in Bluesky’s Age-Verification Flow

So, apparently, with the last few updates Bluesky has done, they have expanded the regions that need to be age-verified to Ohio, and they are preparing to expand it to Australia. They have also made it so that people don’t have access to DMs or material labeled by Bluesky’s moderation services. I’ve been looking into the age verification system that Bluesky uses as I configure my own PDS. app.bsky.ageassurance.begin is an explicit API call that a client or PDS must intentionally call to start the age-verification process, hand the user off to the verification provider, and receive an updated age-assurance state.

Check here for the official Bluesky documentation:

This endpoint is part of the Bluesky application Lexicon APIs (app.bsky.*). Public endpoints which don’t require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user’s PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.

https://docs.bsky.app/docs/api/app-bsky-ageassurance-begin

If a PDS does not call app.bsky.ageassurance.begin, the age-verification flow does not start. Age verification occurs on the client side, not the server side. If a PDS does not implement the app.bsky.ageassurance.* endpoints, it cannot interact with Bluesky’s age verification flow.

Georgia—where I currently live as of writing this post—does have age restriction and verification laws; however, they are weak, so Bluesky has not had to do much in my state. As a result, I’ve just been using Bluesky’s PDS. However, I have been setting up my own PDS. Since my PDS does not call app.bsky.ageassurance.begin, does not check getState, and does not read getConfig, it has no way to initiate age verification, determine whether a user is verified, or enforce or reflect any age-based restrictions. My PDS does not participate in Bluesky’s age-assurance system at all. That’s just one part of Bluesky’s moderation structure. Bluesky’s moderation services use labelers.

Labels and moderation

https://docs.bsky.app/docs/advanced-guides/moderation

Labelers are services or accounts that apply moderation labels. My PDS does not declare default app labelers, so it does not automatically trust any labelers. I have max user control with the minimum level of automated moderation.

If you do not want to through all of this trouble and want to keep using the native bsky.app, see here:

Bluesky’s age assurance sucks, here’s how to work around it.

https://gist.github.com/mary-ext/6e27b24a83838202908808ad528b3318

I am going to be honest. I hate Bluesky’s political, philosophical, and ideological values, think its moderation is heavily flawed, and am more closely aligned politically with the Fediverse. But… the Fediverse is not fun. It’s essentially people constantly commiserating, with no interesting or entertaining content, peppered with manifestos and “this bad thing happened in the news—be enraged by it” posts. I really wanted to love the Fediverse, but there’s nothing to do over there.

BlueSky’s Solution To Moderating Is Moderating Without Moderating via Social Proximity

I have noticed a lot of people are confused about why some posts don’t show up on threads, though they are not labeled by the moderation layer. Bluesky has begun using what it calls social neighborhoods (or network proximity) as a ranking signal for replies in threads. Replies from people who are closer to you in the social graph, accounts you follow, interact with, or share mutual connections with, are prioritized and shown more prominently. Replies from accounts that are farther away in that network are down-ranked. They are pushed far down the thread or placed behind “hidden replies.”

Each person gets their own unique view of a thread based on their social graph. It creates the impression that replies from distant users simply don’t exist. This is true even though they’re still technically public and viewable if you expand the thread or adjust filters. Bluesky is explicitly using features of subgraphs to moderate without moderating. Their reasoning is that if you can’t see each other, you can’t harass each other. Ergo, there is nothing to moderate.

Bluesky mentions that here:

https://bsky.social/about/blog/10-31-2025-building-healthier-social-media-update

As a digression, I’m not going to lie: I really enjoyed working on software built on the AT protocol, but their fucking users are so goddamn weird. It’s sort of like enjoying building houses, but hating every single person who moves into them. But, you don’t have to deal with them because you’re just the contractor. That is how I feel about Bluesky. I hate the people. I really like the protocol and infrastructure.

I sort of am a sadist who does enjoy drama, so I do get schadenfreude from people with social media addictions and parasocial fixations who reply to random people on Bluesky, because they don’t realize their replies are disconnected from the author’s thread unless that person is within their network. They aren’t part of the conversation they think they are. They’re algorithmically isolated from everyone else. Their replies aren’t viewable from the author’s thread because of how Bluesky handles social neighborhoods.

Bluesky’s idea of social neighborhoods is about grouping users into overlapping clusters based on real interaction patterns rather than just the follow graph. Unlike Twitter, it does not treat the network as one big public square. Instead, it models networks of “social neighborhoods” made up of people you follow, people who follow you, people you frequently interact with, and people who are closely connected to those groups. They’re soft, probabilistic groupings rather than strict labels.

Everyone does not see the same replies. Bluesky is being a bit vague with “hidden.” Hidden means your reply is still anchored to the thread and can be expanded. There is another way Bluesky can handle this. Bluesky uses social neighborhoods to judge contextual relevance. Replies from people inside or near your social neighborhood are more likely to be shown inline with a thread, expanded by default, or served in feeds. Replies from outside your neighborhood are still public and still indexed, but they’re treated as lower-context contributions.

Basically, if you reply to a thread, you will see it anchored to the conversation, and everyone will see it in search results, as a hashtag, or from your profile, but it will not be accessible via the thread of the person you were replying to. It is like shadow-banning people from threads unless they are strongly networked.

Because people have not been working with the AT Protocol like I have, they assume they are shadow-banned across the entire Bluesky app view. No—everyone is automatically shadow-banned from everyone else unless they are within the same social neighborhood. In other words, you are not part of the conversation you think you are joining because you are not part of their social group.

Your replies will appear in profiles, hashtag feeds, or search results without being visually anchored to the full thread. Discovery impressions are neighborhood-agnostic: they serve content because it matches a query, tag, or activity stream. Once the reply is shown, the app then decides whether it’s worth pulling in the rest of the conversation for you. If the original author and most participants fall outside your neighborhood, Bluesky often chooses not to expand that context automatically.

Bluesky really is trying to avoid having to moderate, so this is their solution. Instead of banning or issuing takedown labels to DIDs, the system lets replies exist everywhere, but not in that particular instance of the thread.

I find this ironic because a large reason why many people are staying on Bluesky and not moving to the fediverse—thank God, because I do not want them there—is discoverability, virality, and engagement.

In case anyone is asking how I know so much about how these algorithms work: I was a consultant on a lot of these types of algorithms, so I certainly hope I’d know how they work, lol. No, you get no more details about the work I’ve done. I have no hand in the algorithm Bluesky is using, but I have proposed and implemented that type of algorithm before.

I have an interest in noetics and the noosphere. A large amount of my ontological work is an extension of my attempts to model domains that have no spatial or temporal coordinates. The question is how do you generalize a metric space that has no physically, spatial properties. I went to school to try to formalize those ideas. Turns out they’re rather useful for digital social networks, too. The ontological analog to spatial distance, when you have no space, is a graph of similarities.

This can be modeled by representing each item as a node in a weighted graph, where edges are weighted by dissimilarity rather than similarity. Highly similar items are connected by low-weight edges, while less similar items are connected by higher-weight edges. Distances in the graph, computed using standard shortest-path algorithms, then correspond to degrees of similarity. Closely related items are separated by short path lengths, while increasingly dissimilar items require longer paths through the graph. It turns out that attempts to generalize metric spaces for noetic domains—to model noetic/psychic spaces—are actually pretty useful for social media algorithms, lol.

BlueSky’s Solution To Moderating Is Moderating Without Moderating via Social Proximity

I have noticed a lot of people are confused about why some posts don’t show up on threads, though they are not labeled by the moderation layer. Bluesky has begun using what it calls social neighborhoods (or network proximity) as a ranking signal for replies in threads. Replies from people who are closer to you in the social graph, accounts you follow, interact with, or share mutual connections with, are prioritized and shown more prominently. Replies from accounts that are farther away in that network are down-ranked. They are pushed far down the thread or placed behind “hidden replies.”

Each person gets their own unique view of a thread based on their social graph. It creates the impression that replies from distant users simply don’t exist. This is true even though they’re still technically public and viewable if you expand the thread or adjust filters. Bluesky is explicitly using features of subgraphs to moderate without moderating. Their reasoning is that if you can’t see each other, you can’t harass each other. Ergo, there is nothing to moderate.

Bluesky mentions that here:

https://bsky.social/about/blog/10-31-2025-building-healthier-social-media-update

As a digression, I’m not going to lie: I really enjoyed working on software built on the AT protocol, but their fucking users are so goddamn weird. It’s sort of like enjoying building houses, but hating every single person who moves into them. But, you don’t have to deal with them because you’re just the contractor. That is how I feel about Bluesky. I hate the people. I really like the protocol and infrastructure.

I sort of am a sadist who does enjoy drama, so I do get schadenfreude from people with social media addictions and parasocial fixations who reply to random people on Bluesky, because they don’t realize their replies are disconnected from the author’s thread unless that person is within their network. They aren’t part of the conversation they think they are. They’re algorithmically isolated from everyone else. Their replies aren’t viewable from the author’s thread because of how Bluesky handles social neighborhoods.

Bluesky’s idea of social neighborhoods is about grouping users into overlapping clusters based on real interaction patterns rather than just the follow graph. Unlike Twitter, it does not treat the network as one big public square. Instead, it models networks of “social neighborhoods” made up of people you follow, people who follow you, people you frequently interact with, and people who are closely connected to those groups. They’re soft, probabilistic groupings rather than strict labels.

Everyone does not see the same replies. Bluesky is being a bit vague with “hidden.” Hidden means your reply is still anchored to the thread and can be expanded. There is another way Bluesky can handle this. Bluesky uses social neighborhoods to judge contextual relevance. Replies from people inside or near your social neighborhood are more likely to be shown inline with a thread, expanded by default, or served in feeds. Replies from outside your neighborhood are still public and still indexed, but they’re treated as lower-context contributions.

Basically, if you reply to a thread, you will see it anchored to the conversation, and everyone will see it in search results, as a hashtag, or from your profile, but it will not be accessible via the thread of the person you were replying to. It is like shadow-banning people from threads unless they are strongly networked.

Because people have not been working with the AT Protocol like I have, they assume they are shadow-banned across the entire Bluesky app view. No—everyone is automatically shadow-banned from everyone else unless they are within the same social neighborhood. In other words, you are not part of the conversation you think you are joining because you are not part of their social group.

Your replies will appear in profiles, hashtag feeds, or search results without being visually anchored to the full thread. Discovery impressions are neighborhood-agnostic: they serve content because it matches a query, tag, or activity stream. Once the reply is shown, the app then decides whether it’s worth pulling in the rest of the conversation for you. If the original author and most participants fall outside your neighborhood, Bluesky often chooses not to expand that context automatically.

Bluesky really is trying to avoid having to moderate, so this is their solution. Instead of banning or issuing takedown labels to DIDs, the system lets replies exist everywhere, but not in that particular instance of the thread.

I find this ironic because a large reason why many people are staying on Bluesky and not moving to the fediverse—thank God, because I do not want them there—is discoverability, virality, and engagement.

In case anyone is asking how I know so much about how these algorithms work: I was a consultant on a lot of these types of algorithms, so I certainly hope I’d know how they work, lol. No, you get no more details about the work I’ve done. I have no hand in the algorithm Bluesky is using, but I have proposed and implemented that type of algorithm before.

I have an interest in noetics and the noosphere. A large amount of my ontological work is an extension of my attempts to model domains that have no spatial or temporal coordinates. The question is how do you generalize a metric space that has no physically, spatial properties. I went to school to try to formalize those ideas. Turns out they’re rather useful for digital social networks, too. The ontological analog to spatial distance, when you have no space, is a graph of similarities.

BlueSky’s Solution To Moderating Is Moderating Without Moderating via Social Proximity

I have noticed a lot of people are confused about why some posts don’t show up on threads, though they are not labeled by the moderation layer. Bluesky has begun using what it calls social neighborhoods (or network proximity) as a ranking signal for replies in threads. Replies from people who are closer to you in the social graph, accounts you follow, interact with, or share mutual connections with, are prioritized and shown more prominently. Replies from accounts that are farther away in that network are down-ranked. They are pushed far down the thread or placed behind “hidden replies.”

Each person gets their own unique view of a thread based on their social graph. It creates the impression that replies from distant users simply don’t exist. This is true even though they’re still technically public and viewable if you expand the thread or adjust filters. Bluesky is explicitly using features of subgraphs to moderate without moderating. Their reasoning is that if you can’t see each other, you can’t harass each other. Ergo, there is nothing to moderate.

Bluesky mentions that here:

https://bsky.social/about/blog/10-31-2025-building-healthier-social-media-update

As a digression, I’m not going to lie: I really enjoyed working on software built on the AT protocol, but their fucking users are so goddamn weird. It’s sort of like enjoying building houses, but hating every single person who moves into them. But, you don’t have to deal with them because you’re just the contractor. That is how I feel about Bluesky. I hate the people. I really like the protocol and infrastructure.

I sort of am a sadist who does enjoy drama, so I do get schadenfreude from people with social media addictions and parasocial fixations who reply to random people on Bluesky, because they don’t realize their replies are disconnected from the author’s thread unless that person is within their network. They aren’t part of the conversation they think they are. They’re algorithmically isolated from everyone else. Their replies aren’t viewable from the author’s thread because of how Bluesky handles social neighborhoods.

Bluesky’s idea of social neighborhoods is about grouping users into overlapping clusters based on real interaction patterns rather than just the follow graph. Unlike Twitter, it does not treat the network as one big public square. Instead, it models networks of “social neighborhoods” made up of people you follow, people who follow you, people you frequently interact with, and people who are closely connected to those groups. They’re soft, probabilistic groupings rather than strict labels.

Everyone does not see the same replies. Bluesky is being a bit vague with “hidden.” Hidden means your reply is still anchored to the thread and can be expanded. There is another way Bluesky can handle this. Bluesky uses social neighborhoods to judge contextual relevance. Replies from people inside or near your social neighborhood are more likely to be shown inline with a thread, expanded by default, or served in feeds. Replies from outside your neighborhood are still public and still indexed, but they’re treated as lower-context contributions.

Basically, if you reply to a thread, you will see it anchored to the conversation, and everyone will see it in search results, as a hashtag, or from your profile, but it will not be accessible via the thread of the person you were replying to. It is like shadow-banning people from threads unless they are strongly networked.

Because people have not been working with the AT Protocol like I have, they assume they are shadow-banned across the entire Bluesky app view. No—everyone is automatically shadow-banned from everyone else unless they are within the same social neighborhood. In other words, you are not part of the conversation you think you are joining because you are not part of their social group.

Your replies will appear in profiles, hashtag feeds, or search results without being visually anchored to the full thread. Discovery impressions are neighborhood-agnostic: they serve content because it matches a query, tag, or activity stream. Once the reply is shown, the app then decides whether it’s worth pulling in the rest of the conversation for you. If the original author and most participants fall outside your neighborhood, Bluesky often chooses not to expand that context automatically.

Bluesky really is trying to avoid having to moderate, so this is their solution. Instead of banning or issuing takedown labels to DIDs, the system lets replies exist everywhere, but not in that particular instance of the thread.

I find this ironic because a large reason why many people are staying on Bluesky and not moving to the fediverse—thank God, because I do not want them there—is discoverability, virality, and engagement.

In case anyone is asking how I know so much about how these algorithms work: I was a consultant on a lot of these types of algorithms, so I certainly hope I’d know how they work, lol. No, you get no more details about the work I’ve done. I have no hand in the algorithm Bluesky is using, but I have proposed and implemented that type of algorithm before.

I have an interest in noetics and the noosphere. A large amount of my ontological work is an extension of my attempts to model domains that have no spatial or temporal coordinates. The question is how do you generalize a metric space that has no physically, spatial properties. I went to school to try to formalize those ideas. Turns out they’re rather useful for digital social networks, too. The ontological analog to spatial distance, when you have no space, is a graph of similarities.

This can be modeled by representing each item as a node in a weighted graph, where edges are weighted by dissimilarity rather than similarity. Highly similar items are connected by low-weight edges, while less similar items are connected by higher-weight edges. Distances in the graph, computed using standard shortest-path algorithms, then correspond to degrees of similarity. Closely related items are separated by short path lengths, while increasingly dissimilar items require longer paths through the graph. It turns out that attempts to generalize metric spaces for noetic domains—to model noetic/psychic spaces—are actually pretty useful for social media algorithms, lol.

BlueSky’s Solution To Moderating Is Moderating Without Moderating via Social Proximity

I have noticed a lot of people are confused about why some posts don’t show up on threads, though they are not labeled by the moderation layer. Bluesky has begun using what it calls social neighborhoods (or network proximity) as a ranking signal for replies in threads. Replies from people who are closer to you in the social graph, accounts you follow, interact with, or share mutual connections with, are prioritized and shown more prominently. Replies from accounts that are farther away in that network are down-ranked. They are pushed far down the thread or placed behind “hidden replies.”

Each person gets their own unique view of a thread based on their social graph. It creates the impression that replies from distant users simply don’t exist. This is true even though they’re still technically public and viewable if you expand the thread or adjust filters. Bluesky is explicitly using features of subgraphs to moderate without moderating. Their reasoning is that if you can’t see each other, you can’t harass each other. Ergo, there is nothing to moderate.

Bluesky mentions that here:

https://bsky.social/about/blog/10-31-2025-building-healthier-social-media-update

As a digression, I’m not going to lie: I really enjoyed working on software built on the AT protocol, but their fucking users are so goddamn weird. It’s sort of like enjoying building houses, but hating every single person who moves into them. But, you don’t have to deal with them because you’re just the contractor. That is how I feel about Bluesky. I hate the people. I really like the protocol and infrastructure.

I sort of am a sadist who does enjoy drama, so I do get schadenfreude from people with social media addictions and parasocial fixations who reply to random people on Bluesky, because they don’t realize their replies are disconnected from the author’s thread unless that person is within their network. They aren’t part of the conversation they think they are. They’re algorithmically isolated from everyone else. Their replies aren’t viewable from the author’s thread because of how Bluesky handles social neighborhoods.

Bluesky’s idea of social neighborhoods is about grouping users into overlapping clusters based on real interaction patterns rather than just the follow graph. Unlike Twitter, it does not treat the network as one big public square. Instead, it models networks of “social neighborhoods” made up of people you follow, people who follow you, people you frequently interact with, and people who are closely connected to those groups. They’re soft, probabilistic groupings rather than strict labels.

Everyone does not see the same replies. Bluesky is being a bit vague with “hidden.” Hidden means your reply is still anchored to the thread and can be expanded. There is another way Bluesky can handle this. Bluesky uses social neighborhoods to judge contextual relevance. Replies from people inside or near your social neighborhood are more likely to be shown inline with a thread, expanded by default, or served in feeds. Replies from outside your neighborhood are still public and still indexed, but they’re treated as lower-context contributions.

Basically, if you reply to a thread, you will see it anchored to the conversation, and everyone will see it in search results, as a hashtag, or from your profile, but it will not be accessible via the thread of the person you were replying to. It is like shadow-banning people from threads unless they are strongly networked.

Because people have not been working with the AT Protocol like I have, they assume they are shadow-banned across the entire Bluesky app view. No—everyone is automatically shadow-banned from everyone else unless they are within the same social neighborhood. In other words, you are not part of the conversation you think you are joining because you are not part of their social group.

Your replies will appear in profiles, hashtag feeds, or search results without being visually anchored to the full thread. Discovery impressions are neighborhood-agnostic: they serve content because it matches a query, tag, or activity stream. Once the reply is shown, the app then decides whether it’s worth pulling in the rest of the conversation for you. If the original author and most participants fall outside your neighborhood, Bluesky often chooses not to expand that context automatically.

Bluesky really is trying to avoid having to moderate, so this is their solution. Instead of banning or issuing takedown labels to DIDs, the system lets replies exist everywhere, but not in that particular instance of the thread.

I find this ironic because a large reason why many people are staying on Bluesky and not moving to the fediverse—thank God, because I do not want them there—is discoverability, virality, and engagement.

In case anyone is asking how I know so much about how these algorithms work: I was a consultant on a lot of these types of algorithms, so I certainly hope I’d know how they work, lol. No, you get no more details about the work I’ve done. I have no hand in the algorithm Bluesky is using, but I have proposed and implemented that type of algorithm before.

I have an interest in noetics and the noosphere. A large amount of my ontological work is an extension of my attempts to model domains that have no spatial or temporal coordinates. The question is how do you generalize a metric space that has no physically, spatial properties. I went to school to try to formalize those ideas. Turns out they’re rather useful for digital social networks, too. The ontological analog to spatial distance, when you have no space, is a graph of similarities.

This can be modeled by representing each item as a node in a weighted graph, where edges are weighted by dissimilarity rather than similarity. Highly similar items are connected by low-weight edges, while less similar items are connected by higher-weight edges. Distances in the graph, computed using standard shortest-path algorithms, then correspond to degrees of similarity. Closely related items are separated by short path lengths, while increasingly dissimilar items require longer paths through the graph. It turns out that attempts to generalize metric spaces for noetic domains—to model noetic/psychic spaces—are actually pretty useful for social media algorithms, lol.