@Floppy @amcewen

The "which BIT" and the - as I call it - #LinkedData conundrum, I addressed recently in a #SocialHub topic on the #JSONLD vs plain #JSON nature of #ActivityPub. Inspired to write a long and personal #SocialExperience tale on my travels in wild #fedi lands. See..

https://social.coop/@smallcircles/116368803389082089

The #EU @ngi #grant programs and the hard work of @nlnet to distribute @EUCommission Horizon Europe #funding has done wonders to take #fediverse where it stands today. In my article I list all the many #FOSS projects that received stimulus and support during the years.

However something fundamental has been lacking in the mandate on who is eligible. Coding is Social. The support does not cover the rich tapestry of #expertise that end-to-end #solutions need during their lifecycle. Does not include fostering cohesive #technology ecosystems, healthy #OpenStandards evolution.

Effectively this creates a 'handover point' of software code from poor FOSS to others who earn a living with it.

Föderation kann durchaus trickreich sein...

Um die Anzahl Likes und Shares (zwischen den Instanzen) besser abzugleichen, läuft via #ActivityPub gern eine Information über die aktuellen Zahlen, die ein Beitrag aktuell mit sich führt. (#Mastodon ab v4.3 - meine ich - führte z.B. [likes] und [shares]-Elemente ein).

Bei #Mammuthus habe ich das vor einiger Zeit auch implementiert bzw. eben auch die Aktualisierung von Zahlen von Beiträgen auf anderen Instanzen.

Und jetzt kommt der Haken der eingangs erwähnten trickreichen Föderation.

Mir fielen Unstimmigkeiten auf und bei Analyse stellte sich heraus, daß z.B. ein Announce eines Beitrags von einer dritten Instanz auf meiner Instanz einlief, bevor die Originalinstanz, dessen Beitrag geteilt wurde, davon Wind bekommen hatte. Vertraue ich in diesem Fall auf die Zahlen der Originalinstanz, liege ich leider falsch.

Also gleiche ich nun drei Zahlenwerte ab, sofern notwendig und passe die Anpassung passend an... 😉

Ich vergleiche die via #ActivityPub gelieferten Zahlen (bzw. die Zahlen aus einer #JSON-Anfrage an die Originalinstanz) mit den Zahlen, die als Cache-Wert direkt beim Beitrag gespeichert sind sowie einer wirklichen Durchzählung in der Datenbank.

Wollte ich mal kundgetan haben... 😎

People keep reinventing serialisation, generally badly. A year ago I proposed my own as a joke:

https://wiesmann.codiferes.net/wordpress/archives/38143

What I find fascinating, is that I keep seing proposals which are probably worse…

#serisalisation #json #cbor #serialization

The grumpy serialisation format

Every few years we reinvent data serialisation. CDR (CORBA) replaced EDI, and was replaced by XML, and now, clearly JSON is the solution, while ASN.1 still lurks in the shadows. And then it stuck m…

Thias の blog
Four months in the making; #Agama 19 rewrites the foundation of the #openSUSE installer. Stable #API coming soon, new installation modes, and backwards-compatible #JSON profiles. Feedback and bug reports welcome on #GitHub! #Linux https://agama-project.github.io/blog/2026/03/20/agama-19
Agama 19 - A New Beginning | Agama

In our previous post from November 2025 we already told you to expect a

Пошаговые диалоги в Python без боли: описываем визарды в JSON, а не в if-ах

Писать сложные диалоги в Telegram-ботах — это боль из вложенных if -ов, сломанных переходов и бесконечного рефакторинга. В этой статье — как мы вынесли всю логику визардов в JSON и сделали движок, который сам управляет шагами, условиями и навигацией. Без спагетти-кода. Без привязки к платформе. С возможностью собрать рабочего бота за вечер.

https://habr.com/ru/articles/1022354/

#python #telegram_bot #aiogram #wizard #диалоги #json #state_machine #backend #dialog_engine #чатботы

Пошаговые диалоги в Python без боли: описываем визарды в JSON, а не в if-ах

Каждый, кто делал Telegram-бота с анкетой длиннее трёх вопросов, знает это чувство. Сначала всё просто: спросил имя, спросил email, записал в базу. Потом продакт говорит: «а давай если пользователь...

Хабр

RE: https://mastodon.social/@Mastodon/116402716327956884

Glad to see things like search and discovery #FASP, although it doesn't seem like FASPs are being modeled with an #ActorModel or #JSON-LD in mind. Another thing I'd like to see implement is federated search (#sparQL has prior art)

𝗞𝗲𝘆𝘀𝘁𝗮𝘁𝗶𝗰:

#ContentManagment #Markdown #JSON #YAML #Keystatic

https://thewhale.cc/posts/keystatic

Content Management for your Codebase. A tool that makes Markdown, JSON and YAML content in your codebase editable by humans. Live edit content on GitHub or your local file system, without disrupting your existing code and workflows.

I wrote an opinionated piece about using decoders to deserialize JSON instead of reflection like is common in most languages

https://hashset.dev/article/2026/03/21/reflecting-on-deserialization-why-you-should-explicitly-decode-your-json/

#gleam #json
Reflecting on deserialization. Why you should explicitly decode your JSON.

When working with JSON, 99% of the time developers write a custom type that closely matches the format of the JSON payload, and then use their favorite programming languages built in metaprogramming ability to automatically deserialization the payload into a typed object. I want to tell you why you shouldn't use reflection and instead take a page out of functional programming and explicitly decode the JSON payload.

Hashset - Kai Ito

#OpenDataLoader PDF — #opensource #PDF parser for #AI & #accessibility 🚀 #1 in benchmarks (0.90 overall), runs 100% locally, zero cloud, no GPU needed. #RAG #LLM #Python #NodeJS #Java

📄 Extracts #Markdown, #JSON (with bounding boxes) & #HTML from any PDF — correct reading order, heading hierarchy, list & image detection with XY-Cut++ algorithm

🧵👇#pdf