Replying to @mrmaplebar@fedia.io
Use Tailscale, it's stupid simple. it is a Wireguard wrapper anyways.

Replying to @mrmaplebar@fedia.io
Use Tailscale, it's stupid simple. it is a Wireguard wrapper anyways.
Replying to @SlimePirate@lemmy.dbzer0.com
Vibe coded slop by one person. It is not really an open source project if nobody can work on it.
Replying to @Teknikal@anarchist.nexus
Does fluffy chat have voice channels?
Replying to @Some_Emo_Chick@lemmy.world
For people that want advice for finding an alternative service, go to the github repo and figure out the state of development. Find the answers to these questions: how many active developers are there? when was the last commit? does this look like LLM code? What do the issues and PRs look like? Remember that we don't want to have to do this again in 10 years, so open source and decentralized are major points.
Replying to @belsedar@slrpnk.net
I was using a etke as a hosting service for a while but it was a bit expensive and I wanted more control. I set it up on my homelab with a VPS running a reverse proxy and like it a lot more. I believe I deployed it with someone's Ansable playbook I found on github.
Make a matrix.org account and play around with it. I hate the Element client though.
Replying to @litchralee@sh.itjust.works
For built in listeners use ncat, but nmap package is not always included. If you are on Windows find some listener Poweshell script, it will be under 10 lines, with Test-Connection. When I was a SysAdmin one repeated problem was UDP traffic was not working. When you tested the TCP port it would work, verifying that the connection is there, but UDP for a variety of reasons is problematic.
Replying to @litchralee@sh.itjust.works
With TCP there are built in listeners on OSs which you can use to test. Also TCP will work before UDP. For whatever reason firewalls and such do weird things with UDP traffic. I always use a cli tool that I can't remember the name of for testing.
Replying to @lucullus@discuss.tchncs.de
Yes it is uncommon, as people have mentioned it is a Wireguard wrapper. Try just using Wireguard and troubleshoot from there. I would want to know what that 'simple' solution is failing. Your workaround could have similar issues.