#hypha — Public Fediverse posts

My team at #Hypha has a new page describing our work. Give it a peep and feel free to reach out if you want to collab with us on your projects.

https://hypha.coop/co-creation-lab/

Listen to my submission to the Produce This contest, a chill dreamy soundtrack to Desert Nights.
The challenge was to use #nativeinstruments new #hypha synth, I used 17 instances of it in this track 😁

Listen here: https://metapop.com/rule/tracks/desert-nights/273841

Seeing sync + proxy running together at the same time for the first time in Indie Web Server… getting closer :)

#IndieWebServer #Hypha

Indie Web Server v9.1.0 release

This is a minor release that brings better error handling.

https://ar.al/2019/04/30/indie-web-server-9.1.0-better-error-handling/

#IndieWebServer #Hypha

Indie Web Server v9.0.0 release

* Mostly housekeeping
* Breaking change: proxy syntax
* Drops Windows support (use Windows Subsystem for Linux)

https://ar.al/2019/04/29/indie-web-server-9.0.0-housekeeping/

#IndieWebServer #Hypha

Indie Web Server 8.2.0: Cascading archives for an evergreen web

https://ar.al/2019/04/20/indie-web-server-8.2.0-cascading-archives-for-an-evergreen-web/

I just released version 8.2.0 of Indie Web Server. This version brings with it a cascading archives feature to make it easier than ever for you to support an evergreen web and not break existing links as you evolve your sites.

#IndieWebServer #Hypha

Indie Web Server 7.1.0: Launch a live secure static site with a single command

https://ar.al/2019/04/01/indie-web-server-7.1.0-launch-a-live-secure-static-site-with-a-single-command/

I am really excited about this one. To launch a secure, live static site run this on any VPS that has a domain name pointing to it and Node.js installed:

npm i -g @ind.ie/web-server && web-server --live

#Hypha #NotAnAprilFoolsJoke

Indie Web Server: now with native 404 to 302 support for an evergreen web

https://ar.al/2019/03/31/indie-web-server-now-with-native-404-to-302-support-for-an-evergreen-web/

#hypha

Ooh, the stickers I ordered for #hypha arrived.

If you’re at the events in Lille or Copenhagen this month, ask me for one.

:indieHeart:

Right, got Let’s Encrypt certificates working again in Indie Web Server with a less-hackish ACME TLS. Some last bits of telemetry to remove from the Greenlock fork before I can hopefully move onto other things. #hypha

I’m very excited about this – it’s one of the first pieces of the bridge we’re building towards the peer web (it’s on the current web leg of the bridge – that’s where are now.)

Democratising the ability to develop/deploy personal sites is an important step. This is the first of a number of more specialised modules I’m considering releasing as I build the scaffolding of #Hypha. Hypha also will/does use Indie Web Server for its untrusted node (https://source.ind.ie/hypha/hypha).

Breaking ground (not ground breaking)…

https://source.ind.ie/hypha/hypha

#hypha

I’m starting to hit diminishing returns with the spikes (which have morphed, really, into iterations and I’ve started to feel the need to write unit tests, which is a smell that we’re past the initial experiments) so I’m going to start the #hypha project proper in a maintainable manner this week.

Closing the persistence spike in a non-functional state. (I now also have a plan for how to implement signed in/out states using two hyperdbs per node.)

https://ar.al/2019/02/12/hypha-spike-persistence-1/

#Hypha Monday morning update:

Started WIP glossary: https://ar.al/2019/02/18/hypha-glossary/

Updates on persistence spike: https://ar.al/2019/02/12/hypha-spike-persistence-1/

Got the following error on multipass (beta channel) version 0.5:

cannot connect to the multipass socket

If you encounter the same thing, refreshing the snap to version 0.5-27-g49baef0 fixed it for me:

sudo snap refresh multipass --edge --classic

Likely related to this issue: https://github.com/CanonicalLtd/multipass/issues/555

If you want to know what multipass is or how it will be used in #hypha, see https://ar.al/2019/01/05/hypha-spike-deployment-1/

#deployment #provisioning #ubuntu #automation #cloudinit

On the General Architecture of the Peer Web (and the placement of the PC 2.0 era within the timeline of general computing and the greater socioeconomic context)

https://ar.al/2019/02/13/on-the-general-architecture-of-the-peer-web/

Just wrote a thing on my thoughts on the Peer Web and where I see us going with #Hypha.

WIP: New #Hypha spike: Persistence-1

https://ar.al/2019/02/12/hypha-spike-persistence-1/

#Hypha spike multiwriter-2 is now complete.

https://ar.al/2019/02/01/hypha-spike-multiwriter-2/

I will be moving onto exploring persistence next (all spikes so far have been using random-access-memory as the storage layer).

Once persistence is implemented, I will look to refactoring to pull out a general purpose auth module with a simple API that handles decentralised sign up/sign in/and secure p2p authorisation of new nodes/devices.

#Hypha multiwriter-2 spike end-of-day status update

Any authorised node can now authorise any other node, including a native node authorising a browser node and vice-versa with the unprivileged always-on node acting as a dumb relay:

[Native] ←TCP→ [Native] ←TCP→ [Always-on] ←WebSocket→ [Browser] ←WebRTC→ [Browser]

Ephemeral communication between nodes is end-to-end encrypted.

https://ar.al/2019/02/01/hypha-spike-multiwriter-2/

Morning progress on #hypha:

✔ Extend the secure ephemeral messaging channel to support unprivileged relay nodes (the always-on nodes).

✔ Implement secure ephemeral messaging channel on WebSocket connection. (Encrypted messages are now relayed by the always-on node.)

Secure ephemeral messaging channel: https://source.ind.ie/hypha/secure-ephemeral-messaging-channel

Latest spike (WIP): https://source.ind.ie/hypha/spikes/multiwriter-2

Made some good progress on the latest #Hypha spike this week.

We now have a secure (e2e-encrypted) ephemeral messaging channel used for authenticating new nodes (https://source.ind.ie/hypha/secure-ephemeral-messaging-channel) based on Paul Frazee’s excellent work on dat-ephemeral-ext-msg (https://github.com/beakerbrowser/dat-ephemeral-ext-msg). Also, that also now has support for hyperdb and a test suite that covers hypercore, hyperdb, and hyperdrive in master as Paul just merged my request.

WIP post: https://ar.al/2019/02/01/hypha-spike-multiwriter-2/

WIP repo: https://source.ind.ie/hypha/spikes/multiwriter-2

@imacrea Web site as unprivileged always-on node in p2p network of web and native nodes (#hypha in a nutshell. Early spikes.)

#Hypha spike progress: always-on node is now relaying ephemeral messages to both browsers (via WebSocket) and native nodes (via TCP) in addition to browser-to-browser (via WebRTC).

https://ar.al/2019/02/01/hypha-spike-multiwriter-2/

Next: deduplication (due to messages being both relayed and peer replicated) and encryption.

#Hypha (WIP)

Made progress on multiwriter-2 spike: p2p authorisation requests for new nodes proof of concept is working over Dat ephemeral messaging extension channel.

Updated the WIP blog post with latest details: https://ar.al/2019/02/01/hypha-spike-multiwriter-2/

I can haz ephemeral messaging channel extension on dat protocol and I can haz seamless authentication proof of concept. Little win.

:awesome:

#hypha #spike

Scratch the last #hypha update. Just realised I don’t need reproducible local writers in order to implement the flow I want and, in fact, that I was basically replacing an indentifier with a statistically insignificant risk of collision with on that could very easily collide.

Fun times.

Oh well, you code and learn :)