Readit NewsIf I want something cleaner or a little more "presentation ready," I switch to d2 (https://d2lang.com/tour/sql-tables/#basics). It's got really simple syntax and does a great job laying out entity-relationship diagrams without much tweaking.
Haven't tried Kagi yet — not sure the difference is big enough to pay for.
Honestly, I'm still stuck using some Google stuff anyway, like Maps. I'd like to de-Google a bit more, but in practice it's hard.
I missed the first wave: mostly stuck to aggregators and blogs, but eventually set up a Feedly account. Like others here, I found maintaining a meaningful list takes real energy. It's easy to over-subscribe and end up with a second inbox.
Still, I think the effort is worth it. The best systems I've worked on always rewarded small, regular maintenance over trying to automate everything away. Feels like curating information works the same way.
I’ve been using Loki recently and really like the approach: it stores log data in object storage and supports on-the-fly processing and extraction. You can build alerts and dashboards off it without needing to pre-aggregate or force everything into a metrics pipeline.
The real friction in all of these systems is instrumentation. You still need to get that structured event data out of your app code in a consistent way, and that part is rarely seamless unless your runtime or framework does most of it for free. So while wide events are a clean unification model, the dev overhead to emit them with enough fidelity is still very real.