• 0 Posts
  • 534 Comments
Joined 10 months ago
cake
Cake day: March 20th, 2025

help-circle

  • Yup. The reverse proxy takes http/https requests from the WAN, and forwards them to the appropriate services on your LAN. It will also do things like automatically maintain TLS certificates, so https requests can be validated. Lastly, it can usually do some basic authentication or group access stuff. This is useful to ensure that only valid users or devices are able to reach services that otherwise don’t support authentication.

    So for example, let’s say you have a service called ExampServ running on 192.168.1.50:12345. This port is not forwarded, and the service is not externally available on the WAN without the reverse proxy.

    Now you also have your reverse proxy service, listening on 192.168.1.50:80 and 192.168.1.50:443… Port 80 (standard for http requests) and 443 (standard for https requests) are forwarded to it from the WAN. Your reverse proxy is designed to take requests from your various subdomains, ensure they are valid, upgrade them from http to https (if they originated as http), and then forward them to your various services.

    So maybe you create a subdomain of exampserv.example.com, with an A-NAME rule to forward to your WAN IPv4 address. So any requests for that subdomain will hit ports 80 (for http) or 443 (for https) on your WAN. These http and https requests will be forwarded to your reverse proxy, because those ports are forwarded. Your reverse proxy takes these requests. It validates them (by upgrading to https if it was originally an http request, verifying that the https request isn’t malformed, that it came from a valid subdomain, prompting the user to enter a username and password if that is configured, etc.)… After validating the request, it forwards the traffic to 192.168.1.50:12345 where your ExampServ service is running.

    Now your ExampServ service is available internally via the IP address, and externally via the subdomain. And as far as the ExampServ service is concerned, all of the traffic is LAN, because it’s simply communicating with the reverse proxy that is on the same network. The service’s port is not forwarded directly (which is a security risk in and of itself), it is properly gated behind an authentication wall, and the reverse proxy is ensuring that all requests are valid https requests, with a proper TLS handshake. And (most importantly for your use case), you can have multiple services running on the same device, and each one simply uses a different subdomain in your DNS and reverse proxy rules.



  • mic_check_one_two@lemmy.dbzer0.comtomemes@lemmy.worldchrome being chrome
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    3 days ago

    That disclaimer was actually a result of the lawsuit. It didn’t always say that. Google was sued for intentionally misleading users, by tacitly encouraging their misheld beliefs that it made them invisible. Basically, Google wanted to track users. And Google knew that some users trusted incognito mode way too much. And instead of correcting that, they actively misled users into believing that incognito mode was more secure. Because if users believed they were invisible, Google could continue to track them when they thought they weren’t being watched.

    They got sued for those misleading statements, and lost. And now the splash screen specifically says that Incognito Mode doesn’t make you invisible.


  • mic_check_one_two@lemmy.dbzer0.comtomemes@lemmy.worldchrome being chrome
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Well yeah, that’s all it ever was. The lawsuit was because of misleading/deceptive statements made by Google, which led some (intentionally misinformed) users to believe that Incognito Mode was more private than reality.

    Basically, the company knew some users believed Incognito Mode hid their browsing activity. Not just from their local machine (via no logged site history, clearing cookies, etc), but also by hiding it from prying eyes like Google. Some users genuinely believed Incognito Mode was basically some sort of combination of Tor, degoogling, VPN, tracker-blocker, etc… And Google actively encouraged this incorrect belief, because they could continue to siphon off users’ data when they thought they weren’t being watched. The active encouragement of incorrect beliefs is what the lawsuit was about, not the data collection.




  • It can be both server and DNS provider. For instance, Cloudflare allows you to set rules for what traffic is allowed. And you can set it to automatically drop traffic for everything except your specific subdomains. I also have mine set to ban a IP after 5 failed subdomain attempts. That alone will do a lot of heavy lifting, because it ensures your server is only getting hit with the requests that have already figured out a working subdomain.

    Personally, I see a lot of hacking attempts aimed at my main www. subdomain, for Wordpress. Luckily, I don’t run Wordpress. But the bots are 100% out there, just casually scanning for Wordpress vulnerabilities.





  • Yeah, I actually agree. If game devs want to remaster old games, they have every right to do so. Ideally, these remasters would bring meaningful quality of life upgrades, while still allowing the fans to replay the game as they originally did.

    One of my favorite old games is Final Fantasy X, and the remaster was actually really good. They botched the character face models, but added a lot of QoL improvements that you wouldn’t typically find in an emulator without jumping through a few hoops.

    Things like 2x/4x speed which disables during cutscenes, so you’re not wasting time watching the same battle animations constantly. Auto-battle, for when you’re already completely overpowered for an area and don’t want to mash X to keep attacking. An across-the-board buff that makes grinding a breeze. The option to change the random encounter rate, to make them more frequent or non-existent. An option to choose between the classic or remastered music tracks. Etc…

    Sure, lots of those things could be implemented in some way by an emulator. But having them baked right into the base game allows for things like the speed boost to automatically disable during cutscenes. Plus it opens the door for native mod support. Untitled Project X is a wonderful mod that is only possible because the game isn’t running inside of an emulator. Even my complaint about the character faces can be fixed via a simple texture swap mod.

    All of this is to say that I’m happy to emulate things when needed. But since that FFX remaster launched, I haven’t felt the need to boot it up on an emulator. Because the remaster gives me anything I would want from an emulator, and then some.



  • It’s learned helplessness. They hit a roadblock they couldn’t figure out, and instead of trying again, they just went “well I guess this tech stuff isn’t for me.” And now that’s the attitude they fall into every time.

    It’s like if someone lost their first board game, and just wrote off board games entirely because they aren’t any good at them. And any time they do need to play a board game, they can just call their favorite nephew to play it for them.


  • Yeah, the Tizen app will be huge for me. I’ve been dual-running Plex and JF specifically because a few of my users have Tizen devices. And there’s no way I’d be able to explain sideloading to my “throws up their hands and says it’s too complicated as soon as they see anything unexpected” relatives over the phone.

    Luckily, I got a lifetime PlexPass like a decade ago, before JF even existed. So it’s not like supporting Tizen is costing me anything extra.


  • mic_check_one_two@lemmy.dbzer0.comtomemes@lemmy.worldSo annoying
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    10 days ago

    If the person trying to bring back thorn really wanted to be pretentious, they would start using y instead. Y used to make the “th” sound, (the same way they’re trying to use thorn), which is where “ye olde” stuff comes from. It was pronounced “the old” just like modern English, but was spelled with a y instead of th.



  • This is pretty much what we did in my first apartment. There were four of us, and we all just circled our monitors around one end of a dining table, and the other end was kept clear for eating, projects workspace, etc… Every night was like an old school LAN party. I’ll admit, it wasn’t the worst setup. It was definitely “college kid in a cramped dorm room” vibes, but that’s pretty much what we were. Getting around the back of the table was kind of a pain, but the only people who ever realistically needed to get back there were the two people who sat on that side.