what should part 2 be? where should we take statusphere nex…

Samuel

@samuel.fm

what should part 2 be? where should we take statusphere next?

Samuel@samuel.fm· 5 Mar 2025

new blog post: atproto by example part 1 in which I cover how to use the full potential of lexicon for building atproto apps

atproto by example part 1: records and views — mozzius.dev

by Samuel · 11 min read

mozzius.dev

4 3 41

Samuel 5 Mar 2025

some ideas: - blobs and atproto CDNs - indexing app.bsky records - ... and then piggybacking off the bluesky social graph - extending statusphere into micro-microblogging - automod, maybe even labelling?

5 14

The Fresh Prince of Donair 5 Mar 2025

I’d love to learn more about blob storage, encryption of them on PDSs, and the limits around it.

1 3

dame 5 Mar 2025

i am a micro-micro-blogging enjoyer (@now.dame.is) so that’s my vote

fuckface "squeaky" from:me 5 Mar 2025

an example automod without a backing ozone instance would be amazing

1 2

Samuel 5 Mar 2025

here you go: github.com/mozzius/back...

https://github.com/mozzius/backdate-labeller/blob/main/main.ts

github.com

1 3

futur 🔹5 Mar 2025

I like that you kept the 14831 port

Sergio 5 Mar 2025

descentralized identifiers

1 1

Samuel 5 Mar 2025

hmm, say more? I'm more interested in documenting the building apps side of things

Sergio 5 Mar 2025

Ahh yes, from that perspective it is not the best subject 😅 (I just think its a very interesting part of the protocol)

1 1

Sergio 6 Mar 2025

a more practical subject: reading from the firehose AND how to do backfilling

1 1

Samuel 6 Mar 2025

aha first I also need to learn how to do that lmao

Michel Bestaat 5 Mar 2025

As for labeling, the mechanism where you have to put things in a http header (atproxy?) is rather opaque I think. There are a few more, accept-languages and one more.