• 1 Post
  • 312 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle


  • It could just do with a UI refresh and maybe some added functionality

    That is actually huge ask.
    Mumble works in an “engineer brain” kinda way. Cause it has been made by engineers making sure the underlying tech is available to be used in so many scenarios.
    Making it work in a “user” kinda way is a huge change.
    And it would either make the code really difficult to maintain, or would isolate the power users by restricting the flexibility of mumble.
    The fact that mumble is FOSS is absolutely fantastic!

    Feel free to fork the project and refresh the UI.
    Or sponsored programmers to do this. If there is actually a market, you would be able to overtake mumble. You can even start from their codebase, the license is very permissive (just make sure you credit mumble!)






  • And it CAN fix all your problems. But that doesn’t mean you don’t have to fix the problems yourself.
    Which is often more than I can deal with. Thankfully - so far at least - all my problems are problems other people have encountered and have documented (and - in many cases - contributed to various projects to get the fix to more people)



  • Pretty much, yes.
    Developers for the older consoles employed all sorts of hacks and used all sorts of undocumented features.
    Emulators of N64 would develop the emulator for something like 80% of the features of 80% of the games, then put in specific workarounds for the oddities of each game.
    Which is why some games are better on specific emulators.

    Also, decompilation lead to a greater understanding of the various glitches. DK64 and Mario 64 speedruns benefitted massively from this.
    And also fun hack/mods like randomisers and hardcore modes, massively extending the games playability.

    But yeh, the things devs did back in the day is bonkers







  • accessed from the internet

    Accessed only by you and close family/friends who you are also hosting services for?
    Or accessed by anyone?

    “Accessed by anyone” carries more risk.

    “Accessed by users you host for”, the risks can be eliminated (well, other than risks from those users) by using a VPN. As in, only the people authorised to be on the VPN can access the services.
    Wireguard is the go-to these days.
    Tailscale is much easier and free for 3 users and 100 nodes.

    If it absolutely has to be “accessed by anyone” I would look into a “reverse proxy over VPN/tunnel” or just straight tunnel style approach like chisel (or crowbar, or corkscrew), rathole, frp, or cloudflare tunnels.

    Basically, don’t point a domain at your home public IP and don’t forward ports on your home router/firewall






  • So you have local DNS set up?
    If you ping (or dig) speed.mydomain.local, does it resolve the same address as local_ip?
    Considering you are accessing local_ip:3000 and the domain on port 443, there is clearly a firewall somewhere redirecting packets or a reverse proxy on the domain but not on local_ip:3000

    Follow the port chain, forwarding, proxying etc. One of those will be bottlenecking. Then figure out why

    Edit:
    Just because your ISP speed is 100mbps and you are seeing 500mbps, doesn’t mean the connection isn’t hairpinning through your router via it’s public IP (as in, the traffic never leaves your router, but still goes through it)