I'm building a Postgres-native workflow engine using pgmq for queues and TypeScript worker. Workflows compile to definitions (SQL rows), letting Postgres orchestrate the DAG as state machines. The TypeScript DSL is type-safe with inferred inputs/outputs across dependencies with full autocomplete.
Declarative and functional in nature. Just a manifest wiring functions into a DAG and a Postgres SQL functions that manage the graph of state machines. Simple in principle and very opinionated.
Replaces 240 lines of manual pg_cron -> pgmq -> Supabase Edge Function boilerplate with 20 lines of explicit DAG definitions. Currently Supabase-only (leverages their primitives) but planning to make it agnostic for vanilla Postgres setups.
I recently tried to run Apex Legends on my Manjaro (i played this a lot few years ago on my Windows dualboot), but it is impossible to play it on Linux, as EA/Respawn is preventing the game from running on Linux due to Anti cheat systems having troubles with protecting the game.
I'm really curious what would be the appropriate solution for an anti cheat that runs on Linux in a way that a) does not compromise my OS/privacy/security b) protects the game from cheaters at the same time.
I think software transparency could help with this. Or at least remote attestation - you could run the game inside an encrypted VM (AMD SEV) and attest that it is run this way. This way, you're not running a kernel module on your host, and you can't cheat the game even if you just physically write or read to the memory.
that sounds like a reasonable compromise, it may even provide more control and protection over what they are able to achieve on Windows?
i remember their anti cheat was utter crap tbh, not like something that Riot implemented for Valorant (a kernel-level system that runs from boot-up with deep system access)
I don't think there is a good solution. The best for privacy and security would be server-side anti-cheat but imagine the tantrum EA would have when they'd have to spend some dollars themselves instead of installing a spyware into their clients' pc for free.
The same pattern is everywhere: addictive games, addictive food, addictive social-media content.
It is really sad to see how society is driven by the monetization strategies of large companies.
I have a close friend who buried his depression under a pile of games built around these temporal reward loops. He’s not working and still living with his parents at 40.
Thank you for sharing this - awareness of these patterns needs to be spread.
Worth mentioning that WAL is enabling and used by Supabase Realtime [0] and WalEx [1] which both are doing very similar thing - polling the WAL changes in order to emit them as Websocket events.
I never worked with WalEx but have experience with Supabase Realtime and it is a joy to work with and fits great into the Supa ecosystem. So many layers are disappearing when you rely more on Postgres!
Declarative and functional in nature. Just a manifest wiring functions into a DAG and a Postgres SQL functions that manage the graph of state machines. Simple in principle and very opinionated.
Replaces 240 lines of manual pg_cron -> pgmq -> Supabase Edge Function boilerplate with 20 lines of explicit DAG definitions. Currently Supabase-only (leverages their primitives) but planning to make it agnostic for vanilla Postgres setups.
Live demo / explanation here: https://demo.pgflow.dev
reply