Lady of the Land @Lady@cat.family

played “My Best Friends” for @Satsuma and they were NOT having it

Take your Electric type like Jolteon,
Against Leafeon’s Grass the battle’s no fun.
Reach higher with Fire—go Flareon!
Think twice about Ice to be number one.
Water’s in order if you want to be slick.
Espeon’s the best bet when you get Psychic.
Umbreon’s the key to your Dark mood,
But Sylveon won’t leave you with time to brood!

how do you do the things you do? share with me your secrets deep inside. what kind of lesbian are you? are you loyal thru & thru? do you have a heart that’s true?

probably won’t finish my new static site generator makefile by the end of today but hopefully will by the end of new years

@gaditb (DID registry is here if you are curious <https://www.w3.org/TR/did-spec-registries/#did-methods>. i think this whole thing is very silly and reinventing problems we all agreed were a bad idea like ten years ago)

@gaditb the at protocol then specifies how to turn that response plus the path into something meaningful

@gaditb see for yourself: https://plc.directory/did:plc:x4qyokjtdzgl7gmqhsw4ajqj

it's a centralized resolver service (plc.directory) that tracks a bunch of metadata about the thing in question

@gaditb what they're semantically saying is "ask the account plc:… for this post they made on bsky.app"; it's to support account portability (if they ever get a PLC resolver which allows that??)

@gaditb DIDs have a separate registry for all of the DID types that they maintain themselves, so you have to check the registry and look up wtf PLC is and how to resolve it

literally they just reinvented URNs but with a registry they own themselves. you can't resolve them without knowing what they mean

@gaditb i mean maybe i'm coming out as against websockets here, but idk, honestly i don't have to deal with these problems often enough to have a strong opinion

i think the easy case is easy and reachable with just XML, and maybe there's a more efficient, complex case which can be built on top of it, but the easy case should still be possible regardless

@gaditb this is very fucked up, just imo, but that's what it is

@gaditb did: is an IRI format which specifies a resolver (plc?) and a resource key; at:// is a protocol which takes a DID and indicates that it should be accessed using the AT protocol and then that the path should be followed (side-note: IETF does not like the name at: but has no mechanism by which to disallow it)

so this is saying

Access [PLC DID] with AT and then access the [app.bsky.feed.post] collection and then access item [ID] within it

@gaditb i think web/Unix/“view source” philosophy is that the result of any request should be a document, yeah

@gaditb i think i'm mostly in agreement but my sticking point is that if you want document structure to survive data transformation then you need to pick a document structure and stick with it conceptually, even if the view only exposes a subset

i think that the document structure you should pick should be conceptualized as XML Infoset as early in the process as possible, so that all your transformations are conceptually XML Infoset to XML Infoset, even if you're using a syntax which only actually exposes a part of that

i care less whether you're actually serializing that as XML, although I think Unix philosophy would state that at application boundaries you should be

@gaditb like i actually care a lot more about XML Infoset as a baseline than XML the set of strings which match the document production specified in the eXtensible Markup Language specification (version 1.0 or 1.1)