And also Kronikle https://www.kronikle.eu/en/ an app for local libraries. It creates public display interfaces that (I think) are good for showcasing their events.

The web spec is vast and endless, if you try to build something actually works for modern sites, it will be huge. If you want to keep it lightweight, it won't work for most sites.

Just use chrome-headless-shell or webkit. Don't reinvent the wheels.

It's based on the Server-Driven UI philosophy where the backend streams both code and UI into a frontend that just knows how to render what it's told. This is pretty cool because it makes it makes over-the-air updates possible.

It also follows the batteries-included philosophy of Rails. Has an ORM, background and cron jobs (all based on Postgres), Django-style migrations, JSX Emails and pretty great FFI that's built around a simple `"use native"` directive, in the React Server Component fashion).

Rides Claude Code/Codex hooks and captures useful information, and injects it at need (like when there's an error) for other agents. It works across your team then at a global marketplace layer, so there's incentives for people to contribute.

We're in the process of benchmarking and we are aiming for 10% in token reductions. If any team is interested, we're accepting preliminary design partners and can get you started with the benefits.

https://bloom.site

I wonder if anyone reads these? If you do, if you want to complain to me about observability, please shoot me an email at hello@telemetrymachine.com!

We have worked in the observability industry for a combined 15 years and we are trying to right the wrongs we have seen in the industry. It seems like the existing companies are more interested in extracting more and more money from giant customers than actually helping people run their software well.

I won't bury the lede: what we've built is OTel native, wide events native, and works well with agents. We are also, shamelessly, cheaper than everyone else. One of the reasons observability is struggling with adoption is because it's too damn expensive.

So that's what we're building at telemetrymachine.com: an observability product focused on helping you actually track your software (starting with OTel traces and logs). We are really inspired by Observability 2.0/wide events, which really just is an invitation to stuff as many attributes, with as much cardinality as you want, into your spans/logs.

One thing we are also doing differently is trying to be as lean as efficient as possible. We are just two people now, and we are going to be very careful about hiring anyone. Most importantly, what we need to do is avoid a giant salesforce as much as possible. I wrote about this in a blog post[1] but the reason observability is so expensive is actually the giant sales force these companies tend to have.

We also put a lot of work into actual infra efficiency – ie we run on bare metal, and wrote a state of the art[2] storage engine. All of this is to help get prices down while still building a sustainable business.

We are very keen to engage with observability users, so if you do, or do NOT, use observability in your services, please reach out and we'd love to hear your problems and thoughts!

[1] https://telemetrymachine.com/blog/observability-doesnt-have-... [2] https://telemetrymachine.com/blog/the-new-state-of-the-art-i...

https://sunred.app/

https://kaflow-search.whsoul-tools.com/

To enable fast and detailed searches, I adopted a "local indexing" approach that differs from existing Kafka tools.

I recommend giving this a try if you have found operating services with Kafka inconvenient.

All the travel apps out there are built for the instagram generation but dinosaurs like me still use TripIt for travel tracking and itinerary sharing. But its parsing hasn’t changed since Concur bought it 15 years (!) ago and I thought it would be nice to have LLMs read the cancellation minutiae for trips and put in a simple timeline for sharing.