janwilmake

I created a browser that lets you see the markdown variant of all pages you visit, and llms.txt becomes your navigation.

Hi, i just open sourced my alternative at https://github.com/janwilmake/forgithub.badge, which is backed by uithub.com. The advantage is that you don't need a github action to calculate and it still auto-updates daily; also, if you click, you go to uithub to further trim the context window which can be useful if the whole codebase doesn't fit or if you want higher quality outputs.

Hey HN! Super excited to launch this OSS project to support the llms.txt ecosystem.

Similar to how Context7AI works, but you use LLM reasoning on the overview of the entire docs, instead of vector search. Also, you get a dedicated MCP server for the websites you need it for most!

In the process of making this, I discovered more than half of llms.txt live today are not spec-compliant. with LLMTEXT we're fixing this with tools to validate and create better llms.txt's! Read more in the blogpost.

Would love feedback from the HN community on both the tools and the broader question of how we should be serving AI agents vs. humans on the web.

Hey Lennert, congrats on the launch! Still open to chat about uithub

really cool! the problem with new standards though is that it's hard to adopt. what's your plan to adoption? because nobody will understand it if it's not in terms of things they already use/understand.

curious if this can somehow slot into oauth too, or this is impossible? I've been thinking about oauth proxies that alter the oauth scopes into more fine-grained ones, working on this. maybe this is the key to adoption.

Sharing my context engineering process in detail!

Since every developer is independently building new strategies to do good context engineering, I'm super curious to hear other people's takes on how to do builds like this!

Really cool! I just love the simplicity of it: has no drawbacks compared to regular textarea, but has lots of benefits. you basically improved textarea, by a lot!

I also made a similar thing a while ago called contextarea.com, maybe, I should add overtype!

You know what's also faster to roughly get the amount of tokens? string.length/5

Email sent.

Hey HN,

Today I woke up with the idea of making an agent-friendly version of hacker news. The coolest would be to also make it able to login, but that didn't work out, since I got blocked.

However, I made an oauth provider for HN, and it works on my machine. Unfortunately the IP gets blocked in production, so this isn't gonna work out. Even with a residential proxy, I started to get Captcha protection.

I'd love to make a 'login with Hackernews' so third party apps can build cool stuff with it. The code's all there.

Can you whitelist me?

Cheers, Jan

Here's the prerelease of DORM 1@next. I needed cheap performant multi-tenant databases on cloudflare, and the experience on Durable Objects was very painful.

This is my attempt at solving that DX.

Now it's slowly becoming a OSS Turso Alternative, I think. What does it not have yet? Curious for your feedback.

I think especially at the start the modularity of a system is relatively expensive, but once you add more modules, it starts making sense. Gotta find a vertical where lots of variety in modules can create value.

Early release. Please see the repo for the X thread.

Hope you like it. I'm happy to answer any questions here or on X.

The web’s stuck serving one format for all—HTML for humans, but what about bots, APIs, or social previews? It’s a legacy mess.

Here’s the thing: one page should adapt—HTML for crawlers, JSON for APIs, Markdown for agents, and PNG for social. Same data, smartly served.

I built a Cloudflare Worker to ditch legacy bloat. Vanilla JS/HTML/CSS, no frameworks, just a shared layer for all clients. First principles.

Meet my User-Agent Router: a Worker that picks the right format (HTML, MD, JSON, YAML, PNG) via headers or paths. Simple, fast, flexible.

Read more in the repo, check the demo, and lmk what you think!

I strongly believe we need to use Open APIs for agents. OpenAPI is the perfect specification standard that would allow for an open world and an open internet for agents.

When OpenAI first came out with their first version of GPTs, it was all based on open APIs.

Now they are moving away from it more and more. This means they want to control the market because they don't want to base it on an open standard.

It's such a shame!