I also feel like if you're going to invent a new internet from first principles, how are you going to not end up with the current one? (or a shitty version of it)

The answer might be an invite tree as the article suggests. They might be hoping for too much user quality from the invite tree, or at least hoping for a level of user quality that would only work at a small scale. Rather than "zany founders, reclusive poets, eccentric engineers of all kinds, high school teachers, homegrown philosophers, garage tinkerers, and beloved drug-addled futurist artists", imo to include a lot of people a simple invite tree would get you "not a literal bot". Trying to actually evaluate user quality gets you into moderation, federation, it is not easy. You could keep it small, but that's not an Internet replacement, that's a private forum, which as the author says they already have.

Imo a good start would be the much narrow problem of identifying your device as not a bot when browsing. Something like google fraud defense https://news.ycombinator.com/item?id=48039362 except instead of a google owning your identity, some sort of user tree where you can vouch anonymously for people you know, and ban users and users who added them for scraping.

"Diagnosing the ask" and "When they’re missing the philosophy" seem to me like traditional XY problem answers - the user doesn't know what the right question is, we need to step back to guide them.

"When the product needs to change" on the other hand is about figuring out what users want in order to add it to the product. Which takes a lot of figuring out, because it adds debt and you can add things the wrong way. This feels much less condescending to me than traditional XY where it's just tech support for a dumb user. Instead now figuring out questions from enough users helps direct new features.

"When the right path is hidden" I think the text for this one could do more to discuss helping direct the product as well, specifically in terms of documentation, if https://perfetto.dev/docs/getting-started/periodic-trace-sna... exists why is it hidden instead of where people find it when wanting to visualize a long trace.

If you read the title and just want to talk about XY eh fine, but the article's last sentence is the difference, "Both sides almost always walk away with more than they came in with."

Second, this may differ a bit from language to language, but maybe those booleans should not be a boolean: https://gleam.run/documentation/conventions-patterns-and-ant... for example isAdmin boolean could instead be a UserRole custom type, with variants Normal and Admin, which is easier to understand in the function call, and extendable with another Moderator (or whatever) variant

>I was the main contributor and maintainer to OpenEMR about ~20 years ago and then decided it was irredeemable and started over with ClearHealth/HealthCloud. Shockingly some of my code code lives on (from PHP 3). I am reluctant to say don't use it but if you do please don't expose it to anything public, which sadly happens most of the time. There are some real problems that exist in that code base from a security and HIPAA perspective.

Finding SQL injections etc is definitely valuable, but at the same time they did not hack Epic; the "100000 medical providers" number links to https://www.hhs.gov/sites/default/files/open-emr-sector-aler... which links open-emr.org/blog/openemr-is-proud-to-announce-seamless-support-for-telehealth/ which...404s. Per archive.org the source is something the CEO of now defunct lifemesh.ai said.

"medical record software" makes it sound super serious, but again OpenEMR should not be taken as seriously as for instance Epic.

I do think though if I were to delegate the API itself to AI and say something like the code doesn't matter, the high level thinking would suffer from lack of pain working through implementation details.

I don't think it's just the base rate of rounded corners though, these posts feel like the AI tends to spit out a bullet point list of features, like you'd see on an AI readme where each feature has a tangential emoji, then for a website puts them in a grid of rounded rects

AI might (might not, but often does!) also save you from doing original thinking in the domain, which in a show my side project is what people are interested in

(maybe what this post calls "Icon-topped feature card grid." ...that might be the official design pattern term)

Comments URL: https://news.ycombinator.com/item?id=47659644

Points: 3

# Comments: 1

So https://www.jerf.org/iri/post/2025/on_layers_and_boxes_and_l... is an interesting take: put links in your diagram, so it functions as a table of contents. This seems most useful for someone who needs to start working on a project.

Similarly https://haskellforall.com/2026/02/browse-code-by-meaning asks how to show what's in a repo, but maybe file tree is not best and a diagram with links as table of contents is the answer.

That said practically speaking, I'm not sure what tooling easily creates working links in a diagram that looks good in any context, for instance mermaid might render on github but not a text editor.

Of course for other purposes maybe just go crazy with the diagram. I once had a coworker draw this super detailed master diagram, maybe 50-100 things on it, which I was told impressed senior government officials (after my manager recolored all the red to avoid connoting errors). But for the purpose of orienting developers a table of contents with links sounds better.

author reply: not as obvious, but for one thing yes literally em dash, their post has 10 em dashes in 748 words, this comment has 2 em dashes in 115 words. Not that em dash = ai, but in the context of a post about AI it seems more likely. And finally, https://github.com/mksglu/claude-context-mode/blob/main/cont... the file the author linked in their own repo does not exist!

(https://github.com/mksglu/claude-context-mode/blob/main/src/... exists but they messed up the link?)

>this is [summary]

>not just x, it's y

>punchy ending, maybe question

Once you know it's AI it's very obvious they told it to use normal dashes instead of em dashes, type in lowercase, etc., but it's still weirdly formal and formulaic.

For example from https://news.ycombinator.com/threads?id=snowhale

"this is the underreported second-order risk. Micron, Samsung, SK Hynix all allocated HBM capacity based on hyperscaler capex projections. NAND fabs are similarly committed. a 57% reduction in projected OpenAI spend (.4T -> B) doesn't just affect NVIDIA orders -- it ripples into the memory suppliers who shifted capacity to HBM and away from commodity DRAM/NAND. if multiple hyperscalers revise down simultaneously you get a situation similar to the 2019 crypto ASIC overhang: companies tooled up for demand that evaporated. not predicting that, but the purchasing commitments question is real."

Doesn't ai;dr kind of contradict ai generated documentation? If I want to know what claude thinks about your code I can just ask it. Imo documentation is the least amenable thing to ai. As the article itself says, I want to read some intention and see how you shape whatever you're documenting.

(AI adding tests seems like a good use, not sure what's meant by scaffolding)