b64 images violates the "human readable" principle. I don't think rendering them is the right approach.
Discussion
By that standard, every long link violates the principle, including nprofile and nevent links, cashu tokens and ln invoices/withdraws
Yes, but there are two differences:
- Those entities are often provided by the user directly, and are therefore meaningful to users. Clients are imitating natural end-user actions by generating them.
- Entities are references (links, npubs), or content that has no reference (cashu tokens, invoices). b64 images are content that can otherwise be included by reference.
In other words, I've never seen a user paste a base64 encoded image into a note instead of uploading it to a host and referencing it.
Every content can be included by reference. I don't need to type the message, I can just add a link to where the text message is in my server and sign that.
You can search for base64 images on NIP-50 relays. There are 1000s of posts with images before our release went out and those were breaking Amethyst's UX. So, it's a no brainer for me.
The user void has spoken
So if I start publishing notes from Coracle in rot13'd LaTeX you'll render that too?
if people use it, I would be forced to support it.
Ok, serious question, who is publishing content base64'd images in it? I vaguely remember hearing about a new client doing this but can't remember who.
It was freezing amethyst when seeing a base64
Amethyst issue:
https://github.com/vitorpamplona/amethyst/issues/951
event:
And well it might