Some of you may already have seen . It is a re-design of Low-Tech Magazine that I did together with Marie Otsuka and Lauren Campbell. After a few months of working on it I'm happy its out in public, survived the attention and creating discussions!

and its double plus good that it was on the fediverse that the news broke :)

Show thread
@rra Don't know if you seen it, but there has been some discussion about it there [1]. PM me if you need an invite ;)


@Ninjatrappeur its hard to keep up with these discussion threads but there are some interesting comments there! I wouldn't mind an invite. By the way, in case you are active in the discussion at lobsters, I've made a lengthy response over on grid powered lowtech magazine adressing most questions :

@rra Totally agree with you regarding redundancy. It does not really make sense in a context where energy becomes a scarce resource.

To me, it seems HTTP is a pretty terrible protocol if we assume we can't provide a 100% uptime. I've been trying out some post-internet compatible communication protocols lately.

I think we should design such things to still be able to communicate in a global scale, even if internet becomes too energy expensive to maintain.

Interoperability will be really tricky to reach after (if?) the internet goes down.

Secure Scuttlebutt seems pretty interesting: it lets you synchronize with the network in a disconnected manner. It is compatible with small mesh networks and/or cuban pakete-style cold transfers.

It is still a pretty recent project and has some shortcomings:

- you can't have any kind of forward secrecy when using private messages.
- you can't use multiple devices for a same identity.
- the current implementation are a performance hog (electron-based...)

However, the community is pretty active and works toward fixing those shortcomings.

Have you tested it?

I just sent you a lobsters invite to the mail you used to respond to my feedback.

@rra @sifr Oh yeah, I forgot, you made the right choice regarding the dithering, it looks really nice!
@Ninjatrappeur @rra @sifr TBF there's a client called patchfoo that's a static web interface for SSB. It's their version of brutaldon...

Also the patchfoo developer has made a extension for dillo to understand the gopher protocol. That kind of nice person :)

@Ninjatrappeur @rra @sifr sorry for jumping in:
SSB is a protocol. Only some clients are Electron based.
What is really a PITA is that you cannot ever delete anything and you have to download full history of a user because it is a hecking blockchain-like structure.

@charlag @sifr @rra @Ninjatrappeur

Actually you don't have to download the whole history, clients may jump in at any point in time. It's not that you need to verify every post a user ever made. All posts are signed by the author's priv key so they can be validated individually.
@ckeen @charlag @sifr @rra

This is precisely what makes me hopeful about ssb.

I have a related noob question though: is there any kind of distributed system being able to both assert consistency and providing a way to permanently delete a sent information?
@Ninjatrappeur @charlag @sifr @rra How can you permanently delete a postcard you have sent out to a friend with the hope that it gets spread to your friends?

Technically impossible. You could choose an encryption scheme and 'lose' the key afterwards, but your (ex)friends will have access nonetheless.

@ckeen @sifr @rra @Ninjatrappeur hm, pardon me if I wrong then. I Rennes that the client I uses did that and I made wrong assumptions

@hhardy01 Apparently not, I though it was a transfer protocol. Do you have any good ressource on it? The wikipedia page is quite empty.


The point is, uucp and the associated protocols are very good for intermittent connections.

Sign in to participate in the conversation

Welcome to, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.