9b
9bed45ee
9bed45ee7c3241eea3ba74921a2b822c73f1447e5962314205d91a78cc99622e
nostr:npub146y59dkatpwkx0ncs9u34vhmm60dedmdla0s8zy8yw22pqfj4huq36dp2y

works with #brave

ipfs://bafybeib7nj4kqo6pateotfnzpzsvyee245arsw4ff6fl7zxdlmmsdd4hke/Stasya-telephone-1-009.jpg

there is no valid reason behind blocking top level navigation to data uris

only actual reasons are centralization and kyc

there is no real difference between linkin to a https url or data url, other than centralization and kyc

to link to https url, someone has to 1) buy centralized kyc domain name

and 2) rent centralized kyc web server

however, to link to data url, neither of these is needed

data urls enable serverless webapps to be built by anyone to be hosted by any (social) platform that supports text data, like nostr for example

disabling data uris for reasons like "ooh, but bad sites open data uri popups with malware" is no different from "ooh, but bad sites open http urls with malware".

owning domain name and server does not make any site not malware

there is zero security guarantee for such. owning icann domain name is mainly just building centralized kyc infra which the whole digital economy tends to go towards

#datauri #data_uri do not #block_toplevel_data_uri_navigations

make uris great again

#firefox:

about:config -> security.data_uri.block_toplevel_data_uri_navigations: false

test link behind following url

however you need to copy paste this one first, because your nostr client does not create link from this one

data:text/html;r=nos.lol;p=https%3A%2F%2Fcorsproxy.org;i=https%3A%2F%2Fimagewnine.net%2Fimages%2F2022%2F07%2F10%2FLily-Rose-08-037.jpg;,

data:text/html;r=nos.lol;p=https%3A%2F%2Fcorsproxy.org;i=https%3A%2F%2Fimagewnine.net%2Fimages%2F2022%2F07%2F10%2FLily-Rose-08-037.jpg;,

hmm

security.data_uri.block_toplevel_data_uri_navigations

data:text/html,

experimenting

data:text/html,

request can be configured easily, now we get picture by pubkey

data:text/html,