More silly text/gemini spec proposals

[plugd]

Sean Conner writes:
>   That's the incorrect format.  It should be:
> => data:text/plain,a%20person%20dancing

Sure, but the point is to _abuse_ the data: URL so as to make it
useless.

>   The issue is when someone does something like:
>
> => data:image/jpeg;base64,YSBwZXJzb24gZGFuY2luZw...
> ```
>    \o/
>     |
>    / \
> ```

But that will render horribly in clients that are obeying the spec where
we abuse the contents of the data URL to specify the alt-text.  

I'm not actually suggesting this, to be honest - I'm just pointing out
one technically feasible way of making it in the client author's
best interest to prohibit using data: URLs to embed arbitrary content.
Just saying to client authors, "you MUST refuse this URL type" isn't
going to work.  But making it somehow impossible for clients to
simultaneously behave sensibly in the face of correctly formatted
text/gemini _and_ interpret data: URLs as they are intended seems like
it could work, at least in principle.

Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200530/2d95536e/attachment.sig>