<?xml version="1.0" encoding="utf-8"?><svg id="Klienos_SVG_…
<?xml version="1.0" encoding="utf-8"?><svg id="Klienos_SVG_hack" width="508" height="508" version="1.1" viewBox="0 0 100% 100%" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><switch><foreignObject x="0" y="0" width="100%" height="100%"><style>svg {object-fit: contain; background-color: rgba(255, 255, 255, 0.3); font-size: 20px;} p {margin: 0; overflow-wrap: break-word;}</style><p xmlns="http://www.w3.org/1999/xhtml"><style>p{background:radial-gradient(ellipse at center,#12b7fc 0,#9000ff 100%);text-align:center;height:100%;color:#fff;font:64px sans-serif;letter-spacing:-2px;text-shadow:1px 2px 5px rgba(0,0,0,.65)}</style><p>This isn't an image. 👀 Thx Klimenos! 🔥</p></p></foreignObject><text x="0" y="0">Sorry, your browser does not support this SVG.</text></switch>Sorry, your browser does not support this SVG.</svg>
Replies
Well, that was my first test, and it appears that an image is generated in the end. Forgive my bold statement above? 🤷♂️ Regardless, this is some awesomesauce @100
Right on. I inspected the element on my Twetch post, and it was rendered as an <img>, so I suppose since the <img src> is SVG data in the transaction, Twetch renders the vector within the <img> tag.
I could be wrong/off-point, but this is some cool $#!+
Indeed they are. I was mistakenly assuming the <img> was always a raster/bitmap. But that would make no sense because it would mean that Twetch would convert the bico.media vector to bitmap, and display that. Nope! Thanks for the clarifications!