Right now, when I send a GIF, users of clients that don't understand GIF messages do not have a way to:
- Know that what they are looking at is a GIF message
- Access the content of the message (i.e. somehow manually look up the GIF).
It would be good if these were a solution that allowed people to do one or both of these.
My recommended approach would be to change the GIF encoding to use a URL to something. Since it looks like the GIFs already come from Giphy, we could use the full Giphy URLs instead of just the IDs being used currently.
The downside is that this would take more bytes per image. But it would still, as far as I can tell, fit comfortably under the message limit, and it would mean that basically every client would be able to get something useful out of the message, so it would probably reduce concerns like those in #109 about "wasting" airtime or "spamming" the mesh when these extended-feature messages are sent.
Right now, when I send a GIF, users of clients that don't understand GIF messages do not have a way to:
It would be good if these were a solution that allowed people to do one or both of these.
My recommended approach would be to change the GIF encoding to use a URL to something. Since it looks like the GIFs already come from Giphy, we could use the full Giphy URLs instead of just the IDs being used currently.
The downside is that this would take more bytes per image. But it would still, as far as I can tell, fit comfortably under the message limit, and it would mean that basically every client would be able to get something useful out of the message, so it would probably reduce concerns like those in #109 about "wasting" airtime or "spamming" the mesh when these extended-feature messages are sent.