In 2025, Interledger brought Open Payments to Mexico 🇲🇽
4 cities. 4 universities. 500+ students building real solutions.
47 teams at the Mexico City hackathon explored remittances, device-less payments, and more.
🌍 Watch highlights:
https://www.youtube.com/playlist?list=PLDHju0onYcAJTqclf030A87CiX-8KxapZ
In 2025 PRICELESS SA asked us to make it easier for their academic team, & the people who rely on their research, to find what they’re looking for.
So we did what we do best.
Curious how it turned out?
https://juizi.com/news/priceless-results-of-a-search
🌟 Breaking AI News! 🚀 Discover the latest advancements revolutionizing our world 🌍 Stay ahead with insights into cutting-edge tech, innovation, and AI dreams coming true 🤖✨ #AINews #TechTrends #InnovationNation #FutureForward #TechTuesday #AIRevolution #DigitalTransformation
Spent today wrestling with the game's growing memory. Every village, item, and little change needs to stay connected, and missing one link can make something weird break somewhere else. Working on a cleaner way to keep all that info organized so the world can keep growing without turning fragile. It's a quiet kind of progress, but it matters.
☕️ Scopri le migliori macchine da caffè a capsule di marzo 2026 - Un gusto eccezionale ad un semplice click! #CaffeineFix #TechTuesday
🔗 https://www.tomshw.it/offerte/macchine-per-caffe-capsule-cialde
The baseline loop is working, go out gather bring items back. Next focus is how items spawn per tile. I'm building per-tile drop tables with layered probabilities and an editor to visualize drops over the TileMap so sticks spawn near forest not plains. Goal: keep it scalable as new items are added. Any thoughts? Alternatively I could mark the item drops in the editor with a polyshape.
Quick build and deploy update: set up a multistep pipeline to update Nakama and the Godot client with basic error correction. After a push I can test server code in the editor in about 30 seconds as Nakama restarts and reports status. Full deploy without a map upload is 1 to 2 minutes, so players do not notice restarts. I will add in game notifications once a second server stack is updated weekly.
Made a usable login screen today: email/password fields, inline error display, and account name/display name on the side. Not a game yet, but after registration and localization work we can polish UX. Tinkering with localization keys and fallback text will be probaply a small headache. Preview: login UI gif. What auth details should I prioritize next?
Interledger Foundation
Juizi
Livio Acerbo
Tysk Games
Tom's Hardware Italia
SquaredTech
SpringGnoll