I take my shitposts very seriously.

  • 8 Posts
  • 761 Comments
Joined 3 years ago
cake
Cake day: June 24th, 2023

help-circle




  • Tailscale Funnel will let you expose a host to everyone on the internet. You’ll need the Tailscale client running on either the Jellyfin host or a reverse proxy pointing to it. Tailscale itself will act as a reverse proxy with TLS encryption, plus a DNS server.

    Exposing a service to the internet will always present some risk. You should definitely run your LXCs as unprivileged, unless needed otherwise, to mitigate the potential damage if an attacker escapes the container, or put the services in full virtual machines.




  • Not a lot, just enough to get the feel of the game, but also to realize that I’m not the target audience. In some ways, it’s similar to Counter-Strike 1.6 or Team Fortress 2 back in high school: if I have a group of friends and an hour of free time, then sure, I might hop on. But I won’t be investing the time and long-term effort that an extraction shooter expects of me.

    The moment to moment experience is good. Bungie haven’t forgotten how to create a tight FPS experience. But the game needs both longevity and a healthy playerbase, that’s what concerns me. Fans of hardcore extraction shooters already have Tarkov and Hunt, and casual players already have Arc Raiders. It takes something exceptional to move players out of their “home” game.



  • Marathon is probably life or death for Bungie. Sony can’t exactly afford to put out a mid game after spending so much on the studio… and “mid” is exactly what Marathon felt like. Just like so many copycats during the battle royale boom.

    I don’t think it will fail (or if it does, not as hard as Highguard), but unless it manages to stand out from the Tarkov/Arc Raiders/Hunt: Showdown oligopoly, it won’t bring in the numbers to please Sony.


  • By “dev team”, I’m guessing you mean the artists, designers, programmers, and testers; the people who spent the last five or so years actually creating the game. Yes, it sucks for them. Their years of work have effectively been thrown in the trash because of Wildlight’s management. I hope they find better work soon, and I hope the management become personae non gratae in the industry.






  • Simply dual-booting is viable. My Win10 + Arch worked well for over a year. If you’re worried about Windows Update nuking the EFI partition, you can clone a backup of just that partition (dd or a dedicated tool like Clonezilla) that you can then restore from a live environment if needed. Another option, if the disk becomes unbootable, is to boot into a live environment from a USB stick and simply reinstall GRUB into the EFI partition.

    (edit) It’s also a good idea to reduce the frequency of forced updates. You can do that using WinUtil.


  • Windows Update has a habit of eating the EFI partition. That’s how I finally switched to full-time Linux. LTSC doesn’t update as frequently as Win10 Pro, and probably doesn’t touch the EFI partition as much, so there’s a smaller chance for that to happen.

    Dual-booting can work for years without issue. My method just ensures that Windows Update has absolutely zero chance to fuck with the ESP.





  • If you have IPv4 addresses, I guarantee you’re behind at least one NAT gateway. What you need is a Tailscale subnet router, or something equivalent from another service.

    In the most basic configuration, the Tailscale client facilitates communication (by using some UDP black magic fuckery) between one host it is running on and another host it is running on that are both connected to the same tailnet (the virtual network between Tailscale hosts). For this purpose, it uses addresses from the 100.64.0.0/10 “shared address space” subnet. These addresses will only be reachable from within your tailnet.

    If you want an entire subnet (e.g. your LAN) to be accessible within your tailnet, you need to set up a subnet router. This involves configuring the Tailscale client on a device within the target subnet to advertise routes (tailscale set --advertise-routes=192.168.1.0/24), allowing the host to advertise routes in the admin page (Machines -> -> Edit routes), and configuring the Tailscale client on external hosts to accept advertised routes (tailscale set --accept-routes).

    If you want your servers to be accessible from anywhere on the internet, you’ll need Tailscale Funnel. I don’t use it personally, but it seems to work. Make sure you understand the risks and challenges involved with exposing a service to the public if you want to choose this route.