-
chevron_right
event-driven #wireguard connection to #homelab
Simone • 2 June

Here's how I'm using a WireGuard tunnel to connect privately to my homelab, on the go.
mic_none No sound detected from your microphone
Simone’s blog
event-driven #wireguard connection to #homelab
Simone • 2 June
Here's how I'm using a WireGuard tunnel to connect privately to my homelab, on the go.
Simone • 31 May
As promised!
#rsnapshot in progress
Simone • 11 May
How-to coming up next!
COMMutiny got custom #emojis
Simone • 14 April
In your configuration panel, emoji tab, you can pick your favorites, which will show up in the chat emoji's picker!
gemini://woodpeckersnest.space/~roughnecks/archive/termux-fiddlings.gmi
About #pubsub permissions
Simone • 11 January • 8 visibility
A recap about pubsub support on this server and #Movim instance:
Every JID from every server can send them
Every JID from every server can publish them
This is more complicated.. Every JID is subject to their own server's permissions, since the pubsub component used to create a node / publish content is the one of the server you belong to.
In prosody stable, pubsub support is still limited, so our #XMPP server is configured to allow creation of new nodes (communities) to admins only. I could just set every @wpn user as admin for the pubsub component, but that would mean everyone could post in any community created by another @wpn user - and that sounds just bad. The owner should be able to choose the publishers for their community, making use of the permissions available in Movim.
I foresee 2 possible solutions, none of them will happen soon though:
commutiny
's own XMPP server (running ejabberd most likely)Simone • 11 January • 4 visibility
Public brief to test comments and likes.
Simone • 11 January edit • 5 visibility
Here's the official #XMPP room for `commutiny`, join the conversation!
xmpp:commutiny@chat.woodpeckersnest.space?join