Notes
Short thoughts, updates, and quick posts. (1594 total)
-
The other fun project of the weekend was another kind of beast:
I wanted to be able to listen system output from specific RPG programs running on our AS400
The idea was the following:
could I generate a graph from dependencies used when X or Y RPG routine run?
I wanted to be able to map physical programs from libraries and other dependencies.
so I went the Java path since its the main language we use to interface with AS400 routines.
Then I used Neo4J to graph the output of the Java ibmi listening server.
I’m probably going to write a long form about this since it was really interesting to vibe code.
At some point I had to query the RPG routine themselves to be able to find key dependencies my main RPG routines were using.
so I basically created an API endpoint that I can query with specific program names to then find their dependencies and again graph the results to Neo4J
I still have to fine-tune the codebase before I publish this publicly but I’m pretty happy about the results
-
Fun weekend playing with Go to build a CLI + Web app dashboard to display commit/RC/Release deployment on our openshift cluster.
Data from Gitlab, Harbor, Openshift, Argocd
Multi namespaces, multi clusters, build RC tag & deploy to many with image build retag.
This is the third iteration of this idea originally developed in bash, then Python and now Go
the CLI is also able to act as a release manager tool, this means it uses Gitlab API to create SemVer RC tags that our tekton pipelines process differently on each environment:
- commit based build, test, deploy
- RC tag based that build, test, deploy in acceptance
- retag RC image to staging
- retag RC image to production
-
Well someone forgot to renew a certificate at #Bluesky
-
Massive work related step finished late Friday evening
- complete overhaul of our Tekton pipelines ci/cd for two of our biggest project in development.
we’ll be able to release faster with full rollback capabilities if needed and a very smooth tagging release strategy closely coupled to our Sprints.
Monday is going to be fun 😊
-
the whole #Artemis trip makes me want to project Artemis dashboard mission on my walls and have a stream of real time data decorate my living room along with beautiful planet earth 🌎 🌒 🚀 🌌
-
The joy #sarcasm of android mobile app development, I spent the entire day trying to make Deeplinking after a signature test return to my mobile app And just when I got it working I’m out of documents to sign 😅
-
Une belle semaine pleine d’avancées sur plusieurs fronts au boulot mais en particulier :
- mobile app Android/iOs
c’est fou la quantité de bazar à tenir en compte dans le développement d’une application mobile .
-
Fascinating to learn and put in practice mobile app development with an existing codebase (AngularJS member portal) for both #Android and #iOs
But the amount of bureaucracy it involves is astounding, all the while these two monopoly app stores (Google/Apple) are filled with spamware, malware and tons of dubious mobile apps.
The level of friction is huge.
One thing I know is that I will do my best so that our future mobile app is also published on FDroid and any other alternative store that make sense to use for distribution.
-
La série Devs… quel flop vraiment. Limite le concept était intéressant au début et puis … fallait qu’un tech bro joue à God pour revoir sa fille.
Si ça se trouve les plateformes dominants d’aujourd’hui sont toutes des résultantes de traumatismes profond sur des gars qui feraient mieux de suivre une bonne thérapie.
-
Using Claude Code to build an ActivityPub implementation for Indiekit, based on Fedify, was the easy part. (and it was a lot of fun 😊)
Building the UI to actually consume ActivityPub content, and layering a Mastodon-compatible API on top of it that works with existing apps and plays nicely with other AP implementations… that’s the real challenge.
Eating FEPs for dinner and reading how other implementations do things is how you realize just how much work is still ahead — and how many pain points are still unresolved.
Right now, my Indiekit blog has:
IndieWeb (Micropub, Microsub, Webmentions)
ActivityPub (server + reader)
If I wanted to self-host my own ATproto PDS, I’d also need to build an “AppView” to consume Bluesky content.
So I’d end up with:
one reader for RSS (my current Microsub)
one reader for ActivityPub (my native, still ugly AP reader)
one reader for ATproto
That’s a lot of readers for different data streams coming from different protocols.
At some point I thought: what if I just used my Microsub UI to consume everything — not just RSS/Atom/JSONFeed/h-feed?
Since Microsub already supports channels, I figured I could inject an AP timeline into a Microsub channel.
That idea fell apart pretty quickly.
RSS and h-feed from IndieWeb sites are straightforward. I know I can reply, like, repost, or bookmark because the other side supports the same interaction model.
But the moment I had to deal with ActivityPub — likes, boosts, replies — everything became different. The Microsub plugin would have needed so many protocol-specific features that my implementation would drift far from other Microsub implementations.
And I really didn’t like where that was heading.
Microsub turning into a universal ingestion layer for everything? That felt like a guaranteed mess.
So I drew a line: Microsub stays scoped to RSS/Atom/h-feed/JSONFeed. That’s it.
And yet… I’m still torn.
Because instead of one unified UI to consume RSS, ActivityPub, and ATproto, I’m now building three separate readers.
And that honestly feels like a huge waste.
So I’m dumping this conundrum here.
Maybe somewhere between the Fediverse and the Atmosphere, someone has already figured this out — or at least has a better idea.
Do you?
-
Survivre un crash disk…✅ et sans perte de données…mais punaise j’ai eu peur…
-
so painful to watch @evan@cosocial.ca patiently explain over and over tags.push and the way hashtags work on the Fediverse. I admire Evan patience and tone, but people should learn to read and inform themselves really because otherwise innovation on the Fediverse is a uphill battle even for the people that most contributed to it.
-
En France, pour que Justice se fasse, il ne suffit pas de porter plainte, ni de se ruiner avec des coûts exorbitants pour simplement accéder à la justice ⚖️.
Non — en plus de tout cela, les victimes doivent jongler avec l’insuffisance chronique des moyens alloués. Elles doivent subir les changements de juges d’instruction tous les deux ans, favorisant ainsi le non-traitement de dossiers déjà systématiquement oubliés — trop complexes, trop exigeants pour que la justice daigne vraiment “faire justice”.
Et pendant ce temps, alors même que les systèmes de police belge et français sont au courant d’une probabilité effective de récidive — les faits, les crimes dont sont accusés les principaux responsables n’ont jamais cessé de se dérouler tout au long des procédures judiciaires, depuis 1997 —
Et tout le monde s’en fout.
-
Anil’s Endgame for the Open Web is something everyone should read.
-
Listening how Trump has lost the Iran war hawks
-
Test from Phanpy to my own AP server with a link : https://diff.rmendes.net/
-
Test from Phanpy flow is mastodon API ⏭️ micropub ⏭️ Eleventy build ⏭️ Syndication to ActivityPub ⏭️ what you see 😎
-
This is a test (testing mastodon api layer on top of my AP implementation based on Fedify)