toad.social

dilawar<a href="https://crates.io/crates/dicom-dump" rel="nofollow noopener" translate="no" target="_blank">https://crates.io/crates/dicom-dump</a> is an excellent <a href="https://fosstodon.org/tags/cli" class="mention hashtag" rel="nofollow noopener" target="_blank">#cli</a> utility to extract data from <a href="https://fosstodon.org/tags/dicom" class="mention hashtag" rel="nofollow noopener" target="_blank">#dicom</a> files. You can extract data as <a href="https://fosstodon.org/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a>.And it is much faster than popular <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> utility out there. Written in <a href="https://fosstodon.org/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> 😛

onipa 🇬🇭📖Currently appreciating the beauty of JSON (and its mascot?) I'm working on a little project a lexicon/dictionary called texdict.py (name suggestions welcome). The <a href="https://pixelfed.social/discover/tags/python?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#python</a> script attempts to convert a <a href="https://pixelfed.social/discover/tags/TeXLaTeX?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#TeXLaTeX</a> file with glossaries commands (<a href="https://ctan.org/pkg/glossaries" rel="nofollow noopener" target="_blank">https://ctan.org/pkg/glossaries</a>) and some extra commands (which might be released under texdict.sty (or similar name)) into JSON format and vice-versa. JSON is so nice because it's human readable and computer readable. Do you know of any <a href="https://pixelfed.social/discover/tags/LaTeX?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#LaTeX</a> packages and or <a href="https://pixelfed.social/discover/tags/JSON?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#JSON</a> based libraries related to <a href="https://pixelfed.social/discover/tags/dictionaries?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#dictionaries</a> or <a href="https://pixelfed.social/discover/tags/lexicon?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#lexicon</a> Also, I thought about using the texdict.sty file as the only source of truth for the tex2json and json2tex mapping, but haven't figured it out yet. Any leads would be highly appreciated 🖤📖💽

Marcos DioneWho hasn't seen JSON on JSON a.k.a. JSON encoded JSON. As in:``` { "a": "{ \"b\": 0 }" } ```Why do people even do that? Why not``` { "a": { "b": 0 } } ```Also: has anyone ever seen YAML encoded YAML? Does it even exist?All this just to promote my new tool:<a href="https://codeberg.org/mdione/jsjs" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/mdione/jsjs</a><a href="https://en.osm.town/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a> <a href="https://en.osm.town/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a>

Stéphane BortzmeyerSide discussion at <a href="https://mastodon.gougere.fr/tags/IETF123" class="mention hashtag" rel="nofollow noopener" target="_blank">#IETF123</a>. Is there an equivalent of <a href="https://mastodon.gougere.fr/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> for <a href="https://mastodon.gougere.fr/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a> (to control the presentation of the JSON you send)? Any ideas?

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕JWTs Are Not Session Tokens , Stop Using Them Like OneWhen JSON Web Tokens (JWTs) hit the mainstream, they were hailed as the solution to everything wrong with session management. Stateless! Compact! Tamper-proof! Suddenly, everyone started stuffing them into every web app like ketchup on bad code.🧑‍💻 <a href="https://archive.fo/01UkP" rel="nofollow noopener" translate="no" target="_blank">https://archive.fo/01UkP</a><a href="https://chaos.social/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> <a href="https://chaos.social/tags/jwt" class="mention hashtag" rel="nofollow noopener" target="_blank">#jwt</a> <a href="https://chaos.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://chaos.social/tags/token" class="mention hashtag" rel="nofollow noopener" target="_blank">#token</a> <a href="https://chaos.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://chaos.social/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a> <a href="https://chaos.social/tags/bad" class="mention hashtag" rel="nofollow noopener" target="_blank">#bad</a> <a href="https://chaos.social/tags/badcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#badcode</a> <a href="https://chaos.social/tags/WebTokens" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebTokens</a> <a href="https://chaos.social/tags/ketchup" class="mention hashtag" rel="nofollow noopener" target="_blank">#ketchup</a>

Angel D. MunozA small release is out for JDeck. This release adds functions to decode F# Maps and BCL Dictionaries which were missing from the last bit (link to release in the next tweet)<a href="https://github.com/AngelMunoz/JDeck/releases/tag/v1.0.0-rc-002" rel="nofollow noopener" translate="no" target="_blank">https://github.com/AngelMunoz/JDeck/releases/tag/v1.0.0-rc-002</a><a href="https://hachyderm.io/tags/fsharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#fsharp</a> <a href="https://hachyderm.io/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://hachyderm.io/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> <a href="https://hachyderm.io/tags/jsonserializer" class="mention hashtag" rel="nofollow noopener" target="_blank">#jsonserializer</a> <a href="https://hachyderm.io/tags/library" class="mention hashtag" rel="nofollow noopener" target="_blank">#library</a> <a href="https://hachyderm.io/tags/buildinpublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildinpublic</a>

Soliman HindyMastering JQ: Part 1 source: <a href="https://codefaster.substack.com/p/mastering-jq-part-1-59c" rel="nofollow noopener" translate="no" target="_blank">https://codefaster.substack.com/p/mastering-jq-part-1-59c</a><a href="https://mastodon.lovetux.net/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a>

mirabilos“Fun” learning YAML properly?Okay. So. I have to learn ANSI-Bell for $ork. Meh. But okay.Pre-existing “fun”Playbooks are written in YAML. I hate YAML and have always used <a href="https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=useful-scripts/useful-scripts.git;a=blob;f=misc/yaml2jsn.php;hb=HEAD" rel="nofollow noopener" target="_blank">yaml2jsn</a> to convert it to JSON (if possible) when I had to touch it in the past, as somehow a subset¹² of JSON is a valid subset of YAML accepted² by YAML parsers.① you’ll have to make sure you don’t emit some codepoints literally, and to format numbers in scientific notation a specific way, but that’s generally a good advice for JSON emitters ② except JSON strings have codepoints outside the Basic Multilingual Plane encoded as two UTF-16 surrogates in <code>\u####</code> notation whereas YAML parsers require it to be unescaped four-octet UTF-8, which breaks many JSON parsers; I ran into that just this week, in fact, for my RSS to Fediverse gateways…I personally find YAML unwritable, due to things like GitHub Actions’ example of…<pre><code>on: push: branches: - main </code></pre>… does not convert to…<pre><code>{ "on": { "push": { "branches": [ "main" ] } } } </code></pre>… but to:<pre><code>{ "1": { "push": { "branches": [ "main" ] } } } </code></pre>(GitHub accepts both syntacēs in workflow files in JSON.)But let’s go back to the “self-explaining, obvious” YAML:<pre><code>on: push: branches: - main </code></pre>So, we’ve already established that “on” is 1 and that something like <code>country: no</code> isn’t Norway but 0 (and real existing people have fallen into this, yet there are strong recommendations to not quote strings in YAML documents like ANSI-Bell playbooks, and somehow nobody even documents how strings are to be escaped and when they need to be escaped).But, riddle me this:<pre><code>push: <2 spaces>branches: </code></pre>But:<pre><code>branches: <2 spaces><hyphen-minus and space>main </code></pre>But:<pre><code>options: <no space><hyphen-minus and space>Ubuntu <no space><hyphen-minus and space>macOS </code></pre>(All examples from <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions" rel="nofollow noopener" target="_blank">here</a>.)I find this totally obvious and self-explanatory and consistent, and I totally know when to use two spaces, or dash-plus-space, or both.</sarcasm>But there is training material!One of the books I’ve been provided (actual published training material with an ISBN each) just hand-waves it away, the other says:<blockquote>The target section looks like the following code snippet:<pre><code> - hosts: webservers user: root </code></pre>[…] As per the YAML syntax, the line must start with a dash. […]</blockquote>So, basically, the <code>hosts:</code> line must start with a <del>dash</del>hyphen-minus? I think not.The “Hands-on interactive lab and helpful resources” in the Red Hat “YAML essentials for Ansible” “learning path” is similarly deficient in even fundamentally basic explanation. 0/10, won’t recommend. Fun with training material, continuedThe hand-waving book links to <a href="http://www.yaml.org/start.html" rel="nofollow noopener" target="_blank"><code>http://www.yaml.org/start.html</code></a>, so let’s read…<blockquote>a getting started guide for YAML</blockquote>… in my favourite webbrowser <code>lynx</code>:<pre><code> Page not found · GitHub Pages File not found The site configured at this address does not contain the requested file. If this is your site, make sure that the filename case matches the URL as well as any file permissions. For root URLs (like http://example.com/) you must provide an index.html file. [1]Read the full documentation for more information about using GitHub Pages. [2]GitHub Status — [3]@githubstatus Edit this document's URL: https://yaml.org/start.html </code></pre>… oooookay?But surely <code>yaml.org</code> has more material? *looks* … well, it has links to the specs and implementations. All very useful, but not right now for a hopefully structured introduction that explains the hows and ideally also the whys.Let’s follow the <code>*New*</code> link in which they announce the 1.2.2 spec… a blogpost. Okay. It has a title bar (brown background in Firefox) with a promising link:<pre><code> Y * * [2]Blog * [3]Docs </code></pre>Let’s follow #3 to “Docs”!<pre><code>←←← Twitter [1]Skip to main content Y * * [2]Blog * [3]Docs * * [4]YAML Glossary [5]YAML Cheat Sheet (BUTTON) Menu YAML Documentation __________________________________________________________________ YAML documentation is on the way! #content </code></pre>This 80×24 screenshot is literally the entirety of the official <a href="https://toot.mirbsd.org/tags/yaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#YAML</a> documentation.Well, colour me impressed.Wait, no.Fuck that shit.Wait. This is for $dayjob. $customer also edits playbooks. I’m sure they’ll be delighted if I run things through <a href="https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=useful-scripts/useful-scripts.git;a=blob;f=misc/yaml2jsn.php;hb=HEAD" rel="nofollow noopener" target="_blank">yaml2jsn</a> and commit the result as <a href="https://toot.mirbsd.org/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a>.Also, see footnote 2 above.Fuuuuck I’m SOL.So. Do I honestly have to wade through the spec to learn this?(Not that this is new. When I first learnt Python in 2008, I had to look at the C-language source code of the <a href="https://toot.mirbsd.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> interpreter to figure out things missing from the documentation. Which brings us back full circle to <a href="https://toot.mirbsd.org/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a>, the culprit of bringing this entire shitshow to my attention. I’m a programmer, not a DevCloudOp or something.)

technicatI used to hate seeing this used in <a href="https://universeodon.com/tags/commonlisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#commonlisp</a> but I'm doing the equivalent more and more decoding <a href="https://universeodon.com/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> <a href="https://universeodon.com/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> in <a href="https://universeodon.com/tags/swiftlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#swiftlang</a><a href="https://lisp-docs.github.io/cl-language-reference/chap-9/j-c-dictionary/ignore-errors_macro" rel="nofollow noopener" translate="no" target="_blank">https://lisp-docs.github.io/cl-language-reference/chap-9/j-c-dictionary/ignore-errors_macro</a>

makemakehow is there not a <a class="hashtag" href="https://pleroma.makemake.site/tag/rust" rel="nofollow noopener" target="_blank">#rust</a> library for defining a how a <a class="hashtag" href="https://pleroma.makemake.site/tag/json" rel="nofollow noopener" target="_blank">#json</a> object should look like and rejecting anything that doesnt match it exactly? <a class="hashtag" href="https://pleroma.makemake.site/tag/programming" rel="nofollow noopener" target="_blank">#programming</a> <a class="hashtag" href="https://pleroma.makemake.site/tag/infosec" rel="nofollow noopener" target="_blank">#infosec</a> <a class="hashtag" href="https://pleroma.makemake.site/tag/pentest" rel="nofollow noopener" target="_blank">#pentest</a>

Gytis RepečkaThis meme is so good it has to be shared widely: <code>{"</code> :jason_statham: <code>"}</code><a href="https://social.gyt.is/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> <a href="https://social.gyt.is/tags/statham" class="mention hashtag" rel="nofollow noopener" target="_blank">#statham</a> <a href="https://social.gyt.is/tags/meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#meme</a>

Carlo ZottmannWorking with <a href="https://norden.social/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a> a lot? Even if you work with and are comfortable with `jq`, don't sleep on `fx`, because it's a nice alternative that brings its own strengths to the table.<a href="https://fx.wtf" rel="nofollow noopener" translate="no" target="_blank">https://fx.wtf</a>

CliffI just realized that I have now been using EchoFeed by <a href="https://social.lol/@robb" class="u-url mention" rel="nofollow noopener" target="_blank">@robb</a> for a year!The service that EchoFeed provides is unmatched in my opinion. It allows me to send posts from so many platforms such as my SeerOfSouls.com blog, Vernissage, CrucialTracks and so much more to so many places across the web including to Mastodon, Discord, GitHub and many others. If you've not given EchoFeed a try, don't hesitate any longer as you can check it out via the link below. You won't be disappointed..<a href="https://EchoFeed.app" rel="nofollow noopener" translate="no" target="_blank">https://EchoFeed.app</a> <a href="https://infosec.exchange/tags/EchoFeed" class="mention hashtag" rel="nofollow noopener" target="_blank">#EchoFeed</a> <a href="https://infosec.exchange/tags/Blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blog</a> <a href="https://infosec.exchange/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> <a href="https://infosec.exchange/tags/Discord" class="mention hashtag" rel="nofollow noopener" target="_blank">#Discord</a> <a href="https://infosec.exchange/tags/Feeds" class="mention hashtag" rel="nofollow noopener" target="_blank">#Feeds</a> <a href="https://infosec.exchange/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSS</a> <a href="https://infosec.exchange/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a> <a href="https://infosec.exchange/tags/Atom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Atom</a>

Daniel BowenMy local station is {"text":"Bentleigh"} <a href="https://mastodon.social/tags/Melbourne" class="mention hashtag" rel="nofollow noopener" target="_blank">#Melbourne</a> <a href="https://mastodon.social/tags/PublicTransport" class="mention hashtag" rel="nofollow noopener" target="_blank">#PublicTransport</a> <a href="https://mastodon.social/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a>

Dave MasonMy latest endeavor involved exporting data to a semi-structured (and that's being generous) file, parsing it for 'parent' values and name/value pairs...then further parsing that data into JSON, storing it in a SQL Server table, and creating a god-awful view that uses OPENJSON to coerce hierarchical data into a tabular format.<a href="https://mastodon.social/tags/SQLServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQLServer</a> <a href="https://mastodon.social/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a>

ResearchBuzz: FirehoseShane O’Sullivan: Search Huge JSON files on the Web. “Working with very large JSON files (20MB+) using online tools tends to be a crashy affair. Whether you’re looking to format or search them, all the tools I found just crash. I found myself having to work with huge JSON files recently, so I built a tool specifically optimized for huge JSON files, called Huge JSON Viewer.”<a href="https://rbfirehose.com/2025/06/19/shane-osullivan-search-huge-json-files-on-the-web/" class="" rel="nofollow noopener" target="_blank">https://rbfirehose.com/2025/06/19/shane-osullivan-search-huge-json-files-on-the-web/</a>

Terence EdenOK Fedifriends, I need your help with some complex ActivityPub stuff.Mastodon won't show a list of followers for <a href="https://colours.bots.edent.tel/colours" class="u-url mention" rel="nofollow noopener" target="_blank">@colours</a> It has an orderedcollection at <a href="https://colours.bots.edent.tel/followers" rel="nofollow noopener" translate="no" target="_blank">https://colours.bots.edent.tel/followers</a> which paginates properly.The mimetype and JSON are all correct, I think.You can check out the source code at <a href="https://gitlab.com/edent/activity-bot/" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/edent/activity-bot/</a>What magical incantation do I need to do to help Mastodon see the details of the account's followers?Feel free to reply here or on the repo.<a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/MastodonAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastodonAPI</a> <a href="https://mastodon.social/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a>

Thomas Cherryhomes<a href="https://oldbytes.space/tags/PlusCart" class="mention hashtag" rel="nofollow noopener" target="_blank">#PlusCart</a> and <a href="https://oldbytes.space/tags/FujiNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#FujiNet</a> work together to bring a larger Internet platform to the <a href="https://oldbytes.space/tags/Atari2600" class="mention hashtag" rel="nofollow noopener" target="_blank">#Atari2600</a>.Here we see it tracking the position of the International Space Station using a <a href="https://oldbytes.space/tags/JSON" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSON</a> feed from a web API. Cool, huh?<a href="https://oldbytes.space/tags/retrogaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrogaming</a>

Alvin Ashcraft 🐿️What's new in SQL Server 2025 | Microsoft Mechanics with Bob Ward & Jeremy Chapman.<a href="https://www.youtube.com/watch?v=PvA3Ah3JJxg" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=PvA3Ah3JJxg</a> <a href="https://hachyderm.io/tags/sqlserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#sqlserver</a> <a href="https://hachyderm.io/tags/database" class="mention hashtag" rel="nofollow noopener" target="_blank">#database</a> <a href="https://hachyderm.io/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#data</a> <a href="https://hachyderm.io/tags/sqlserver2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#sqlserver2025</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> <a href="https://hachyderm.io/tags/msfabric" class="mention hashtag" rel="nofollow noopener" target="_blank">#msfabric</a>

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕NaaS – No-as-a-ServiceNo-as-a-Service (NaaS) is a simple API that returns a random rejection reason. Use it when you need a realistic excuse, a fun “no,” or want to simulate being turned down in style. – from <a href="https://social.isalman.dev/users/hothead" class="u-url mention" rel="nofollow noopener" target="_blank">@hothead</a> ❌ <a href="https://github.com/hotheadhacker/no-as-a-service" rel="nofollow noopener" translate="no" target="_blank">https://github.com/hotheadhacker/no-as-a-service</a><a href="https://chaos.social/tags/naas" class="mention hashtag" rel="nofollow noopener" target="_blank">#naas</a> <a href="https://chaos.social/tags/noasaservice" class="mention hashtag" rel="nofollow noopener" target="_blank">#noasaservice</a> <a href="https://chaos.social/tags/api" class="mention hashtag" rel="nofollow noopener" target="_blank">#api</a> <a href="https://chaos.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://chaos.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> <a href="https://chaos.social/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a> <a href="https://chaos.social/tags/random" class="mention hashtag" rel="nofollow noopener" target="_blank">#random</a> <a href="https://chaos.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://chaos.social/tags/no" class="mention hashtag" rel="nofollow noopener" target="_blank">#no</a> <a href="https://chaos.social/tags/reaction" class="mention hashtag" rel="nofollow noopener" target="_blank">#reaction</a> <a href="https://chaos.social/tags/js" class="mention hashtag" rel="nofollow noopener" target="_blank">#js</a> <a href="https://chaos.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://chaos.social/tags/nonsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#nonsense</a> <a href="https://chaos.social/tags/asaservice" class="mention hashtag" rel="nofollow noopener" target="_blank">#asaservice</a> <a href="https://chaos.social/tags/joke" class="mention hashtag" rel="nofollow noopener" target="_blank">#joke</a>

Recent searches

Search options

Administered by:

Server stats:

#json