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.

I can't find references now, but Gnome or Ubuntu had a phase where they were booting the desktop with under 128MB of RAM.

It would be great if LibreOffice had a spurt of speed-ups. Kind what the browser wars also competed fiercely about.

I love the idea that these can live forever in apt/rpm repositories.

This is a good reminder for myself to get some onion addresses for my sites and spread awareness of Tor.

TIL that Onion-Location is a header, only new about the <meta> element.

  <meta http-equiv="onion-location" content="http://<your-onion-service-address>.onion" />

The "http-equiv" in that meta tag means "equivalent HTTP header", FYI.

But it's not always followed. Most HTTP headers aren't interpreted when specified with http-equiv, and vide versa.