in reply to New Design for Sending + - votes on PerlMonks

Earlier someone told me not to post inline html pictures in my post, because it makes each of my post very big.
I didn't see the context in which that comment was made, but I strongly suspect that they may have meant that it makes the post "very big" in terms of the amount of screen space consumed to display it, not the number of bytes sent. Inline images (depending on size and position, of course) can break the site's layout, which many of us find annoying, at best. I'm not aware of anyone having concerns over the site's bandwidth usage, although I'm sure there are at least a handful of monks who do have such concerns.
  • Comment on Re: New Design for Sending + - votes on PerlMonks

Replies are listed 'Best First'.
Re^2: New Design for Sending + - votes on PerlMonks
by eyepopslikeamosquito (Archbishop) on Jul 16, 2025 at 08:40 UTC
      I can't find a suitable word to describe the downsides of using HTML tables for displaying images here.

      But there are alternatives allowing a lot of details without bandwith problems.

      • Base64 encoding
      • SVG
      And less so
      • ASCII graphics
      I had to use the latter multiple times in the past and it was kind of bothersome moving characters by hitting the bar.

      But a nodelet-hack to extend the ability of the local markup to show base64 or SVG could be an easy proof of concept.

      Alas I doubt that's our top priority here.

      FWIW here a POC:

      The Perl Onion as Base64

      The Perl Onion as SVG

      UPDATE

      You can copy either code into your Free Nodelet Settings to see the effect. (Don't forget to activate the free nodelet to be shown in your nodelet tab)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery