HN user

stopachka

3,795 karma

https://stopa.io stepan [dot] p [google's email service]

If you think we'd get along, reach out : )

Posts288
Comments494
View on HN
openai.com 20d ago

Core dump epidemiology: fixing an 18-year-old bug

stopachka
3pts0
openai.com 21d ago

Core dump epidemiology: fixing an 18-year-old bug

stopachka
1pts0
www.baserates.dev 1mo ago

Show HN: Baserates.dev, memorize programmer napkin math

stopachka
2pts0
www.anthropic.com 1mo ago

Project Fetch: Phase Two

stopachka
73pts26
lacker.substack.com 1mo ago

Turing Conjugation

stopachka
3pts0
www.vibediary.dev 1mo ago

Vibe Diaries: Training Nanochat

stopachka
2pts0
www.youtube.com 1mo ago

The most complex model we understand [video]

stopachka
2pts0
www.dwarkesh.com 2mo ago

The math behind how LLMs are trained and served

stopachka
1pts0
www.instantdb.com 3mo ago

Instant 1.0, a backend for AI-coded apps

stopachka
215pts124
www.instantdb.com 5mo ago

Counter-Strike Bench: GPT 5.3 Codex vs. Claude Opus 4.6

stopachka
4pts0
www.vibediary.dev 6mo ago

What Is ChatGPT Doing?

stopachka
4pts0
www.instantdb.com 7mo ago

GPT 5.2 on the Counter-Strike Benchmark

stopachka
3pts0
qy.co 7mo ago

I miss the old Qasar, not the new Qasar

stopachka
3pts0
www.instantdb.com 7mo ago

Codex, Opus, Gemini try to build Counter Strike

stopachka
287pts132
www.instantdb.com 9mo ago

How count-min sketches work – frequencies, but without the actual data

stopachka
49pts7
www.vibediary.dev 9mo ago

Building a CMS without programming experience

stopachka
12pts1
clojure.org 9mo ago

Core.async and Virtual Threads

stopachka
29pts0
www.instantdb.com 9mo ago

Founding Firebase with James Tamplin [video]

stopachka
3pts0
www.manyminiapps.com 10mo ago

Show HN: One prompt generates an app with its own database

stopachka
82pts66
blog.sbensu.com 10mo ago

High Variance Management (2023)

stopachka
2pts0
stopa.io 10mo ago

iPhone Dumbphone

stopachka
4pts4
bipinsuresh.info 10mo ago

Resist – Open-Source extension that lets you control your Twitter Feed

stopachka
1pts0
danwang.co 11mo ago

Violence and the Sacred: College as an incubator of Girardian terror (2017)

stopachka
1pts0
www.instantdb.com 11mo ago

GPT 5 vs. Opus 4.1 for Vibe-Coded Apps

stopachka
29pts10
www.instantdb.com 1y ago

How and where will agents ship software?

stopachka
153pts75
abesorock.substack.com 1y ago

The Psychological Significance of Eiji Yoshikawa's Musashi

stopachka
3pts0
expo.dev 1y ago

What if useState was your back end?

stopachka
1pts1
zdimension.fr 1y ago

Everyone gets bidirectional BFS wrong (2024)

stopachka
8pts0
tonsky.me 1y ago

When You Get to Be Smart Writing a Macro

stopachka
5pts0
noorsiddiqui.com 1y ago

The Inner Ring – C.S Lewis [pdf]

stopachka
4pts0

Interesting idea! Question:

It is highly unlikely that an AI agent startup becomes wealthy by creating the best harness for a particular use case.

If it's not the harness, what do you think is the thing that will differentiate AI agent startups? Is it mainly data, or something else?

I don't quite understand, what would 100K buy you?

AFAIK you would get about ~5 concurrent users, with a max context window of ~128K tokens on the larger models.

This wouldn't be good enough for coding -- are you guys thinking of using it for something else?

The UUID doesn’t actually affect the response. Every GET request still generates unique credentials each time, no matter what the value is that passes to /provision/<uuid>

We added it to help the app builders that do a lot of caching get unique responses. Turns out even if you set no-store cache headers, some app builders cache the pages. We tested this idea with those app builders and saw that they did generate uuids each time.

Is this the kind of use case that is seen as valuable?

I think it could be. Consider an argument like this:

It's valuable to ask ChatGPT questions and receive text responses. Some of the responses are more valuable when they don't just return text, but some markup: bolding, adding visualizations etc. Why can't some responses be more valuable if they return little apps?

One place where I've wanted this myself are with using LLMs for long-running goals I have. For example, I do my blood work about once a year, and I use the results to make changes and track. For a long time I had a long chat thread with ChatGPT. Now I have a little app instead.

An extreme version of this starts to turn responses into more and more fully-fledged apps. I did an experiment recently with creating a personal finance app. I found customizing the app to my specific needs made it much more valuable to me then generic personal finance apps, which have much more effort put it, but aren't tailored to my needs [^1]

[^1]: more on this experiment here: https://x.com/stopachka/status/2040982623636607009

One place where a tool like GETadb can be helpful, is when you as a developer wanted to build a quick demonstration. For example one of co-founders Joe saw a tweet about how VCs were ranked. He pointed Instant to an agent, made a quick polling app, and got 600 votes [1].

We hope delightful experiences like that then prod hackers to dive deeper and use Instant for startups.

[1] https://x.com/JoeAverbukh/status/2028544576206860697

Good question. Two ways:

1. For the users table specifically, we have a default rule that says `"view": "auth.id == data.id"`. This way even if the the user (or AI) did not set access controls, user data is protected by default.

2. In the instructions file given to the agent (https://www.getadb.com/provision/new), we specifically mention permissions and how to push them. We found this prods the agent to push perms.

Here's my argument:

In practice many GET requests don't adhere to this spec. For example, when you load a page, your "view" generally changes lots of things on the backend. Those changes come back to you in ways too: for example, consider view counts on Youtube videos or X posts.

Two reasons this could make sense:

1. With this, agents can actually deploy a full backend with their credentials [^1].

2. If your agent ever wants to add auth, or real-time presence, or file uploads, or streams, they'll be able to do that too

[^1] Alas we don't offer static site hosting, so to push the website you would need to use something like a vercel cli.

This post seems to "throw doubt" on Bun, based on the OP's experience of Claude Code. But this seems unnecessary indirect. It's not like Bun is hidden software: it's open source and actively developed.

So the more direct question would be: How has Bun actually been since the acquisition?

From what I can tell they have been responding to users as fast as before, and improving the product as well as before.

Stop Flock 3 months ago

I am surprised how overwhelmingly negative the comments are here. I would have expected at least a few voices defending Flock.

I'll step in and add a voice. Ultimately, Flock is solving a real problem with crime. This is why police departments when them.

Stopping Flock doesn't address the need that got police departments to use them. If you want to "stop flock", you need to address that need better.

My choice of the word "logically separated", was meant to specifically answer the question the reader asked:

If someone else's account is compromised, how do I know I won't be?

If you have other questions, you can feel free to ask, and I'd be happy to answer in more detail.

Any example more complex in the backend?

The home page has some examples of complex startups that use Instant as their core infra:

https://www.instantdb.com/#:~:text=Startups%20love%20Instant

Are we supposed to expose all entities and relationships and rely on row level security?

Yes. This may feel foreign, but we think it's one the best ways to do permissions. We were originally inspired by Facebook's EntPrivacy. When you have permissions at the object layer, you can be more confident that _any_ query you write would be allowed.

Photon looks interesting! I am not too familiar with it, but from what I understand Photon and WebRTC are for communicating messages between clients. Those messages can be very fast, because they aren't blocked by writes to disk. Instant has two similar services, Presence & Streams. The primary sync engine is more for storing relational data.

Thank you.

Curious if you considered shipping the engine itself as a standalone infra piece.

We are thinking about supporting something like "Bring Your Own Postgres", which would allow folks to opt into just the sync engine piece.

Right now we focused on the integrated system, because we really wanted to optimize for a delightful developer experience on greenfield projects.

If by backend you mean functions, you are right, we don't support this just yet! We give you an Admin SDK, which you can run in frameworks like NextJS, or inside systems like CF workers. We are definitely thinking about bringing this as a first-class citizen.

Supabase

We are similar to supabase in the sense that we support a relational database. We're different in that with us, you get real-time queries, offline mode, and optimistic updates out of the box.

Pocketbase

I am not too familiar with Pocketbase.

I would say:

We both offer a real-time queries out of the box. I am not 100% sure, I but think Convex also set up a multi-tenant database; so they can offer a good number of free projects well.

The way I would differentiate Instant:

With Convex you write your queries as Javascript functions. This means you have to do joins for example imperatively. With Instant, you can write queries declaratively.

As of today Convex doesn't work offline, and you have to write optimistic updates manually. Instant can run offline and comes with optimistic updates out of the box.

Both Convex and Instant support files out of the box. But with Instant you can write CASCADE delete rules, and you also get other services, like presence and streams.

Thank you.

Is React the only first class citizen in this stack?

Each system gets the same functionality. We centralize the critical logic for the client SDK in "@instantdb/core". React, Svelte, Tanstack, React Native et al are wrappers around that core library.

The one place where it's lacking a bit is the docs. We have specific docs for each library, but a lot of other examples assume React.

We are improving this as we speak. For now, the assumption on React is quite light in the docs, so it's relatively straightforward to figure out what needs to happen for the library of your choice.