5 ms·

You could create a client that uses a non-standard markup and be able to render inline images just fine... oops! I think I just broke the web again :)

• MartijnBraam 5y ago
  That would be against the spirit of the whole Gemini thing
• SilverRed 5y ago
  Just put them in markdown and have compatible clients inline render an image and non compatible clients get a link.
  • edflsafoiewq 5y ago
    Compare this thread with the thread about <img> 30 years ago: http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.ht...
    • goodpoint 5y ago
      Thank you! The HN crowd has an extremely short memory.
      • SilverRed 5y ago
        "Short memory". That email was sent almost a decade before I was born.
        • goodpoint 5y ago
          So? Historical memory is not based on your age.
    • krapp 5y ago
      The generic <include> tag being discussed there might have been nice to have. Also Marc Andreeson's suggestion of "a general-purpose procedural graphics language within which we can embed arbitrary hyperlinks attached to icons, images, or text, or anything" before JS or HTML5 canvas arrived on the scene is interesting. An alternative protocol that explored some of these evolutionary dead ends of the early web could be fun. [0]http://1997.webhistory.org/www.lists/www-talk.1993q1/0209.html http://1997.webhistory.org/www.lists/www-talk.1993q1/0209.ht...