# the head of trust and safety should not have an automated enemies list

- Link: https://tacobout.online/2026/09/30/bluesky-head-trust-safety-automated-enemies-list/
- Published: 2026-09-30T11:45:00-05:00
- Author: schwegler

a personal block is a boundary. a head of trust and safety automating one is a governance
problem wearing the skin of a vibe check.

this morning, Andrew discovered that Aaron Rodericks had blocked him on Bluesky.
Rodericks’s profile identifies him as Bluesky’s Head of Trust and Safety and currently
announces, “Automation enabled on interactions — abuse will generate auto-blocks.”
Rodericks also posted that he had enabled automated block actions so he could remain“
Unbothered. Moisturized. Happy. In my lane. Focused. Flourishing.”

> I didn’t even call the dumb motherfucker out for liking questionable skeets or
> anything. smdh
> — [schweg, but spooky (@schwegler.lol)](https://bsky.app/profile/did:plc:djguxreovfe4bkm7sizg2kxk?ref_src=embed)
> [2026-09-30T12:11:42.096Z](https://bsky.app/profile/did:plc:djguxreovfe4bkm7sizg2kxk/post/3mwqctvqjfs2l?ref_src=embed)

![Bluesky screen stating that @aaron.bsky.team has blocked Andrew](https://i0.wp.
com/tacobout.online/wp-content/uploads/2026/09/andrew-blocked-by-aaron-bsky-team.
webp?resize=1206%2C314&ssl=1)

The block notice Andrew posted on September 30. Screenshot: [@schwegler.lol on Bluesky](https://bsky.app/profile/schwegler.lol/post/3mwqctvqjfs2l).

maybe every account caught by that automation deserved the block. maybe none did.
that is not the interesting part, because a user does not owe anybody a hearing 
before removing them from a feed. the block button exists precisely so ordinary 
people can stop litigating whether somebody has earned access to them.

the problem is that this is not an ordinary account. the person pressing—or delegating—
the button also leads the team that can label content, restrict visibility, suspend
accounts, and decide what counts as abuse across the service. the personal preference
and the institutional judgment live inside one profile, and an automated system 
is apparently helping sort the guest list.

## the block button has two jobs now

Bluesky’s [founding moderation pitch](https://bsky.social/about/blog/4-13-2023-moderation)
was built around separating powers. instead of one company making every fine-grained
decision, users could choose additional labelers, filters, and community rules. 
the company described moderation as customizable infrastructure where human and 
automated systems work together, with user agency as the point.

that is a genuinely better idea than pretending one universal feed can settle every
argument on earth. it also makes this particular mess look worse. composable moderation
depends on people understanding which layer is acting on them. did a person set 
a private boundary? did an automated tool classify an interaction as abuse? did 
a platform official exercise power? when all three wear the same handle, “user choice”
begins to resemble the manager personally working the velvet rope.

> Automated block actions on my account, so that I can stay Unbothered. Moisturized.
> Happy. In my lane. Focused. Flourishing.TBH it was well overdue.
> — [Aaron Rodericks (@aaron.bsky.team)](https://bsky.app/profile/did:plc:ksjfbda7262bbqmuoly54lww?ref_src=embed)
> [2026-09-30T12:33:40.828Z](https://bsky.app/profile/did:plc:ksjfbda7262bbqmuoly54lww/post/3mwqe37envs2x?ref_src=embed)

![Profile photograph of Aaron Rodericks, Bluesky's Head of Trust and Safety](https://
i0.wp.com/tacobout.online/wp-content/uploads/2026/09/aaron-rodericks-bluesky-avatar.
webp?resize=1000%2C1000&ssl=1)

Aaron Rodericks identifies himself as Bluesky’s Head of Trust and Safety. Image:
[@aaron.bsky.team](https://bsky.app/profile/aaron.bsky.team).

Bluesky’s own [user guide](https://bsky.social/about/blog/5-19-2023-user-faq) says
blocking prevents both accounts from seeing or interacting with each other’s posts.
that is fine for users. it becomes structurally strange when the blocked person 
is still subject to the blocker’s professional authority. Andrew put it neatly: 
if the head of trust and safety blocks you, he also should not get to use moderation
tools to inspect your posts.

> it should be a rule that if the head of trust and safety blocks you that he also
> can’t use his moderating tools to see your skeets
> — [schweg, but spooky (@schwegler.lol)](https://bsky.app/profile/did:plc:djguxreovfe4bkm7sizg2kxk?ref_src=embed)
> [2026-09-30T12:16:22.419Z](https://bsky.app/profile/did:plc:djguxreovfe4bkm7sizg2kxk/post/3mwqd4b2xls2l?ref_src=embed)

## due process cannot be a mood

this does not require executives to accept unlimited abuse. it requires boring procedures,
which is how organizations keep personal conflict from becoming policy. staff accounts
can mute freely. blocks can trigger disclosure and recusal. automated lists can 
be documented, appealable, and separated from enforcement tools. another moderator
can review reports involving somebody their boss has personally blocked. none of
this is exotic. it is the administrative equivalent of not letting the referee place
bets from the field.

Bluesky’s current [community guidelines](https://bsky.social/about/support/community-guidelines)
explicitly prohibit abusing lists, labels, community moderation tools, and automated
harassment systems. the company also says baseline enforcement requires careful 
judgment and that appeals exist when it gets something wrong. those promises need
to apply most visibly when the dispute involves the person running trust and safety.
otherwise the lesson is that automation creates accountability for users and plausible
deniability for management.

the internet has spent years discovering that content moderation is unavoidable 
and power without transparency is intolerable. Bluesky was supposed to improve that
bargain by making moderation plural, legible, and user-controlled. an automated 
enemies list attached to the trust-and-safety chief’s personal account moves in 
the opposite direction. it collapses a private annoyance, a machine judgment, and
an institutional hierarchy into one cheerful little “Unbothered” button.

being unbothered is a reasonable goal for a person. it is not a governance model.
