Notes
Short thoughts, updates, and quick posts. (1594 total)
-
This is a test from Phanpy -> Micropub -> Indiekit Syndicator -> ActivityPub -> Your timeline if you follow me :)
-
This is a test, from Phanpy -> Micropub -> Eleventy rebuild -> AP Syndication
-
@KevinMarks@xoxo.zone test reply from Phanpy
-
This is a test, from Phanpy -> Micropub -> Eleventy rebuild -> AP Syndication
-
My ActivityPub “reader” aka the view where I can check my home timeline and also explore public instance timeline is ugly but it works and it has this feeling that I built it, so if I’m not happy with it, I’m the only responsible to improve it.
Still… its an odd feeling that this is my fediverse home now and there is no coming back !
-
One day, I would like to meet a Wikipedia enthusiast willing to work on the OKC page and the Spatz page, in exchange for access to a large amount of data (from the already closed belgian/french trials) that could significantly enrich the legal timeline, as well as many facts that are completely unknown to the public.
Unfortunately, adding content to Wikipedia when it is done under the name “OKCinfo”, our Wikipedia account — which allowed us to demonstrate that the main editor of the OKC page for 17 years was none other than the general secretary of the OKC sect — is far more strictly controlled than when it was the sect itself editing its own page and that of its guru.
In fact, it is very difficult to find people to collaborate with so that added content is not systematically classified as biased or lacking sources. This is all the more difficult because it is almost impossible to provide “proof” in the Wikipedia sense, since no media outlet follows this case over time. Whether it is Le Monde, Mediapart, or others, no one really cares about this case, either in France or in Belgium.
As a result, the existing articles are extremely thin, even though we have a large amount of documentation, including original sources coming directly from the sect.
How can you create properly sourced links on a case that interests almost no one, apart from a handful of journalists — two, in my opinion — who have actually worked seriously on this file?
Today, the OKC page almost presents the sect as being caught in a legal “turmoil” despite itself, and an entire part of the legal content has been removed or moved to the guru Spatz’s page, as if he were the only person implicated.
The OKC Wikipedia page does not at all reflect the complexity of the legal and technical reasons that led to the recognition of a form of “irresponsibility” or “influence” affecting the OKC leadership in various rulings, without in any way clearing them — far from it.
In reality, if the OKC leadership was not convicted, it is not for the reasons presented on the page. If they are “free” today, it is largely because they helped shape, over more than twenty years, the absence of meaningful legal outcomes: by taking advantage of investigative shortcomings, the silence of victims, and the expiration of reasonable time limits. In that sense, OKC, just like Spatz, has shaped the outcome of this case as much as — if not more than — the judges and prosecutors who have handled it over the past forty years.
But nobody cares.
-
Un jour, j’aimerais rencontrer un·e passionné·e de Wikipedia prêt·e à travailler sur la page OKC et la page Spatz, en échange d’un accès à un grand nombre de données (des procès belges-français aujourd’hui terminé) qui pourraient enrichir considérablement la chronologie juridique, ainsi que de nombreux faits totalement inconnus du public.
Malheureusement, ajouter du contenu sur Wikipedia lorsque cela est fait sous le nom « OKCinfo », notre compte Wikipedia — qui nous a permis de démontrer que l’éditeur principal de la page OKC pendant 17 ans n’était autre que le secrétaire général de la secte — est bien plus soumis à contrôle que lorsque c’était la secte elle-même qui éditait sa propre page ainsi que celle de son gourou.
En fait, il est très difficile de trouver des personnes avec qui collaborer afin que le contenu ajouté ne soit pas systématiquement qualifié de biaisé ou insuffisamment sourcé. Ce point est d’autant plus complexe qu’il est quasiment impossible d’apporter des « preuves » au sens de Wikipedia, dans la mesure où aucun média ne s’intéresse à cette affaire sur la durée. Que ce soit Le Monde, Médiapart ou d’autres, le sujet est largement ignoré, en France comme en Belgique.
Par conséquent, les articles existants sont très maigres, alors même que nous disposons de nombreuses archives, y compris des sources originales émanant directement de la secte.
Comment établir des liens correctement sourcés sur une affaire qui n’intéresse presque personne, en dehors de quelques journalistes — trois, à ma connaissance — qui ont réellement travaillé sur ce dossier ?
Aujourd’hui, la page OKC présente presque la secte comme prise dans une « tourmente » juridique malgré elle, et toute une partie des éléments juridiques a été supprimée ou déplacée vers la page du gourou Spatz, comme si il était l’unique personne mise en cause. (totalement faux)
La page Wikipedia OKC ne reflète absolument pas la complexité des raisons juridiques et techniques ayant conduit à la reconnaissance d’une forme d’« irresponsabilité » ou d’« emprise » concernant la direction d’OKC dans différents jugements, sans pour autant la blanchir — loin de là.
En réalité, si la direction d’OKC n’a pas été condamnée, ce n’est pas pour les raisons présentées sur la page. Si elle est aujourd’hui « libre », c’est en grande partie parce qu’elle a contribué, pendant plus de vingt ans, à l’absence de résultats juridiques probants : en tirant parti des lacunes de l’instruction, du silence des victimes, ainsi que des délais raisonnables dépassés. En ce sens, l’OKC, tout comme Spatz, a façonné l’issue de cette affaire autant — sinon plus — que les magistrats et procureurs qui s’y sont succédé pendant quarante ans.
Mais tout le monde s’en fout.
-
Test if self-mention to my own site URL’s are now properly skipped :
- filter-out my own syndicated posts from mentions
-
@HolosDiscover@discover.holos.social follow
-
If you see this post, please interact with it with a reply or like, I will then be able to retrieve your interaction to my blog/AP fedify instance and then I will test replying to your reply to demo threaded reply backfilled to my site You can also comment using IndieAuth/indieweb if your site support it !
-
This blog post (sadly on substack) is truly fascinating :
Two years after the campaign started, in August 2021, China’s Supreme People’s Court, along with the Ministry of Human Resources and Social Security, officially ruled “996” illegal. It was, as far as I know, the first time that a grassroots, developer-led campaign used open source organizing mechanisms to enforce not just intellectual property norms, but labor rights norms, and ultimately ended in a legal victory.
-
Funny how building an ActivityPub plugin for #indiekit fully based on Fedify, migrating my Mastodon account to my own server @rick@rmendes.net and building my own UI to consume AP content from the #Fediverse made me use even more than before.
This post is simultaneously a blog post, an #ActivityPub object in the inbox of my followers and a syndicated post to Bluesky.
Next in line? getting inspired by #Wafrn and turn this indiekit/AP instance into my own #Bluesky Pds.
-
Two Microsub reader updates this week:
Feed type indicators — each feed now shows its type (RSS, Atom, JSON Feed, h-feed) as a badge, and subscribing to a feed that already exists in another channel returns a clear error instead of silently creating a duplicate. URL normalization catches trailing slash and http/https variants.
Mark source as read — the mark-as-read button is now a split button. The main action marks a single item, but a dropdown caret reveals “Mark {source name} as read” — which bulk-marks all items from that feed in one click. Cards animate out smoothly. Handy when a noisy feed floods a channel and you want to clear it without losing items from other sources.
Both features work in the channel view and the unified timeline view. https://github.com/rmdes/indiekit-endpoint-microsub
-
L’open web a gagné la guerre des standards. Il est en train de perdre la guerre de l’attention.
peut-on encore faire marche arrière ?
individuellement oui, mais collectivement c’est déjà plus compliqué… comme le démontre la difficulté de sortir ses amis proches des réseaux privatisés.
-
Public statements by Israeli leaders, and reports of biblical rhetoric inside the U.S. military, show how this war is being wrapped in religious language. When states frame bombing campaigns through theology, prophecy, or sacred enemies, they move away from secular democratic accountability and toward a dangerous fusion of militarism, religion, and political power.
-
When U.S. and Israeli officials or commanders tie war to biblical enemies, divine plans, or sacred destiny, they reveal a political logic closer to religious nationalism than to secular democracy. That fusion of state violence and theology is a hallmark of authoritarian regimes, whatever flag they fly.
-
Just updated indiekit-deploy (indiekit docker/compose based deployment)
Changes Summary
- Plugin versions aligned (package.core.json + package.full.json)
Plugin Old New syndicator-bluesky 1.0.14 1.0.19 endpoint-syndicate beta.34 beta.36 endpoint-microsub 1.0.41 1.0.43 endpoint-homepage 1.0.19 1.0.22 endpoint-activitypub 2.2.0 2.8.0 endpoint-github 1.0.7 1.2.3 - indieauth.js patch added
- Copied from Cloudron — fixes redirect URI validation that rejected hyphens/dots in paths
- Added COPY line to docker/indiekit/Dockerfile
- routes.js patch synced
- Two-tier rate limiting (session 50/15min, API 1000/15min) instead of single 250/15min
- Added content negotiation routes for ActivityPub
- Eleventy submodule updated
- From f5f77cb to 48160a5 — 131+ commits of fixes including OG batch spawning, a11y audit, PageSpeed optimization, design system compliance
- –expose-gc added to watcher
- Enables post-build GC hook in eleventy.config.js and OG batch spawning GC
- Atomic release swap implemented
- Builds to /data/site/releases/TIMESTAMP/, atomically swaps symlink at /data/site/current
- All 3 Caddyfiles updated: root * /data/site → root * /data/site/current
- First-run migration handles existing flat /data/site volumes
- Keeps 2 releases for rollback
- Watcher heap increased to 2048 MB
- Was 1536 MB, now matches Cloudron’s production setting
- Needed for OG batch spawning during incremental rebuilds
github.com