Search results for Decoded+the+HTML
@harryhalpin @rossjanderson @nymproject to decrypt (if the content was encrypted), verify PGP signatures (for signed content) and decoded it into web pages HTML, images etc so you could point a browser at this local proxy pulling content out of a local USENET feed. as reading is passive it becomes hard to observe.
@SWRadiogram For the sake of completeness here a collage of the RC17 reception last Thursday. From the decoded HTML playlist I made a corresponding cue sheet that matches with the 30 min brodcast via WRMI. Here encoded in EasyDRF/DRM: dropbox.com/scl/fi/ck5o0rr…
@joaxcar @avlidienbrunn Yep, attributes get HTML decoded due to DOMPurify .innerHTML usage to serialize the DOM tree. I'll try to fuzz it when I come back home, I'll DM you if I find anything interesting ;)
I couldn't resist: Optimizing my browser-based DOS game remake to run from a 5.25" floppy. 💾 The server hosts the game, on disk. A boot loader of sorts fetches gzip-encoded HTML + JS + CSS files from disk, decoded via DecompressionStream(). A fun throwback experiment.
...a .lnk file and an HTML file. However, the current version spreads through spear phishing emails with a ZIP file attachment. The ZIP file drops a JScript file, which then drops an encrypted DLL file that is decoded and executed.
Interesting, copying a Figma frame and then viewing the clipboard in Clipboard Viewer (langui.net/clipboard-view…) shows this metadata in "public.html" clipboard record. Perhaps the string starting "(figma)" could be decoded as base64 and then passed to some Figma parser?
Be careful with the context (both clients and servers). « A query parameter can be url decoded on the server side whereas the text content of an html element may be html decoded client side »@PortSwigger
A weak and fading signal for the last Shortwave Radiogram EasyDRF special on 5850kHz at 0800UTC via a Columbia KiwiSDR IQ recording. The HTML decoded, but fading then took the signal below threshold for images 1, 2 and 3. After that, the signal came way up! @SWRadiogram
The html has decoded via an SDR in the upper lower peninsula of Michigan, despite a high noise floor. During the 1530-1600 UTC broadcast, 9955 kHz from WRMI Florida.
From IQ recording of 1300-1330 UTC broadcast, 15770 kHz from WRMI Florida, received via SDR in France, all html and images decoded from USB playback. Nothing decoded in LSB because of the RTTY-like signal just under 15770.
Via Switzerland SDR, IQ recording, USB playback, the html and first image decoded. It won't be a full set of images. And I can't try LSB because of an RTTY-like signal just under 15770. During the 1300-1330 UTC show, 15770 kHz from WRMI Florida.
Direct reception in Virginia on my Yaesu FT897D in USB mode, with 6/10M vertical on the roof. Html decoded, and it looks like all the images will appear. During the 1300-1330 UTC show, 15770 kHz from WRMI Florida.
Shortwave Radiogram EasyDRF special, 9265kHz, decoded live via the Weston-Super-Mare, UK KiwiSDR. Missed the first two files due to low SNR, so I had to borrow the HTML from the test to display stats... @SWRadiogram
@__xuorig__ If so: 1. You could allow arbitrary requests from arbitrary clients to receive a GraphQL response to their first HTTP request, in parallel with any SSR’ed HTML. 2. You don’t need a DB to store the set identifiers, because they are stored in the URL and decoded from there.
Oh no decoded the HTML source code! Gasp 😮
Oh no decoded the HTML source code! Gasp 😮
@rvanlaar @terrajobst @kaitai_io ImHex can also export highlights made by the pattern language as HTML code so you can embed the hex view in a web page and still hover over the bytes to see the decoded values
Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code 😬
First GRC-img prototype 👀 🔹Note that the image render updates according to data pulled from simple html (few bytes) 🔹 Data presented are inscription height (future prototype) and DNA 🔹DNA (hex) is used to store traits IDs which are then decoded to layers and rendered
First GRC-img prototype 👀 🔹Note that the image render updates according to data pulled from simple html (few bytes) 🔹 Data presented are inscription height (future prototype) and DNA 🔹DNA (hex) is used to store traits IDs which are then decoded to layers and rendered https://t.co/KxEVyRBXjj
So for <img>s in your initial HTML the browser will spot it, queue it for downloading, and happily render other stuff while that’s happening. After it’s downloaded, it will be decoded and likely be drawn in its own frame anyway with little to “sync” or not.