Is my reaction (in the comments to the Sharkey MR) wrong? I'm pretty sure that IRIs in JSON-LD work just like namespaces worked in XML… so they don't need to resolve to actual resources, and changing a prefix-to-IRI mapping changes the meaning of the document. How wrong am I?
@dakkar@hrefna I believe you are correct - it's like XML namespaces in that the exact value controls interpretation, and it doesn't matter if the domain name even exists.
so… the firefish devs have made a change that did not break things only because the consumers (mostly Misskey forks) process JSON-LD "wrong", completely ignoring the context.
I have suggested they revert that change, let's see what happens.
@ryanc@infosec.exchange@hrefna@hachyderm.io oh no, it's even more simple-minded: it completely ignores the @context (which contains "firefish": "https://joinfirefish.org/ns#", "speakAsCat": "firefish:speakAsCat"), and only looks for speakAsCat (which is the only property defined in the firefish namespace) in the top-level of the activity
@dakkar pragmatically, if every implementation that understands this thing is broken... just leave it be and fix the implementations so they use context correctly?
seems like the json equivalent of shotgun parsing...
@ryanc@infosec.exchange in the sense that "people will probably not notice the breakage", sure I'll still try to get them to revert, because it's wrong 😠