<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://antoniuk.org/</id><title>Juan Andrés Antoniuk</title><subtitle>A personal blog by Juan Andrés Antoniuk.</subtitle> <updated>2026-09-13T10:39:51-03:00</updated> <author> <name>Juan Andrés Antoniuk</name> <uri>https://antoniuk.org/</uri> </author><link rel="self" type="application/atom+xml" href="https://antoniuk.org/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://antoniuk.org/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Juan Andrés Antoniuk </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Where Payment Routing Ends and Orchestration Begins</title><link href="https://antoniuk.org/posts/edge-core-data-three-clocks/" rel="alternate" type="text/html" title="Where Payment Routing Ends and Orchestration Begins" /><published>2026-09-03T00:00:00-03:00</published> <updated>2026-09-03T18:55:34-03:00</updated> <id>https://antoniuk.org/posts/edge-core-data-three-clocks/</id> <content type="text/html" src="https://antoniuk.org/posts/edge-core-data-three-clocks/" /> <author> <name>andresantoniuk</name> </author> <category term="technology" /> <category term="opensource" /> <summary>Building fluxrig has meant spending a lot of time on a narrow question: what happens between the moment a byte arrives on a socket and the moment something durable decides what it means. Those are two different jobs, and they want opposite things from the software doing them. The first has to answer now and is free to forget. The second has to remember everything and can take its time. Most of...</summary> </entry> <entry><title>Routing ISO 8583 Without Pretending to Be a Payment Switch</title><link href="https://antoniuk.org/posts/fluxrig-payment-switch-iso8583/" rel="alternate" type="text/html" title="Routing ISO 8583 Without Pretending to Be a Payment Switch" /><published>2026-08-01T00:00:00-03:00</published> <updated>2026-08-01T16:58:21-03:00</updated> <id>https://antoniuk.org/posts/fluxrig-payment-switch-iso8583/</id> <content type="text/html" src="https://antoniuk.org/posts/fluxrig-payment-switch-iso8583/" /> <author> <name>andresantoniuk</name> </author> <category term="technology" /> <category term="opensource" /> <summary>fluxrig 0.7.0 is out, and the source is on GitHub, with the documentation here. It is the payment-switch release, and since that name promises far more than the release delivers, I would rather start by drawing the boundary than by listing features. What shipped The centrepiece is Conductor: a gear that routes each request across a tree of strategy nodes (failover, round_robin, least_loaded),...</summary> </entry> <entry><title>Never From Scratch: My Open-Source Initiation into Fintech</title><link href="https://antoniuk.org/posts/opensource-fintech-sero-fluxrig/" rel="alternate" type="text/html" title="Never From Scratch: My Open-Source Initiation into Fintech" /><published>2026-07-24T00:00:00-03:00</published> <updated>2026-07-24T00:00:00-03:00</updated> <id>https://antoniuk.org/posts/opensource-fintech-sero-fluxrig/</id> <content type="text/html" src="https://antoniuk.org/posts/opensource-fintech-sero-fluxrig/" /> <author> <name>andresantoniuk</name> </author> <category term="technology" /> <category term="opensource" /> <summary>In the space of a few days, two posts from people I deeply respect sent me back in time. Daniel Goldman shared something that took me to 2014, to a wall covered in sticky notes where we spent hours arguing about a product we could not yet name. Looking at that photo now, I can still spot notes about IoT and M2M on the wall, threads I would keep pulling for years. Then Alejandro Revilla wrote ab...</summary> </entry> <entry><title>The Chicken and the Egg: Automotive Telematics, Protocol Validation, and the origins of fluxrig</title><link href="https://antoniuk.org/posts/acp245-telematics-fluxrig/" rel="alternate" type="text/html" title="The Chicken and the Egg: Automotive Telematics, Protocol Validation, and the origins of fluxrig" /><published>2026-06-12T00:00:00-03:00</published> <updated>2026-06-13T11:23:29-03:00</updated> <id>https://antoniuk.org/posts/acp245-telematics-fluxrig/</id> <content type="text/html" src="https://antoniuk.org/posts/acp245-telematics-fluxrig/" /> <author> <name>andresantoniuk</name> </author> <category term="technology" /> <category term="opensource" /> <category term="history" /> <summary>Recently, I had the pleasure of speaking at a Tribu Latam event (you can read more about it here: ¿Quién controla al vigilante? Tecnología, privacidad y el desafío de los estados digitales). The discussion brought back a flood of memories from my days in automotive hardware, reminding me that while technology evolves, the fundamental challenges of sovereignty and protocol control remain exactly...</summary> </entry> <entry><title>The 25-Year Long Game: From 486CORE Kernel Drivers to fluxrig</title><link href="https://antoniuk.org/posts/open-source-journey-fluxrig/" rel="alternate" type="text/html" title="The 25-Year Long Game: From 486CORE Kernel Drivers to fluxrig" /><published>2026-04-26T00:00:00-03:00</published> <updated>2026-04-26T00:00:00-03:00</updated> <id>https://antoniuk.org/posts/open-source-journey-fluxrig/</id> <content type="text/html" src="https://antoniuk.org/posts/open-source-journey-fluxrig/" /> <author> <name>andresantoniuk</name> </author> <category term="technology" /> <category term="opensource" /> <summary>It’s been quite a ride. Yesterday, I finally hit “public” on the fluxrig repository. While it feels like a new beginning, this release is actually the culmination of a journey that started exactly 27 years ago, in a very different technical landscape. 1999: The 486CORE Spark In July 1999, CompuLab introduced what was then the world’s smallest embedded PC: the 486CORE. It was a marvel of mini...</summary> </entry> </feed>
