brianwmunz

6 ms·

1.
by brianwmunz 3mo ago
"what the server can see to support rich queries" is the whole ballgame, right? Anything queryable is metadata that can leak or be subpoenaed... membership, access patterns, query frequency. For the activist/journalist threat
2.
by brianwmunz 3mo ago
Right, and it's a sliding scale. People think in terms of institutions acting the way they're supposed to. As we've seen those lines can get blurry and reasons can be created to track and suppress free speech.
3.
by brianwmunz 3mo ago
Whenever I would talk to people about the importance of privacy in data and online activity, people would always say something like "I don't care, I've got nothing to hide. I'm not some weird pervert." And yeah I&#x
4.
by brianwmunz 3mo ago
I have had it with these mother Fn keys on this mother Fn keyboard!!
5.
by brianwmunz 3mo ago
Maybe this is heretical in today's AI hype climate but...weirdly due to the rise of AI, then AI-slop polluting everything, a lot of old fundamentals are coming back. Clear, well-structured, descriptive content on a well-built page has
6.
by brianwmunz 3mo ago
The thread keeps smushing two separate questions into one. "Can these companies hit the revenue they need to justify the capex" and "are the tools actually useful day to day" are different arguments, and you can answer y
7.
by brianwmunz 4mo ago
"LLM evals" is maybe an overused term because it can mean a bunch of things. This article talks about LLM-as-a-judge where an LLM scores another system's outputs.
8.
by brianwmunz 5mo ago
Yeah people are just coming around to practicality.
9.
by brianwmunz 5mo ago
This is crazy. It narrated the failure in real time, naming the exact safety rules it was overriding. Then says "NEVER FUCKING GUESS!" Ha, we need to figure out better guardrails...
10.
by brianwmunz 5mo ago
yeah exactly the opacity is doing more damage than the limits themselves. anyone who's worked with AI knows there's a lot of limits you need to contend with. secret behavior changes are another level of badness.
11.
by brianwmunz 5mo ago
This is interesting. Reminds me of the W3C traceability work a few years back that I was briefly involved with... main focus was defining agreed upon vocab for interoperability across supply chains. Never thought of the same approach being
12.
by brianwmunz 5mo ago
Nein neins
13.
by brianwmunz 5mo ago
I use it for moving SSH keys, VPN configs, and .env files between my laptop and a work machine. Obviously don't want that sitting in dropbox, pasted into Slack, etc. Localsend on the same network, gone in two seconds no account and no
14.
by brianwmunz 5mo ago
Hey...interesting idea and definitely trying to solve a legit problem. With the human-in-the-loop aspect of it, is there any timeout or retry logic? Otherwise, the agent's sitting there blocked waiting on you.
15.
by brianwmunz 5mo ago
I feel like a core of this is that agents aren't exactly a replacement for a junior developer like some people say. A junior dev has its own biases, predispositions, history and understanding of the internal and external aspects of a
16.
by brianwmunz 5mo ago
Blaming "AI-accelerated tradecraft" for a breach that started with an OAuth token hijack from a compromised Google account is...interesting. The attacker didn't need AI they needed a stolen session and too many people with pr
17.
by brianwmunz 5mo ago
OpenAPI spec indexing is a good idea...semantic search is good for general API questions, but often sucks at specific questions about exact requirements for fields, etc. We've built a lot of connectors at my company and have had this p
18.
by brianwmunz 5mo ago
Tech pivoting from innovation to simply selling ads is often a last gasp. Couldn't figure out how to monetize so....ADS!
19.
by brianwmunz 5mo ago
Honestly I think you can tell pretty quickly if a company or person is approaching AI from the viewpoint of accelerating development and innovation or just looking to do the same amount of work with less people. The space has been flooded b
20.
by brianwmunz 5mo ago
Most of this thread is about protecting keys on a single developer's machine, but the problem gets way harder when you're managing credentials across customer tenants... env vars and secrets managers don't solve the orchestra
21.
by brianwmunz 5mo ago
PayPal benchmark is a smart way to launch this I think...showing real numbers on a recognizable API gives people something concrete to evaluate against. The 65% token reduction is probably the stat that'll matter most to teams watching
22.
by brianwmunz 6mo ago
A good idea is to build thin proxy layers that map "coarse" upstream tokens to more fine tuned internal permissions. The proxy holds the real API token and your internal services authenticate with scoped tokens that only allow spe
23.
by brianwmunz 6mo ago
I've seen similar with AWS where an API endpoint got flagged for "suspicious traffic patterns" just because it was serving webhooks at irregular intervals. The appeal process took weeks and nobody could explain what triggered
24.
by brianwmunz 6mo ago
Lol...Google's credential setup really is the worst part of building anything with their APIs. The actual API calls are usually fine, but getting there feels like a bureaucracy designed by people who never had to use it themselves.
25.
by brianwmunz 6mo ago
I know this is old but the OAuth advice aged well. Two years later it's still the part of every integration project that eats the most time relative to how simple it seems... Prefixed tokens especially is one of those things that seems
26.
by brianwmunz 6mo ago
The missing middleware layer is real... MCP handles the wire format but you still need something managing OAuth flows, token refresh, rate limiting, schema mapping per user etc... all the operational stuff. Authentication alone is brutal wh
27.
by brianwmunz 6mo ago
The token savings bit is interesting but seems incomplete without showing that tool call accuracy holds up. I like the CLI-as-interface idea...the model already knows how to use CLIs, and on-demand discovery is genuinely smarter than front
28.
by brianwmunz 6mo ago
Very cool..did you build this as one monolithic API with 48 endpoints, or separate services?
29.
by brianwmunz 7mo ago
The no-LLM-in-CRUD-path thing makes sense...I've seen teams hit real latency walls routing every memory operation through inference. What's your thinking around retrieval patterns? Most agent memory systems I've worked with e