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.
#Hypha
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
@edsu
#socialcoop Tech Working Group minutes
https://www.loomio.com/d/UwAeiBgE/tech-meeting-minutes
mention #hypha. What's the Hypha connection in #techwg?
I ask bcos Hypha are important contributors in #meetcoop and it's good to be aware of how this coop-to-coop admins ecosystem is weaving.
Nice minutes, nice to see the kind of consideration being given to stuff under 'tech' rubric. I note #bonfire too. Wasn't too impressed by bonfire when I tried it (as a UI/UX) but endorse the principles and the experimenting.
There's also a delete & redraft option which has already saved my bacon when I forgot to add alt-texts and adding them after posting wasn't working.
Tags are the #Hypha of (new) social networks the sort of underground structure that allows them to work, for shit or for good.
@andia
This is really helpful thanks, and will read. Missed your earlier posting in Dripline, but will catch up. Greetings to #hypha friends.
@disco_coop
A Traversal Network of #feminist #servers (#ATNOFS) travels to #Bucharest this weekend where #HYPHA has organised a two day programme https://hypha.ro/program
More about ATNOFS here https://culturalfoundation.eu/stories/cosround4_atnofs
with @snisioi !
Seeing sync + proxy running together at the same time for the first time in Indie Web Server… getting closer :)
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/
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/
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.
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
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/
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).
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.)
#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/
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst