danappelxx

7 ms·

1.
by danappelxx 25d ago
How does the agent auth with 1pw? How do you give it access to only the credentials it needs, with an approval flow and revocation? Who renews the token? You’ll likely end up reinventing something pretty close to what MCP is building toward
2.
by danappelxx 6mo ago
There is natural incentive for engineers working on a project to keep Claude skills up to date. I cannot say the same for general documentation.
3.
by danappelxx 7mo ago
GitHub API is actually quite tricky here because there is a different between “comment” and “review” and “review comment” (paraphrasing, I don’t remember the details). So it’s not as simple as one API call that grabs the markdown. Of course
4.
by danappelxx 1y ago
If the DNS resolution call blocks the thread, then you need N worker threads to perform N DNS calls. Threads aren’t free, so this is suboptimal. OTOH some thread pools e.g. libdispatch on Apple operating systems will spawn new threads on de
5.
by danappelxx 1y ago
Mirrors my experience. IPv6 issues are frustratingly hard to triage and reproduce, lots of “works on my machine” etc.
6.
by danappelxx 2y ago
This is an interesting point. Hangs usually cost $ from user experience, with serverless they cost $ from compute. All the more reason to set strict deadlines on all API calls!
7.
by danappelxx 2y ago
Took the same class at UCI (with Prof Anton Burtsev). Best class I ever took.
8.
by danappelxx 2y ago
Yup, exactly. Phones change wifi networks, routers drop packets, load balancers get overloaded. Hard to fully eliminate tail latencies.
9.
by danappelxx 2y ago
Unless your database is in the browser, you are always going to be at mercy of network latencies talking to the backend.
10.
by danappelxx 2y ago
I think you always need loading states to account for slow network, or am I missing something?
11.
by danappelxx 3y ago
“Cabin Noise during Acceleration with Ludicrous Enabled” was by far the most interesting
12.
by danappelxx 3y ago
Generally stems from the philosophy that code is read more than written, and this helps readability.
13.
by danappelxx 3y ago
What do you use instead?
14.
by danappelxx 3y ago
Not that difficult, but it’s still a separate dependency (with python requirements). If the goal here is a Caddy competitor, then IMO it’s missing the mark in terms of “one stop shop”. What’s the killer feature?
15.
by danappelxx 3y ago
Ah, good to know!
16.
by danappelxx 3y ago
It’s becoming standard as a security measure. See: Kata containers, Firecracker VM
17.
by danappelxx 3y ago
I’ll assume the worst case: - lots of containers running on a single host - containers are each isolated in a VM (aka virtualized) - workloads are not homogenous and change often (your neighbor today may not be your neighbor tomorrow) I bel
18.
by danappelxx 3y ago
IMO if you’re concerned about performance and yet are deploying databases this way — mmap should not even be on the radar.
19.
by danappelxx 3y ago
Who is deploying databases in containers?
20.
by danappelxx 3y ago
Agreed, but if you’re asking for a solution that will generate a spec from your code, the more proven path is to generate code from a spec. Gives you more and costs less. In my opinion the problem is that there’s some APIs that are impossib
21.
by danappelxx 3y ago
I suspect OpenAPI advocates would argue you should start with the spec and use it to generate both the client and server. This is already a common pattern in other RPC definition languages such as gRPC. You _could_ write a server to match t
22.
by danappelxx 3y ago
does it add support for streams?
23.
by danappelxx 3y ago
Right! Which is why we use (public) short-lived JWTs and (private) long-lived refresh tokens. What’s missing?
24.
by danappelxx 3y ago
Interesting. You already don’t have to worry about revoking JWTs if they’re sufficiently short lived. This gives you the exact level of protection as a short-lived mTLS cert, because if that gets stolen the attacker can continue to establis
25.
by danappelxx 3y ago
How does this approach practically differ from using short-lived JWTs+TLS?
26.
by danappelxx 3y ago
This is incorrect, value types are not referenced counted in Swift. If a value type contains a reference type member (usually an anti pattern!), then that member’s reference count is indeed incremented when the value type is copied. But it
27.
by danappelxx 4y ago
There’s partial support which is under active development. https://github.com/apple/swift/tree/main/docs/CppInteroperab... https://forums.swift.org/t/swift-and-c-interoperabilit
28.
by danappelxx 4y ago
Unsurprisingly, this is out of touch. Juul has been dead among teenagers for years, basically immediately after the FDA banned flavors. Its now been replaced by, as far as I can tell, completely unregulated disposable e-cigarettes which hav
29.
by danappelxx 4y ago
To clarify: - I was talking about ACID guarantees across databases (ie across users) - I was talking about aggregations across databases (ie across users) Of course working inside one database works as you would expect it to. My point was t
30.
by danappelxx 4y ago
Hold on, doesn’t one-database-per-user totally absolve all ACID guarantees? You can’t do cross-database transactions (to my knowledge), which means you can end up with corrupted data during aggregations. What am I missing?

More ›