From #CTAN:
Jasper Habicht submitted an update to the jsonparse package.
Version: 1.5.0 2025-04-20
License: lppl1.3c
Summary description: Parse, store and access JSON data in LaTeX documents
ctan.orgCTAN: Paket jsonparse
Frühere Suchanfragen
Suchoptionen
#JSON
2 Beiträge2 Beteiligte0 Beiträge heute
#Blogger so: Hübscht eure #Blogs auf und optimiert sie für #AI mit #JSON.
Andere Blogger so: Hört mit dem Bullshit und den ausgedachten JSON-Formaten auf.
Blogger früher so: Liebes Tagebuch, heute war ein Scheißtag.
Wo sind wir Blogger denn falsch abgebogen? Wir wollten auf SEO verzichten und machen nun AI-O? Wozu? Um dem Ami Google noch mehr Daten zum Fraß vorzuwerfen? Wer sagt denn, dass mir das mit meinem Blog irgendwas bringt?
From #CTAN:
Jasper Habicht submitted an update to the jsonparse package.
Version: 1.4.0 2025-04-10
License: lppl1.3c
Summary description: Parse, store and access JSON data in LaTeX documents
ctan.orgCTAN: Paket jsonparse
From #CTAN:
Jasper Habicht submitted an update to the jsonparse package.
Version: 1.3.1 2025-03-30
License: lppl1.3c
Summary description: Parse, store and access JSON data in LaTeX documents
ctan.orgCTAN: Paket jsonparse
Canada
Full-time
HashiCorp
From #CTAN:
Jasper Habicht submitted an update to the jsonparse package.
Version number: 1.3.0 2025-03-25
License type: lppl1.3c
Summary description: Parse, store and access JSON data in LaTeX documents
www.ctan.orgCTAN: Paket jsonparse
From #CTAN:
Amir Mohammad Tahsiri submitted the BibBreeze package.
Version: 1.0
License: lppl1.3c
Summary description: A referencing package for automatically reconstructing bibliography data
ctan.orgCTAN: Paket BibBreeze
From #CTAN:
Jasper Habicht submitted an update to the jsonparse package.
Version: 1.2.3 2025-03-23
License: lppl1.3c
Summary description: Parse, store and access JSON data in LaTeX documents
ctan.orgCTAN: Paket jsonparse
Exploring Nix Derivations: A Hands-On Guide to Building with JSON
In the world of Nix, creating derivations can be both a challenge and an adventure. This article takes you through the intricate process of building a simple derivation from scratch using JSON, reveal...
https://news.lavx.hu/article/exploring-nix-derivations-a-hands-on-guide-to-building-with-json
Mastodon-Client-API
Auch wenn sich im #Fediverse viel um #ActivityPub dreht und hier durchaus auch eine #Client-Schnittstelle skizziert ist, nutzt #Mastodon eine eigene Client-API, die (zumindest teilweise) auch von anderer fediversaler Serversoftware unterstützt wird (z.B. #Friendica, #Firefish, #Mammuthus).
Diese #API (application programming interface, eine #Schnittstelle zur #Programmierung von Anwendungen) dient Apps und Clients dazu, entsprechende Funktionen auf einer #Instanz durchzuführen. Diese API ermöglicht die Entwicklung von Apps wie #Tusky, #Fedilab & Co.
Man kann diese API auch nutzen, um Konten etwa (teil)automatisiert zu betreiben.
Oder Statistiken zu sammeln... oder... oder... ;-)
Die API ist soweit öffentlich dokumentiert und steht frei zur Verfügung.
Allgemeine Dokumentation zu #Mastodon (auf Englisch):
https://docs.joinmastodon.org/
"Getting started with the API":
https://docs.joinmastodon.org/client/intro/
Wer mit dem Gedanken spielt, die API zu nutzen, sollte sich mit #HTTP, #JSON & Co. anfreunden können. Und Englischkenntnisse sind in diesem Bereich grundsätzlich von Vorteil...
docs.joinmastodon.orgMastodon documentationWelcome to the Mastodon documentation!
File format building blocks: primitives in digital preservation
by @beet_keeper
A primitive in software development can be described as:
a fundamental data type or code that can be used to build more complex software programs or interfaces.
– via https://www.capterra.com/glossary/primitive/ (also Wiki: language primitives)
Like bricks and mortar in the building industry, or oil and acrylic for a painter, a primitive helps a software developer to create increasingly more complex software, from your shell scripts, to entire digital preservation systems.
Primitives also help us to create file formats, as we’ve seen with the Eyeglass example I have presented previously, the file format is at its most fundamental level a representation of a data structure as a binary stream, that can be read out of the data structure onto disk, and likewise from disk to a data structure from code.
For the file format developer we have at our disposal all of the primitives that the software developer has, and like them, we also have “file formats” (as we tend to understand them in digital preservation terms) that serve as our primitives as well.
I can't really complain about the functionality of my brain synapses. It's just that with languages, they don't work the way I want them to. This also applies to programming languages – unfortunately.
My upcoming project requires data output. Of course, I'm familiar with the combination of #PHP and #MySQL, without being able to create both of them. I'm concerned about the how, since I won't be using any of the common monsters (WordPress, Drupal, etc.). I've heard of #frameworks and read various things about them, but – this is where it gets embarrassing – I just don't understand how to use them. However, I have a feeling they can help me [1]. Does anyone have any ideas how I can overcome my lack of understanding? #Linux #Programming #Database #json
[1] For example, the recently discovered #Flight
docs.flightphp.comÜber - Flight - An extensible micro-framework for PHPFlight is a fast, simple, extensible framework for PHP. Flight enables you to quickly and easily build RESTful web applications.
Ich kann mich wahrlich nicht über die Funktionalität meiner Gehirnsynapsen beschweren. Nur bei Sprachen wollen sie nicht so, wie ich es mir wünsche. Das gilt auch für Programmiersprachen – leider.
Für mein kommendes Projekt sollen Daten ausgegeben werden. Natürlich ist mir die Kombination #php und #mySQL bekannt, ohne beides selbst erstellen zu können. Mir geht es um das wie, da ich keines der verbreiteten Monster (Wordpress, Drupal usw.) einsetzen werde. Ich habe schon von #Frameworks gehört und diverses dazu gelesen, aber – jetzt wird es peinlich – ich kapiere einfach nicht, wie sie anzuwenden sind. Jedoch ahne ich, dass sie mir helfen können [1]. Hat jemand eine Idee, wie ich meine Begriffsstutzigkeit überwinden könnte? #Linux #Programmierung #Datenbank #json
[1] Z.B. das frisch entdeckte #Flight
docs.flightphp.comÜber - Flight - An extensible micro-framework for PHPFlight is a fast, simple, extensible framework for PHP. Flight enables you to quickly and easily build RESTful web applications.
found, not really a bug, an interesting behavior in C# and @godotengine
When parsing JSON, an int gets parsed to a float. Which probably makes sense, since everything in JavaScript is a float anyways.
But that then breaks the ulong parsing with a wrong format. Don't know if this is a new 4.4 behavior or if it was always this way. In any case it took me a while to find this bug in my code.
#csharp #godot #gamedev #indiedev #Godot4 #programming #programmingtips #JavaScript #json
![TL;DR: The code attempts to parse a floating-point number as an `ulong`, causing a `System.FormatException`.
Description: The image shows a debugging window in an IDE, evaluating an expression in C# within Godot. The expression tries to parse the `"total"` field from a `GodotDictionary` as an `ulong` using `ulong.Parse(data.AsGodotDictionary<string, string>()["total"])`. However, the value `"68.0"` is a floating-point number (with a decimal point), causing a `System.FormatException`. The error message indicates that the input string is not in the correct format for an unsigned long integer. The issue can be resolved by converting to `double` or `decimal` first, or by ensuring the value is an integer before parsing.](https://files.mastodon.online/media_attachments/files/114/170/657/126/963/273/original/cb62cfb9ddc72494.png "TL;DR: The code attempts to parse a floating-point number as an `ulong`, causing a `System.FormatException`.
Description: The image shows a debugging window in an IDE, evaluating an expression in C# within Godot. The expression tries to parse the `\"total\"` field from a `GodotDictionary` as an `ulong` using `ulong.Parse(data.AsGodotDictionary<string, string>()[\"total\"])`. However, the value `\"68.0\"` is a floating-point number (with a decimal point), causing a `System.FormatException`. The error message indicates that the input string is not in the correct format for an unsigned long integer. The issue can be resolved by converting to `double` or `decimal` first, or by ensuring the value is an integer before parsing.")
Make your #JSON pretty, colorful and scrollable
in terminal.
(command that output json) | jq -C | less
- jq -C -> indent and force color output
- less -> let you navigate through the result.
I may state the obvious, but it's always cool to know or remember 
.
With the impending end of Skype, I’ve gone and downloaded all my Skype data from Microsoft so I won’t lose decades of conversations with my friends.
Now I have a 35MB JSON file, with everything in it stuffed together.
I’m assuming there must be some good tools out there to examine the contents so I can figure out the data structure (my cheap IDE won’t handle files that big). Any recommendations? I’m not afraid of writing a parser from scratch, but I’m guessing there are libraries/tools out there already, since JSON is so common.
[Edit: thanks for all the helpful comments! Since originally posting this I found that someone has already built a tool to parse our Skype message files and has made it available here: https://becausecurious.me/skype_exports_for_humans ]
becausecurious.mebecausecurious.meA site of a very curious person.
clean-web.orgInvocation | clean-web.org