This looks useful: https://age-verifier.kibty.town/
#Discord
Also; just use a #forum and a #Mumble server. If you really need live text chat, consider #xmpp, but seriously forums are far more useful long term.
Jérôme Herbinet | FLOSS
boosted
Le bonheur tient en deux noms : SuperTuxKart & Mumble ✨
Pas de chichis, juste de la jouabilité et du fun pur entre passionnés. La preuve qu’avec du Libre et de la simplicité, on crée les meilleurs souvenirs ! 🐧💨
On se retrouve sur la piste ? 🏎️💨
Envie de me rejoindre ? Les infos de connexion sont sur la capture ! 😉
Le bonheur tient en deux noms : SuperTuxKart & Mumble ✨
Pas de chichis, juste de la jouabilité et du fun pur entre passionnés. La preuve qu’avec du Libre et de la simplicité, on crée les meilleurs souvenirs ! 🐧💨
On se retrouve sur la piste ? 🏎️💨
Envie de me rejoindre ? Les infos de connexion sont sur la capture ! 😉
Le Alternative
boosted
Alternative a Discord
Quali alternative a Discordo esistono? Abbiamo provato a riassumere alcune alternative possibile in questo articolo!
https://www.lealternative.net/2021/03/26/alternative-a-discord/
2 media
David Vasandani
boosted
I have a very weird issue with my #tailscale + #mumble server setup:
I have a murmur (mumble) server that binds to the tailscale interface on my server.
I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.
Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".
The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.
How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.
#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin
CC @tailscale
Please boost 
I have a very weird issue with my #tailscale + #mumble server setup:
I have a murmur (mumble) server that binds to the tailscale interface on my server.
I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.
Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".
The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.
How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.
#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin
CC @tailscale
Please boost