@hongminhee @loops now it does!

@hongminhee @ghost @fedify these properties should be part of the https://w3id.org/security/v1 context, but it looks like we are omitting this context in some activities

Smithereen (I'm writing this from it) also does JSON-LD processing but also supports LD signatures. I don't understand what's the problem here — imo you aren't supposed to LD-process the signature itself. I remove it before any LD processing and treat it as a separate object passed alongside the main one.

@hongminhee Do they want LD signatures in Fedify in order to process forwarded Create activities? I simply fetch object by its id when signer and actor do not match.

@hongminhee@fosstodon.org anything that improves accessibility, be it for disabled or people of different language, should not be a suggestion but mandatory

@hongminhee@fosstodon.org
what the fuck why is unicode like that?

I'm sharing a prototype of #Fedify written in #Python, codenamed “FediKit.” Many of the ideas for Fedify were already implemented in this prototype, albeit in a different language.

https://github.com/dahlia/fedikit