I try things on the internet.

rarely, shit just works.

  • 0 Posts
  • 48 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle
rss





  • 1 contributor’s opinion and the existence of one community does not an argument make.

    the devs don’t care about laws, if you want to put it so broadly, because the devs aren’t the ones who would get in trouble here, anyway. instance owners would likely catch the most trouble, especially because you can also add your own gdpr compliance if you want to.

    also most devs aren’t facebook. most devs don’t really care too much about tracking users. the commercial sector on the other hand…








  • They wouldn’t need a dongle for phone cases, they could easily make room for a headphone jack, but they don’t as a concious decision for a few reasons:

    • “people don’t want or use them” as “the market” has “spoken”. In other words, phone manufacturers removed it, the public didn’t revolt, people bought more wireless headphones and other manufacturers followed suit.
    • less lint in your phone I guess. A few more extra phone features, or capacity or battery life. USB-C truly is the future. Why add a feature that most people won’t use instead of features they will use?

    I mean there are many MANY reasons why we would want to keep the jack:

    • we could actually use the FM receiver that phones are capable of and use the headphone jack as an antenna, as was the case when smart phones started hitting the market.
    • batteries die and the wireless headphones have batteries. Really kinda silly to have two products that can do what you need with one wire but they no longer can because there are no magic pixies to send over the air from one to the other.






  • +1 for nginx, although there has been some concern because nginx is developed by a group of russians though it is open source and appears to still be widely used. If this worries you, look into traefik.

    Otherwise does your ProxMox setup run docker containers? If so you can use NginxProxyManager which has a web gui for configuring your virtual hosts.

    At a high level what you need is this:

    • all domains routed to your host (or home if self hosting) IP.
    • that IP needs to have a reverse proxy server like traefik or nginx listening on port 80 and port 443 if you want ssl/tls.
    • your app servers which run lemmy, nextcloud, etc can be anywhere on your network where your reverse proxy can access. You’ll need to create vhosts for each. The server uses the Host header to determine which IP to reverse proxy to, eithe lemmy.moorefam.net or nextcloud.moorefam.net
    • the reverse proxy will get the content from lemmy or nextcloud and serve it via that IP and port.
    • ensure your home router is port forwarded on 80 (and 443 if you want ssl/tls) if you want to access these instances from the public internet but beware, you might want to add a firewall in-between if you aren’t confident in your router’s firewall.