Recent submissions

Comment · 2 years ago
Not a free car because I paid them.

Funny enough their dashboard showed a payment so I just screenshot that for them to look up in their own db!

Comment · 2 years ago
Rivian lost my full payment for an R1S.
Comment · 2 years ago
Comment · 2 years ago
I've helped with this one. Happy to answer any questions also.
Comment · 3 years ago
We use :telemetry to collect usage data per tenant for Supabase Realtime.

We do this for rate limiting but it also makes it very easy for us to attach a listener (https://github.com/supabase/realtime/blob/main/lib/realtime/...) which ships these (per second) aggregates to BigQuery (via Logflare), which then the billing team can aggregate further to display and actually bill people with.

Comment · 3 years ago
Comment · 3 years ago
Yo :D This is what Supabase Realtime does!

https://github.com/supabase/realtime

Spin up a Supabase database and then subscribe to changes with WebSockets.

You can play with it here once you have a db: https://realtime.supabase.com/inspector/new

Comment · 3 years ago
Comment · 3 years ago
Comment · 3 years ago
> although ensuring that only a single client is writing to a database at any time is (mostly) left to the application

Sounds like trouble.

Comment · 3 years ago
Yeah as in zero ops needed. Maybe NoOps.
Comment · 3 years ago
I hadn't seen WalEx. Looks rad!!
Comment · 3 years ago
Comment · 3 years ago
Triggers can affect throughput quite a bit on busy tables.

And we didn't want people schemas polluted with triggers.

But also we use Erlang distribution and Phoenix.PubSub because with a global network clients connected to the same node in the same region will get normal Broadcast messages to each other faster. If we ran them through Postgres or Redis the added latency wouldn't work for a global thing.

Comment · 3 years ago
Accepting pull requests if anyone is interested :D

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton