@raphael yes, that's how it works now. You can use an array of Link items for the location of an image (say), with different hrefs with different protocols.
OK, this is interesting. I think peer-to-peer file storage is probably a good optional feature, with HTTPS as a fallback. I don't know if IPFS is the right storage solution, but it's probably worth exploring. I'm somewhat agree.
@janl So, could you break down why you think it would be a nightmare? I agree that CSAM is really bad, but I don't understand IPFS well enough to know why having someone somewhere on the network post illegal content would cause me problems on my node.
@thisismissem@janl OK, so, this is how I understand IPFS; happy to be corrected.
Data uploaded to a local node is not automatically pushed to any other nodes. Those other nodes have to request the data (say, because they're following a link).
If "bad" data was uploaded to someone else's node, and nobody on my node requested it, it's not going to end up on my node.
Someone uploaded bad data to a remote node, and someone on my node requested it (say, by following a link). Now it's cached in my node. I can delete it from my node.
Someone on my node uploaded bad data to my node, and people on remote nodes requested it, pulling it to their nodes. I can delete it from my node, but not from remote nodes.
Is there an Internet Media Type for social microsyntax, the plain-text source format that is used to convert @-mentions, hashtags, and URLs into links in HTML5? I've been unable to find one, and have fallen back to text/plain.