Viewing profile — chasers
chasers
HN member- Joined
- Wed, Aug 01, 2007, 5:01 PM UTC
- HN karma
- 159
- Public activity
- 82 items
- HN profile
- View on Hacker News ↗
About chasers
No profile information was provided.
Recent public activity
-
comment
Comment #39845965
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
Comment #39844323
Rivian lost my full payment for an R1S.
-
comment
Comment #39275580
btw recently cleaned up my wal cache busting code quite a bit if you're interested. https://github.com/Logflare/logflare/blob/main/lib/logflare/... Need to make a lib out of this!!…
-
comment
Comment #38626932
I've helped with this one. Happy to answer any questions also.
-
comment
Comment #38018258
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.c…
-
comment
Comment #38018074
We just had some orphaned database connections (our bug) to a tenant and were able to find and kill them because of Erlang's observability: https://gist.github.com/chasers/e4aa3362…
-
comment
Comment #37614583
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…
-
comment
Comment #37089949
supabase dev here... this was a very fun load test to run. happy to answer any questions. shoutout to José Valim and the Dashbit team for the help on Supavisor. elixir and erlang a…
-
comment
Comment #37067593
yes otel across all of Supabase in on our radar for sure. we just added ingest support for otel payloads to Logflare (docs coming soon) so when we have that you'll get them on the …
-
comment
Comment #36615011
> 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
Comment #36335206
Yeah as in zero ops needed. Maybe NoOps.
-
comment
Comment #36334267
I hadn't seen WalEx. Looks rad!!
-
comment
Comment #36334173
Phoenix.PubSub is basically a noop service. It really just works. If discovering nodes is difficult in your env, try using a listen/notify libcluster strategy: https://github.com/s…
-
comment
Comment #36334133
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 …
-
comment
Comment #36334030
Accepting pull requests if anyone is interested :D
-
comment
Comment #35571002
Happy Livebook user here! Congrats on all the new stuff this week. Really great work.
-
comment
Comment #35570649
Also fwiw, if this is self-hosted I'm sure you can export them from BigQuery in an acceptable format. And if this is Supabase hosted, you can reach out to support and we can do tha…
-
comment
Comment #35570586
I work on logs at Supabase. What format(s) would you need?
-
comment
Comment #35526665
For sure > https://github.com/supabase/supavisor/issues/69
-
comment
Comment #35525614
Appreciate the detailed feedback here. Frankly these are all things I've wanted to address. We've just had to prioritize other tasks. We're definitely going to keep iterating. Than…
-
comment
Comment #35524786
Wow man Quickwit looks amazing. Probably would have reached for it when I started Logflare if it was around. I have not seen anything open source that really separates compute and …
-
comment
Comment #35524674
Depends on your use case. If the volume of data you're looking at is not much, Sentry is more feature rich and refined. If you want to expose a logging interface to your customers …
-
comment
Comment #35524536
Yes! You can sign up for Logflare separately actually.
-
comment
Comment #35524513
> Can you point out ways in which Logflare uses it that makes it so (for ex, is it tiered-storage with a BQ front-end)? After 3 months BigQuery storage ends up being about half the…
-
comment
Comment #35524421
Curious how was it awful for you? Really have not regretted any part of using BigQuery.