mpeg doordash

this really is old twitter because i can finally see patton on my feed retweeting blaine capatch again

"must be a king!"
"why do you say that?"
"hasn't got shit all over him"

ah it has leveled up to senior developer

thiccsky

what’s an example of a well-designed social federation protocol?

PS: if you say email i’m going to block you (just kidding xD)

there’s nothing about atproto that prevents protecting a subset of data from anonymous public view…idk where you got that assumption from but it’s false. i’m part of the WG adding private/protected data to atproto, which includes bsky engineers, so they for sure have not “given up” on the idea…

yup! we’re still a “middle man” of sorts because we facilitate all payments on the network, like for subscriptions and ad impressions.

i get that…personally i did have to deal with something similar when i was much younger. it made me very aware of how accessible the things i wrote were.

yeah that makes sense...kinda like how deleting a branch in git doesn’t actually delete the comments, just the reference to them. a savvy user could still get to those commits hence why removing leaked creds is a damn hassle :)

this philosophy is probably what led to the decision to ship bsky without private posting…figuring that most users won’t care about it, and it will add complexity to the design of the protocol. it’s not perfect, but clearly we’re here so it’s good enough, and we can make it better!

com.atproto.repo.deleteRecord | Bluesky *This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS i...

oh that might be a bsky specific thing…i was referring to the records themselves which is a bit more lower-level. protected data would also work on this level, how bsky uses it is up to their discretion.

docs.bsky.app/docs/api/com...

that’s pretty neat! are you doing this to embed metadata in like stream VODs or something? or just to mess around with binary formats? xD

as a longtime vim user, i gotta go with “à la mode”

everybody says “react is just javascript” but sometimes it isn’t fair so i think it’s actually unjust javascript.

pretty much. it’s more like if you ran your own spotify, over atproto. so you’re hosting your own content (or paying for managed hosting), but also given the tools to monetize it. the end user can browse all artists and listen seamlessly…just works like any other music app.

many devs, including myself, are working on bringing protected data to atproto. it’s something everyone wants, but in a distributed system it’s not exactly trivial to implement. i disagree that it’s “malpractice” that it’s missing, requiring it could have prevented bsky from launching at all imo.

pining for the days when posts were on an actual post

converting would be (theoretically) pointless because the post is already public…even the protected data proposals are only for stuff going forward.

however, u COULD copy the body of that record & replace it with a protected one, then delete the old record. might break some links but should work…

just make one big fragmented .mp4 for the whole repo and address each record by byte range xD

does the atproto spec enforce that record lexicons must be of type object, or is that just a lex cli thing? never noticed it anywhere but iirc you get errors if you try to do e.g. “type”: “bytes”

if you’re using claude and generating atproto types make sure you add those to your contexts! it’ll try to reinvent the wheel a LOT if you don’t tell it that you already have autogenerated client & server code.

i think the transcoder technically does have to do that by design, because it is decoding from one format into binary and then encoding into another format...

noticed we got email 2FA in the bsky app now…curious as to why this route was chosen instead of WebAuthn or “real” 2FA (like with a security key or authenticator app)?

and yeah i know @baileytownsend.dev made a “real” MFA thingy for the PDS and that’s probably what i’m gonna use when i self host.

like how @skylight.social live stream comments use @stream.place chat message lexicons so they’re interoperable on both apps?

or how @tracklist.diy plays use @teal.fm scrobbles so when you get your teal invite you already have a corpus of data?

yeah that’s probably the CDN they’re using…a lot of em do that these days. especially for small videos it takes like no time to segment so it could likely be done on-demand, similar to image optimizations and stuff like that.

part of what i like about atproto is that the end user doesn’t need to know about how the sausage is made just to understand the platform. this is in stark contrast to other decentralized systems like cryptocurrencies or activitypub, where not knowing that stuff can land you into possible trouble.

Glossary of terms - AT Protocol A collection of terminology used in the AT Protocol and their definitions.

“XRPC is a term we are deprecating, but it was historically used to describe atproto's flavor of HTTP usage.”

it’s just HTTP with possible extra steps.

atproto.com/guides/gloss...

the “communism” of software architectures

the cool kids write most of their post in the alt text

tracklist:// — the world is listening music without limits

what was once a block of marble is now beginning to reveal the shape of an application that’s been in our minds for close to a decade.

last week, we successfully implemented DRMed audio streaming over atproto!

wanna be the first to get access?

sign up here:
tracklist.diy