Ogumon

@GergelyOrosz Twitch has the exact same illegal stream problem but they chose the smart path: they give rights holders proper DMCA-style tools to takedown streams instantly without breaking the internet

It's hard to believe that the "~80%+ of the internet is blocked in Spain during football games" claim is true - but it is!! And has been for years. The government is sabotaging their complete digital economy... for La Liga, a private football org worth €5B. Pure madness

@orcachillin @adamrunner1 The fans and heat become brutal once loaded. From experience, the APC Netshelter CX 24U soundproof enclosure is far better suited for home than an open rack.

@adamrunner1 it was kind of a pain! it was worth it in the end though

someones the new proud owner of a 42u server rack :3 and yes we dont have a car so we brought it home on the train

@_newtonjob @andreapozza_ High-performance setups encrypt the entire session context (user, plan, limits) into the cookie so the proxy can enforce everything at line speed. No backend lookup per request. RTFM on cookie-based offloading.

@Ogumons @andreapozza_ So you still need the rate limiting feature of Laravel. And I still don’t see how it knows the user on the next request. Might be missing something, but HTTP requests are stateless, and only the application can determine the user.

Very underrated rate-limiting feature in Laravel. You can very easily apply dynamic rate limiting on a route based on the value of a database column on your users table🤌

@tomik99 This is mostly a myth in Poland too. Paper intake forms are rare, clinics use the national P1 system for medical documentation. Doctors rely on copy-paste templates and adjust them to the patient. The real admin burden comes from clunky systems, not typing from paper

Startup Idea. Healthcare: Intake to Documentation There will be 100 successful startups built on AI-first healthcare workflows. Clinics still collect data on paper forms and then retype it into EMRs. Doctors spend more time on computer than with patients. Build a Healthcare Intake Agent that: - digitizes patient intake - structures symptoms, history, and meds - pre-fills EMR entries - drafts visit notes for review Vertical AI in healthcare is already doing real-time documentation. If you’re a dev shop in medtech, this is your chance to create regulated-ready IP on @OpenMercato.

@_newtonjob @andreapozza_ Did you even bother looking at the spatie varnish code? Laravel does the DB lookup once, sets a damn header like X-Rate-Bucket: premium. Then HAProxy ACLs shove the user into the right stick-table. No PHP on the hot path. Read the code instead of wasting time.

@Ogumons @andreapozza_ Doesn’t quite answer my previous question though.

@andreapozza_ @_newtonjob It works almost exactly like spatie/laravel-varnish does for caching

@_newtonjob @Ogumons I'm curious to know too

@_newtonjob @grok explain in simple terms (for @_newtonjob) how @Ogumons solution works when using HAProxy as the reverse proxy? this solution is similar to spatie/laravel-varnish

@Ogumons No. I don’t see how can possibly work. How does the proxy identify the user? How does know which routes must be ratelimited if you don’t implement it at Laravel. How does it even know whether or not a request should be counted against the rate limit? This isn’t generic stuff

@_newtonjob Proxy needs only one request to reach Laravel to read the plan & set the limit. After that, everything should be handled at the proxy level (millions req/sec), not inside PHP which handles only hundreds. This is a reason for not using this rate-limiting feature in Laravel.

@Ogumons The reverse proxy cannot determine what the rate limits should be upfront. The request has to reach Laravel first, then the middleware decides if the request should be rate limited, and includes the necessary headers, before your reverse proxy can then block subsequent requests.

@penberg How do you ensure full SQLite compatibility, without access to the closed-source SQLite test suite?

What are Turso, Turso Cloud, and libSQL? I get this question a lot, and AI agents seem confused about it, too. tl;dr: Turso is a new SQLite-compatible database, rewritten from scratch in Rust, currently in beta. libSQL is our open-source fork of SQLite, which powers Turso Cloud today. Turso Cloud is our managed database service, and we're actively working towards adding Turso to it. Still confused? That's fair. The names evolved as the product did. Here's the full story in chronological order. Back in October 2022, we announced a fork of SQLite called libSQL. At the time, we were building an edge-replicated database based on SQLite for our internal use. However, we faced a major problem that there was no way to upstream the core enabling technology, WAL virtualization. We decided to fork SQLite and make it open to everyone's contributions. With the fork out of the way, we kept building what would become Turso Cloud. One of the most memorable moments was when ThePrimeagen tested our database on his stream sometime in February 2023, while we were still in private beta. The whole team was watching the stream and monitoring our systems, hoping everything would work out fine. In April 2023, we launched a public beta. With our own fork of SQLite, we spent a lot of time early on trying to address one of its biggest limitations: the single-writer transaction model, which limits scalability and isn't the greatest DX. Me, @sarna_dev, and @iavins built a Hekaton-based MVCC implementation and a prototype of libSQL supporting BEGIN CONCURRENT. However, the integration wasn't great, and there was a lot to do with Turso Cloud, so we shifted priorities there. During that same time, I began exploring rewriting SQLite. I initially used Zig, thinking I would reuse large parts of the SQLite front-end, for example. However, I also wanted to make the database core fully asynchronous with io_uring support, and it turned out to be very hard to reuse any of the SQLite code for such a fork. With some skill issues during comptime (as ThePrimeagen and Jarred Sumner once framed it), I ended up ditching Zig and, in late August 2024, switched to Rust. I called the project Limbo at the time, but later it was renamed Turso. The whole thing was more of a side quest than anything at that point, mostly exploration. In early 2024, we had a bunch of people asking for vector support in libSQL. @SivukhinN added support for approximate vector search, similar to pgvector, but we had to compromise on the DX because the changes to libSQL would have been very intrusive. Around this time, we realized that forking SQLite would only take us so far, mostly because the main test suite SQLite uses is fully proprietary, and we had not been able to obtain access to it. After some back-and-forth, we ended up making my SQLite rewrite side quest public. Surprisingly enough, early people like @Peristocles1, @jussisaur, and @PThorpe92 showed up and started contributing to the project. As we saw more uptake, we made it an official company project in December 2024, renaming it to Turso. (As a side note, we did end up rewriting the libSQL server components using TigerBeetle-style DST architecture with S3-based diskless architecture in August 2024 and migrating from Fly to AWS. But that part fortunately added very little confusion to users, as it's mostly a Turso Cloud internal detail.) Today, Turso is in beta with early customers working toward production deployments. The libSQL fork has been an incredible success with 800k weekly downloads for the JavaScript SDK and running production workloads at scale. We're actively maintaining libSQL, but the future is Turso. Built from scratch with no proprietary test suite in the way, Turso supports features like concurrent writes that a fork of SQLite never could, and we're working on bringing it to Turso Cloud.

@paulg @sha3loul @ConwayAnderson Just commit to one brand that gets you right. Buy all your pieces from them. You always look good, zero mixing, zero thinking. Just like Feynman with dessert: always chose chocolate.

@sha3loul @ConwayAnderson Because you can't simultaneously optimize two unrelated things.

tech people: taste has never been more important the taste:

@KamilStanuch @cursor_ai Ogarnięty notariusz nawet komputera nie włącza. Szablony Word/Google Docs od dekad dają 100% powtarzalny, zero kosztowy, bezbłędny akt. Asystent żywy człowiek wkleja dane do szablonu i drukuje Notariusz czyta wydruk, sprawdza tylko dokumenty tożsamości i skończone 🤡

Jako notariusz w 70% przypadków nie potrzebujesz dedykowanego legal techu. Do administracyjnej pracy wystarczy @cursor_ai albo dowolne IDE z LLMem. Przykład poniżej: - Wzór umowy sprzedaży mieszkania - Plik z danymi stron, nieruchomości, KW, ceną, szczegółami (te dane można zbierać w formularzu przed rozpoczęciem czynności) - Jeden prompt “na bazie wzoru X przygotuj umowę i użyj danych z Y.txt” Do tego w Cursor rules są zdefiniowane zasady formatowania, jasna instrukcja by nie zmieniał struktury aktu etc. Tak, to narzędzie do „czarnej roboty” administracyjnej, a nie do wydawania opinii prawnych. Nie, tu nie ma halucynacji, bo to powtarzalne case’y według wzoru sprzedaż, darowizna, służebność, najem okazjonalny. Bardziej zaawansowane “znajdź i zamień”. Tak, standardowo dane przetwarza LLM w chmurze, ale możesz podpiąć lokalny model (np. Bielik) Nie, to nie „koniec zawodu notariusza”. Notariusz ma myśleć, poza tym i tak sprawdza ten tekst. Tak, to wygląda jak środowisko dla programistów. Ale to tylko edytor tekstu na sterydach, który rozumie kontekst całego projektu (sprawy), a nie tylko jednego pliku. PS. Przygotuję jeszcze kilka przykładów.

@OskarStark Bad programmers brag about the time they rm -rf'd production and survived. If your seniority is measured in near-death deploy stories, your org is broken. Real seniority builds the guardrails: staged rollouts, ACLs, and monitoring that screams before rm hits prod.

Controversial take: "Senior developer" doesn't mean 10 years of experience. It means you've mass-deleted production data at least once, mass-emailed customers by accident, and mass-deployed on Friday. The "senior" is trauma, not tenure. 😅

@IlirAliu_ @loki_robotics Easy test drive in a clean restroom. But drop this thing into the worst Indian public free toilet I’ve ever seen poo smeared on walls, floor like a swamp, smell that hits you before you even enter Those aren’t dirty they’re biohazard-level disgusting

Everyone talks about humanoids. Meanwhile, @loki_robotics:

@matt_elevenlabs 11B

We just raised $500M at an 11B valuation 🎉 To celebrate, we’re giving away 1,000 free credits so you can test our platform. For the next 6 hours, comment “11B” below and we’ll DM you the credits (must follow) 👇

@gutomartino @amritwt how are you actually getting real value out of Perplexity Pro? I've had it for a full year and it's been mostly garbage for me. Constant low-quality SEO spam as sources, barely any high-authority content (academic, official reports, reputable outlets), answers hallucinated

@amritwt What kind of research did you do? I am getting more value and better outcomes from Perplexity these days. I pay $20 a month for each.

I got a $20 Claude subscription to see what its like and did just one deep research to find stock arbitrages My usage is 40% finished lol is this normal

@umikathryn Sanding is the way to fix that yellow heat stain, but it risks uneven texture. Recoating takes real skill. Call the pro who made the desk, or accept the mark.

Asking all artists/physical builders/DIY-ers: Does anyone know how to remove a superficial heat stain (yellow) from cured white resin? I’ve tried hydrogen peroxide+baking soda, and distilled white vinegar. My desk is like 300lbs so I can’t just casually take it somewhere.

@tomik99 youtube.com/watch?v=RW2IbJ… Amisze mają na to patent, który u nich świetnie działa od dekad, ale poza ich światem budki telefoniczne jako sposób na „wymuszenie” skupienia się przy stole się nie przyjął

Telefon na stole = rozmowa na pół gwizdka. Imho to nie tylko problem kulturowy. To problem do rozwiązania produktowo. Myślę o czymś w stylu: 🪓 Murdered Smartphone in Social Context Chętnie: – zainwestuję – albo zbuduję coś małego z kimś, kto czuje ten problem tak samo. Też widzisz, jak bardzo smartfony psują rozmowy?

@tomik99 Widzę że chcą wykorzystać trudną sytuacje na rynku i urządzają konkurs dla kandydatów na product managera AI. Dostaną jakieś prototypy agenta i zanotują najlepsze pomysły do wdrożenia za darmo. Kiedyś to robiło się hackathon ale to kosztuje..

Wydaje się to super pracą dla ambitnej osoby. Zerknijcie.

@PoeHaH @brendt_gd Exercise just show how retarded the patterns are. One Statement: SELECT … INTO `visits_per_hour` ... ON DUPLICATE KEY UPDATE... and the DB keeps its own damn data locality instead of playing fetch with PHP.

@Ogumons @brendt_gd Of course there are faster things out there. The point of the exercise is that you can make PHP a lot faster than you initially think. The speed increase is massive.

Remember how yesterday I optimized my #php replay command to process 14k events per second instead of 30? Yeah well… someone made a suggestion which bumped that number to 50k events per second. stitcher.io/blog/processin…