1.Open source + polished README
2.Listed on directories like create.io
3.Added to awesome-rust
4.Did a Show HN post
That's all I've done so far. 60 stars currently.
13 karma · joined July 23, 2026
1.Open source + polished README
2.Listed on directories like create.io
3.Added to awesome-rust
4.Did a Show HN post
That's all I've done so far. 60 stars currently.
The full project is here: https://github.com/IndexFlowing/IndexFlow-core
I already had access to web-based AI with much more usage, so I started wondering: why not let the web AI do the thinking, and let the coding agent do the actual work?
MCP made this possible.
AgentBridge connects the two: the Brain can inspect the local project and create a plan, while the local coding agent executes the changes and runs tests.
It started as a way to make better use of my AI subscriptions, but I think the Brain/Executor separation could be useful beyond that.
Would love to hear what you think.
I built IndexFlow-core, an open-source search engine indexing infrastructure written in Rust.
The project started from problems I encountered while building content-heavy websites. I found that making a website available online does not mean search engines can reliably discover and understand it.
IndexFlow focuses on the technical layer between websites and search engines:
- Sitemap management
- SEO quality gates
- URL discovery
- Indexing workflows
- Multi-site scheduling
- Quota-aware request handling
The goal is to provide a self-hostable infrastructure layer for developers who care about search engine visibility.
Website:
Feedback welcome.
As for the game itself, I feel the process is a bit too complicated. In today's world, not many people are willing to go through someone else's wedding story, especially in the form of a game.
Anyway, congratulations on the wedding!
PostgreSQL is a great database — I use it too, and I'd recommend it.
I wouldn't suggest Java though — it's too resource-heavy. If you have really good server resources, maybe consider it. But I'd recommend Rust instead. Don't be afraid — Claude will write most of the code for you. You just need to know how to debug.
As for Redis, you probably don't need it at the early stage. Only worry about it when your app has a lot of users — by then you'll naturally figure out how to use it.
One more thing: write detailed API documentation first. Everything should revolve around the docs. Don't rush into writing code. Trust me, documentation matters more than code.
Good luck, and go for it!