This post makes the case that attaching a crypto currency to a protocol would ensure the long term funding of development and maintenance of the protocol.

OK. But IMO it seems like a distraction too, and rife with potential mistakes. Mistakes that could sink your protocol. Is it worth it? Maybe there are other ways?

Anyways, everything I read about the governance of crypto tells me it's a total ****-show so it's probably better to find a better solution.

- it's the first time I hear of an application for Bitcoin technology that is actually interesting to me.
- article was a bit "hand-wavy" and unconvincing wrt users controlling their data but putting an encrypted blob in the cloud.
- I am quite concerned about the filter bubble problem, but I am afraid it's a societal problem, and needs resolution at that level
- I agree we should put more effort in protocols than in applications. There is lots that can be done here.

Just read this piece on protocols:

.. And the hn discussion and followed some links.

Some takeaways:
- if you great an open protocol, don't expect it to survive if users don't know there using the protocol. Ex: email versus jabber/XMPP.
- protocols get run over by platform due to lack of funds. What causes people to invest in a protocol? And if they don't, h ow do you keep up with funded platforms?


On a sales call, a prospect asked me explain security precautions I take with our servers. I struggled for a moment for a response that would make sense to someone totally unfamiliar with devops and then mumbled something about strong passwords. It worked. She signed up. 🤷‍♂️

Are there any good reasons for servers that support HTTPS to allow HTTP connections without TLS? My site currently forces HTTPS. Intuitively that seems like the right choice to me. Is there a reason I shouldn't do this?

WhatsApp Shows "From Facebook" in the splash screen now. I hope they add ads soon and people stop using the app.

Half a century of dither and denial – a climate crisis timeline 

Discord post-mortem from a cloud engineer on the outside 

Oh the front was only big in the compose box. 😒

Hypothesis[1] is a good idea but it is a centralized service (as far as I can tell).

Haven't looked in depth but dokieli looks to be a worthy replacement:

"Decentralised Authoring, Annotations and Notifications for a Read-Write Web with dokieli"

(Wow that's a big font)


I think the three R's (Reduce, Reuse, Recycle) are missing a critical fourth R. (Reduce, Reuse, Repair, Recycle)

complaining, pixelfed 


Times I've invoked Google Chrome's "Pull to Refresh" page:


Times I've done so intentionally:


Times I've lost state invoking Google Chrome's "Pull to Refresh Page":


Times I've wished Firefox's Android performance was sufficient to be able to ditch Chrome:


Times I've wished for a viable tablet full-Linux Android alternative:


@alcinnz I mean, Usenet had MMF:

My general view is:

- Focus on *behaviour* rather than *features*

- Recognise that *complexity* enables both more bad behaviour, and can mask it.

- Reputations matter. Rather than identify *content*, track the *creators*, both good and bad.

Effective trust networks tend to be *small*. A few tens, *possibly* hundreds, of actors. Trust scales poorly.

pinebook pro day one:
it's hosed. we tried to upgrade it to debian 10, and this immediately resulted in a horrific dependency knot that not even all our strength could rip out. tomorrow, we will try to reflash it.

nice hardware, though.

Is it just me or is Safari in iOS 13 _extremely_ buggy? Especially if you have a service worker?

Show more

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!