Scuttlebutt is a peer-to-peer social network that is completely decentralized and independent of the standard…

Scuttlebutt is a peer-to-peer social network that is completely decentralized and independent of the standard internet. It is resilient at every level unlike federated services like Diapora and Mastodon.

It reminds me of the old FidoNet https://en.m.wikipedia.org/wiki/FidoNet systems I used to use many years ago, long before I had access to the internet. The difference is that this technology is designed to be secure.

I also remember chatting with a political activist years later who said he regretted the disappearance of those old BBS networks because they were much harder for repressive governments to censor and control. He used to hand out floppy disks to activists across the world to facilitate communication that was outside of the listening range of government eavesdroppers.

Scuttlebutt looks to me like a return to this older, more resilient and ultimately more liberating approach to social networking. This technology is part of the solution Andre Staltz was talking about in history TEDx talk that I posted yesterday.

https://plus.google.com/+JohnAHardy/posts/Qao9ED1REbX

These days you should be shipping two sets of bundles with your webapp.

These days you should be shipping two sets of bundles with your webapp. One which targets IE11 and the other that targets JavaScript.

http://main.mjs

http://fallback.js

Browsers that understand type=”module” ignore scripts with a nomodule attribute. This means you can serve a module-based payload to module-supporting browsers while providing a fallback to other browsers. The ability to make this distinction is amazing, if only for performance! Think about it: only modern browsers support modules. If a browser understands your module code, it also supports features that were around before modules, such as arrow functions or async-await. You don’t have to transpile those features in your module bundle anymore! You can serve smaller and largely untranspiled module-based payloads to modern browsers. Only legacy browsers get the nomodule payload.

The web always wins in the long run. On mobile (ahem, Apple) it’s going to take a little longer.

The web always wins in the long run. On mobile (ahem, Apple) it’s going to take a little longer.

Quoting from the article:

*I built a PWA and published it in 3 app stores. Here’s what I learned.*

Summary: Turning a web app into a Progressive Web App (PWA) and submitting it to 3 app stores requires about a month of work, a few hundred dollars, and lots of red tape.