I need to check out [Wayback/Archive.is] The Time Travel Debugger for Web Development:
one frame of the replay.io demo
Posted by jpluimers on 2023/06/27
I need to check out [Wayback/Archive.is] The Time Travel Debugger for Web Development:
one frame of the replay.io demo
Posted in Development, JavaScript/ECMAScript, Scripting, Software Development | 1 Comment »
Posted by jpluimers on 2023/06/26
[Wayback] 150629 UM IM SM Tzerra M NL.pdf – Remeha
Installatie-, gebruikers- en servicehandleiding Condenserende gaswandketels Tzerra M 15s Plus – 24/28c Plus – 25s Plus – 35s Plus – 35/40c Plus
–jeroen
Posted in Hardware, LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2023/06/23
For my link archive:
–jeroen
Posted in LifeHacker, Power User, Solar Power | Leave a Comment »
Posted by jpluimers on 2023/06/22
Boy, I wonder what can go wrong with [Wayback/Archive] Yes, I can connect to a DB in CSS
Via: [Wayback/Archive] Kris on Twitter: “… “Yes, I can connect to a DB in CSS” Abusing houdini.how, and using a JS version of Sqlite, CSS can connect to a DB.” / Twitter
Related:
–jeroen
Posted in CSS, Database Development, Development, Software Development, SQLite, Web Development | Leave a Comment »
Posted by jpluimers on 2023/06/21
For my link archive: [Wayback/Archive] doegox/EMV-CAP: This tool emulates an EMV-CAP device, to illustrate the article “Banque en ligne : à la decouverte d’EMV-CAP” published in MISC, issue #56.
Via: [Archive] Philippe Teuwen on Twitter: “Our 10 years old EMV-CAP emulator is now republished on Github under GPL3+, use it responsibly! …” / Twitter
Related:
–jeroen
Posted in Development, Python, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2023/06/20
[Wayback/Archive] ~mvforell/toluol – sourcehut git: Rust tool to make DNS queries
From [Archive] Max on Twitter: “@b0rk Shameless plug of an alternative to dig I’ve written: … It’s not complete yet (it can’t do what dig +trace does), but it’s getting there :) I’m also planning to add coloured output to make it more readable. …” / Twitter
In a reaction to [Archive] 🔎Julia Evans🔍 on Twitter: “I wish dig‘s output actually looked like this? I feel like there’s no reason (except compatibility or whatever) that it has to be as unreadable of it is …” / Twitter
Posted in *nix, *nix-tools, Development, dig, Power User, Rust, Software Development | Leave a Comment »
Posted by jpluimers on 2023/06/19
I archived a long thread that started with [Archive] 𝚓𝚘𝚗𝚗𝚢﹏𝚜𝚊𝚞𝚗𝚍𝚎𝚛𝚜 on Twitter: “More fun publisher surveillance: Elsevier embeds a hash in the PDF metadata that is unique for each time a PDF is downloaded, this is a diff between metadata from two of the same paper. Combined with access timestamps, they can uniquely identify the source of any shared PDFs. ” / Twitter at [Wayback/Archive] Thread by @json_dirs on Thread Reader App – Thread Reader App.
TL;DR: publishers put hashes in PDF metadata to track back redistribution; they hardly use smarter watermarking as those are difficult to automatically parse; the hashes can be easily removed.
Posted in Hashing, LifeHacker, PDF, Power User, Security | Leave a Comment »
Posted by jpluimers on 2023/06/16
For my link archive: [Wayback/Archive] Heffingsvrij vermogen – Uitleg vrijstelling box 3 | Spaarrente.nl
–jeroen
Posted in LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2023/06/15
Every time I use YAML, I bump into things even I copy paste from exact working configurations.
Today I learned I’m not just alone, but there is even a term for it: “YAML-NOrway Law.”
[Wayback/Archive] I’d like to propose the “YAML-NOrway Law.” “Anyone who uses YAML long enough wil… | Hacker News
I’d like to propose the “YAML-NOrway Law.”
“Anyone who uses YAML long enough will eventually get burned when attempting to abbreviate Norway.”
Example:
NI: Nicaragua NL: Netherlands NO: Norway # boom!`NO` is parsed as a boolean type, which with the YAML 1.1 spec, there are 22 options to write “true” or “false.”[1] For that example, you have wrap “NO” in quotes to get the expected result.
This, along with many of the design decisions in YAML strike me as a simple vs. easy[2] tradeoff, where the authors opted for “easy,” at the expense of simplicity. I (and I assume others) mostly use YAML for configuration. I need my config files to be dead simple, explicit, and predictable. Easy can take a back seat.
[1]: [Wayback/Archive] http://yaml.org/type/bool.html [2]: [Wayback/Archive] https://www.infoq.com/presentations/Simple-Made-Easy
Even a key Ansible author seems to regret using YAML: [Archive] Kevin Honka on Twitter: “@hikhvar @isotopp jap :) Muss da immer an den Spruch des entwicklers von Ansible denken: Hätte ich gewusst, wie einfach es ist in Python eine DSL zu bauen, hätte ich nie YAML verwendet” / Twitter
Somewhere in the tread, Kris mentioned [Wayback/Archive] Code rant: The Configuration Complexity Clock:
It seems to be a recurring issue in both Kris’ and my life: One needs to actually fail in order to get a feel for reality.
Via [Archive] Kris on Twitter: “Die YAML Spezifikation gelesen. yaml-dox-url Jetzt habe ich Alpträume. “Erkläre Node Tags, Complex Keys mit ?, resolved und unresolved tags, und partial representation.”” / Twitter
[Wayback/Archive] YAML Ain’t Markup Language (YAML™) revision 1.2.2
–jeroen
Posted in Configuration Management, Infrastructure, YAML | Leave a Comment »