atproto
thought-ful @oms
packing them up so i can sleep
Sep 12, 2025 · 2 min read
- what is actually possible vs. legal responsibility of bluesky and others wrt different levels of atproto (pds, relay, appview {for the love of all things can we rename this}, client)
- bother with getting one of python pds implementations setup / up to (my admittedly perfectionist high) standards or just use like…some other impl in a language I don’t know?
- cloud pds vs home server may be conundrum for some incl me
- what are legal implications of being on PDS outside country of residence wrt their country of residence and the host country?
- pds service for creators - promise of perma storage + backups. real lure is gonna be monetization. Meta gives shit. TT gives…something? Idk but I’d guess not impressive.
- how to ensure ecosystem supports, without luring in bullshit?
- what if feed builders can monetize via ads but then have $$ earned just go toward creators? issue arises again if avoiding luring in bullshit. and monopoly of large accounts / “early bird” affect.
- how to work around wall-gardens to make transition to open-gardens more feasible for COMMUNITIES? creators and small biz?
- better user-composable moderation. aside from clearly egregious, inform users before action / more indicators of e.g. who & why warning. def don’t apply to mutuals. labelers to have lik, Google reviews.
- srsly need feed-level regex mute lists a la graze but like, easy toggle on/off in client kinda thing
- saw once bsky app not v accessible. so forks arent either. this needs fixing. esp for a fork that has alt appview layer options, since disabled community is so often forgotten and targeted (which is why i say fork; accessible client limited if relies on bsky appview
Did this enjoy this document?
Give it a heart — Standard Reader surfaces well-loved writing to more readers across the network.
Notes & Ideas
@byarielm.fyi