Goofed Home

Just had to add a workaround to #Fedify for http://joinmastodon.org/ns, a JSON-LD context URL that has never actually served a JSON-LD document. Mastodon has always inlined the term definitions, but some implementations put it as a bare URL in their @context, so Fedify’s JSON-LD processor tries to fetch it and gets a 404 Not Found. Now Fedify ships a bundled copy of a context that never existed in the first place.

https://github.com/fedify-dev/fedify/pull/631

#fedidev #ActivityPub #JSONLD

@hongminhee Can Fedify process this post?

https://mitra.social/.well-known/apgateway/did:key:z6MkumzpDj1cYZD2GrBbVT86xL6CfPuyqWZAEXMfSqN9j3hf/objects/019ce2d7-6367-ef68-9810-6a5548c8ca1d

@hongminhee @kopper I'm too stupid to understand AP specifically (but I have a deep CS background).. I've always wondered why this wasn't the model by default? Using UUIDv7 you could mark every in order of timetime.

I think you could push the separation of intents further. Make a "AP post" hold all of the metadata, but make the actual text an attachment like an image, video, audio etc.. then you could just store all of the text in blobs in storage "even as ciphertext" requiring the original toot to fetch and decrypt.

also. I think the idea of attaching a user to an instance (domain) was always a mistake. A user should be whoever owns the key material on a frontend (endpoint), and it should be able to ask any "client in your meaning" to be it's new primary location (they can be AP broadcast... user with public key X is now defaulting to client Y)...

BUT all of this is fan fiction, nobody has even solved the storage problem on mastodon :/

Turning media URIs from dedicated single URLS to magnet:<hashes> that can be pulled down from multiple locations incase the original dies feels like REALLLLLY low hanging fruit that nobody has touched (and It kind of annoys me nobody has).

@hongminhee @COSCUP
If there's any kind of travel bursary, I'd be delighted to speak.

@hongminhee @COSCUP woooooooooooo! Let me know if @swf can help in any way

@evan@cosocial.ca @swf@socialwebfoundation.org That means a lot, thank you! I’d love to take you up on that—will send you a DM with some specifics shortly.

@julian I can read the outbox and activities 👍

There is a minor problem with Like activities, which don't have a to field (this means nobody should be able to see them).

And while we're at it: when NodeBB sends a signed GET request, does it add a Digest header? I see warnings in my log due to invalid header value.

@django @hongminhee