Thanks for this.

They never learn.

lemmy is really really cool.

We should always have more alternatives to chose from - good to see so many players.

You bring a regulation - can you really enforce it?

so proton is now a movement.

Libreoffice is great !

But a true easy to use discord alternative is still not there.

I am making a GitHub repository https://github.com/dp1620/awesome-markdown-devtools for markdown tools - I will include revealjs.com along with sli.dev

Postman was great when it made APIs simple, but over time all the accounts, cloud sync, and extra features kind of slowed down the core workflow. And then a lot of clients just ended up copying that model instead of rethinking it.

On the optimistic side we are seeing some stuff that want to rethink this: tools like Voiden and Yaak with a few new approaches like  Git-native workflows, reusable request pieces, more composable setups basically making API work feel more like actual dev work again.

Everyone seems to hate this template.

all the comments are written by humans and no bots.

Curl is great. I use curl. Most developers use curl. But “you can call an API with curl” and “curl is enough as an API working environment” are two very different claims.

The problem is that real API work is almost never just one request typed into a terminal like some kind of beautifully minimalist Unix haiku. It usually turns into auth, environments, copied headers, reused payload fragments, request chains, documentation, testing, debugging, sharing examples with teammates, reviewing changes in Git, and trying not to break prod because you forgot to swap one token or one base URL.

At that point, people are not really using “just curl” anymore. They are using curl plus shell scripts, plus notes, plus env files, plus copied commands from Slack, plus random JSON files, plus tribal knowledge. Which is fine, until it becomes annoying, fragile, and weirdly hard to collaborate around.

Reddit really needs a great alternative. Lets see how Lemmy does in this regard.

April Fools?

That's a pretty good comparison.

The core idea of executable documentation next to your code is exactly what we were aiming for.

The difference is that Voiden is a dedicated, cross-platform app for the modern ecosystem, bringing the power of that file-centric workflow to everyone. We specifically go further by offering resuable composable blocks for requests (closer to functions than monolithic objects), a unified toolchain for design, testing, and documentation, and a clean, Git-native experience for all developers.

Voiden's core request model is based on composable blocks (for elements like headers and auth) that are reusable across requests for a DRY (Don't Repeat Yourself) approach, unlike Bruno which treats the request as a single, monolithic object that leads to copy-pasting and maintenance burden.

For documentation, Voiden provides living documentation by integrating runnable requests and human explanations side-by-side in the same Markdown file, ensuring it stays in sync with the API, while other tools' documentation is often separate.

From the monetisation side Voiden: Is an open-source community infrastructure project backed by a different main business, reducing the pressure to monetize aggressively. Bruno is as an open-source project that is under pressure to find a viable monetization strategy, which can lead to license shifts or paywalls.

You can read about the comparison here : https://voiden.md/comparison

Well having decent documentation is kind of rare.

This one is pretty great!

Codeberg.