|
3 posts total
 I received a request from @ghost today to add #LDSignatures to @fedify for compatibility with #Mastodon, as Mastodon does not plan to implement Object Integrity Proofs (FEP-8b32) for the near future. 😩 However, Mastodon's implementation of LD Signatures does not even use valid JSON-LD properties (despite the name), so I'm not sure how to make it compatible with Mastodon since #Fedify does JSON-LD processing. 🤔 Wow, English-only people (or Western languages, for that matter) are so naïve. In case you didn't know, the lang attribute is very important in East Asian languages. https://lobste.rs/s/9ck6y9/what_programming_language_is_this_code#c_0zuhqs
Show previous comments
 @hongminhee@fosstodon.org anything that improves accessibility, be it for disabled or people of different language, should not be a suggestion but mandatory  @hongminhee not just East Asian. Some other languages suffer from this as well. Unicode is a fuck.
https://tonsky.me/blog/unicode/ |
Gregory's Server
@hongminhee @ghost @fedify these properties should be part of the
https://w3id.org/security/v1context, but it looks like we are omitting this context in some activitiesSmithereen (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
objectby itsidwhen signer and actor do not match.