Mail server
Amnezia VPN
keibidrop daemon to access files on-demand
a bunch of 1 off micro tools (metadata remover via static html, gains tracker, etc.)
Working with remote large data sets as if they where local.
I made the project public on May, and now as September has arrived, you can work with post production videos anywhere in the world. You can run the daemon on your own NAS and access the data on-demand from your working machines.
The same applies to data acquisition in digital forensics flows.
Since last month hardened bidirectional edits such that people can work on video assets with Premier Pro, DaVinci, and such.
Got a pre-alpha release, where we managed to split congestion control over QUIC and bulk data transfers over TCP, and the lockless conflict resolution :D
Why did your group use the AI, how would you answer the Conclusion questions?
As an anectdote: I like low-fi punk music because of the energy, and low skill for entry level. So when I started playing music, I went for this genre. I used it as a hobby over 10 years as it brought me joy, and enjoyed the process, without the grind for leveling up the skill.
It's also fun to do low effort things that are good enough. Much more fun than being l33t.
Hi ogig, funilly enough I was also running this boids experiment a few months ago. Managed to get around 8k at 60 fps on 1 thread on my cpu, using golang.
My goal for this experiment was to encode the optimal cache data structures into meta programming generators such that claude can write high level DSL and generate down to this level of simulations. I am curious if you had such an approach also.
That's very interesting, thanks for commenting. Not my approach, I have a multithreaded Rust kernel (SoA, spatial hash, bounded-kNN, rayon on some passes). The agents sit on top of several diffuse fields, an econ layer and combat logic, all of it needing bit-determinism for the netcode.
I do use some metaprogramming, but as safety rather than generation: a declarative macro derives the modifier struct, defaults, parsing and wire order from a single list, and feeds hash/save/resync so I can add mechanics at a high level without being able to desync the sim. Also a set of probes help me test for correctness and speed after a change.
So seems like I'm taking an iteration speed approach with safeguards, checking after the fact, while yours is optimizing beforehand by trying to encode optimal structs. That's fascinating, it will probably occupy my head for a good portion of the day, thanks again.
I went full meme, and stacked like 3 level of generators on top of eachother.
Level 1: A basic generator does the same stuff: Raw Structs to SoA + Wire Codecs + Bitfields to not waste space.
Level 2: Then on top of this one, I got a generator for relation between entities.
Level 3: And on top of this one one for "game" design and schema behavior.
And then all this runs on the simluator engine that handles Collision, Flow Fields, Events, Genetic Algorithms, Networking, etc.
The flow is something like this:
You ask claude to read a story, novel, w/e and extract relations, entities, etc.
Then it edits a Schema.go with the High Level DSL adnotations, like 10 lines per entity.
Then I run the Level 2 Generator: That creates the primitives and a high level API.
Then it combines the high level API rules in main.go and just compiles it to the final gamestate.
And runs benchmarks to see how many allocs/ops per entity are.
And one more fun thing, it encodes the gamestate on 1400 bytes, in order to fit on a UDP datagram such that it can support networking, quite fun. Once you get the primitives correct.
For all this + networking + disk i/o; works on 4 cores (threds) only. But the simulation in itself is on 1 core 1 thread. The networking offloaded to 1 core (1 thread), and disk i/o to a different core (thread), and the painting on screen (to a different core (thread))
Two weeks ago presented current state of KEIBIDROP at Pass The SALT 2026, and now I am planning the push for the next version 0.4.0.
KEIBIDROP: Makes remote files appear as local (it hides the network latency in order to let you open and edit a peers file without downloading it upfront or re-uploading it fully back).
For version 0.4.0 I am planning multi-user support, using UDP (QUIC) instead of TCP as the networking layer, optimization of live-edit regions of files, and to test it even more for data heavy workflows.
I am curious if I got it right, but the business of the company is providing exit nodes for AI bots/ strangers via peoples residential IP's? This is my impression from accessing the website. I was interested at first, but now I got a bit of ethical doubts about it.
Yep, everyone comes out happy here. It's a win-win-win. Unlike other proxy businesses, we always get our providers' consent before adding them to our pool.
I think OPs mantra is "Scrape. Automate. Scale."
It feels like people who consent to this "passive" income, do not understand what they consent to.
The business model seems grey towards black. "Signup to be part of 3rd party bot farms exit node, you get paid, all will be good. Nothing bad happens, you consent"
I think you’re steering this conversation in a direction that isn’t really meaningful. We have security mechanism in place that prevents misuse and fraud.
reply