Good thing about trmnl is you can run the entire backend if the company disappears.

I made fun of the 'America First' campaign slogan and referred to it as 'America Only'.

Then you can quickly use this idea on people who put themselves in front of others. And the reality is it's not about being first, rather it's only about them, not what comes after them.

Coming from Slack for a number of years, there is an initial shock of missing out of the 'slack way of things'.

The killer feature is everything is a stream/thread. I argue that is a better UX over Slack, but it takes some getting used it.

As mentioned, Slack is way more polished.

> The killer feature is everything is a stream/thread. I argue that is a better UX over Slack, but it takes some getting used

I personally can't stand it. _However_ I just learned today that it can actually be disabled, which I would do if I was deploying a zulip instance for my team. We are all very wired towards the crackhead energy of just.. a chronological chat and a competent search.

You can just not specify a topic and write your messages in "general chat", nothing stops you from doing this.

we want topics allowed in certain channels only (ie #announcements) so that's probably what we'll use this feature for which certainly was not there when we tested maybe a year ago or so

The nice general chat UI and per-channel permissions for it were new in Zulip 11.0 last year: https://blog.zulip.com/2025/08/13/zulip-11-0-released/. So probably you tested not long before this got built.

That's new.

True, though even before this we just made a chatting topic with the name "general", that worked just fine while still letting people make other threads for long discussions.

> Coming from Slack for a number of years, there is an initial shock of missing out of the 'slack way of things' [...] takes some getting used it.

I have a theory for why some people love Slack and others love Zulip (Completers -vs- cultivators) which I shared in a sibling thread.

https://news.ycombinator.com/item?id=46960569

Curious to hear what you think.

It's getting movement in tough political environments like Uganda: https://www.archyde.com/bitchat-surges-to-1-in-uganda-amid-p...

And natural disasters like in Jamaica https://www.gadgets360.com/cryptocurrency/news/bitchat-becom...

> Its soaring popularity highlights how decentralised technology can offer a vital communication lifeline during natural disasters. Its soaring popularity demonstrates how decentralised tools can provide a critical communication lifeline when natural disasters knock out traditional infrastructure.

seems like the second article is written by AI

You might be referring to Bitchat.

I was a big fan, the original version was called forecast.io.

It was a rare example at the time when it was _the_ webapp better than any existing 'native' apps.

As a fan of webapps, https://yr.no is a good no-frills weather webapp.

Whats the cycle time here? This work flow makes sense to me.

It’s largely asynchronous for me. I'll trigger the generation and come back to the PR whenever I'm free.

I'd say the cycle time largely depends on the complexity of the tools you are building. I've built a movie shelf hooking up with trakt.tv under 30 minutes and a mermaidJS diagram editor spanning multiple sessions and couple of days.

This is a hard truth. I looked at my own Show HN post history, some are definitely in the graveyard.

Savage, but accurate.

But I argue for these projects to have a long tail, they need revenue.

A few have tried by selling hardware, but it never lands mainstream enough.

Started on this with OpenELEC. Nowadays LibreELEC.

Just feels the best that it's not a commercial product, rather a project built by cool people.