just noticed the atproto spec never actually defines "mime type" in any way. theres not reference to rfc6838 anywhere in the specs ... feels problematic

what is the mime type of an atproto record? maybe application/atproto+app.bsky.feed.post

Hey @dholms.at, do you have plans for blobs in spaces? We're chatting about it on @iame.li's stream. The proposal says blobs are uploaded to space host, right? That makes sense when the space host is a PDS because it has `com.atproto.repo.uploadBlob`, but not if the space host is something else.

I mean, basically yeah! This is the atproto database I've been playing with lately.

An ATProto-aware blob proxy! What a sensational idea. github.com/Blooym/porxie

I made meme-museum.at to explore making a complete (if simple) atproto app. Build a collection of meme images and post htem. I don't know if anyone needs it, but, as I tried to lay out in the post, I'll be happy if it helps demonstrate why I'm so excited about the potential of atproto.

an app that uses atproto blobs as 'generic file storage' seems eminently possible but maybe against the intent of the system?

Been thinking about how we could support access-controlled blobs in ATProtocol. Right now, all blobs are public - anyone can fetch them with a CID. But what if we could gate them? #atproto #atdev 🧵

Random musings: I think I kinda understand where attie, or a tool like it, exists now. This is a long play that will only reach its final state if access to data important to a user continues to improve within atproto. The model performance is irrelevant. It's just a data problem.