• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle











  • Yeah, I mistyped part of the sentence. Should have been “without some serious effort or illegal methods.” Serious effort is well beyond most ISP’s. They aren’t sniffing wireless AP’s then busting down doors to find out if its a 5g AP or an AP using their network. I actually know quite a bit about WiFi signals. I happen to be certified in Meraki (CMSS). If the uni said “no wireless signals” that would be a completely different story.



  • Sure, people might not care, but that doesn’t change the facts. Experts aren’t denying the legitimacy of the Panama or Paradise Papers, but they are saying that the idea of megacorporations secretly listening to your microphone and selling you products based on that is false. If they were doing that, it would be pretty easy to find out. Smartphones aren’t some mysterious black box; security engineers and hackers are constantly checking for these kinds of exploits. If corporations were actually spying on us through our phones, it would be the biggest topic at DEFCON. Believing that this could be kept secret would require assuming that all these experts are either paid off or in cahoots with the corporations, which veers into full-blown conspiracy theory territory.




  • Tracking is actually incredibly tiny bandwidth-wise. Like, fractions of a fraction of your bandwidth. Adserv is also very tiny due to modern edge server infrastructure. Ads are static content. It’s already cached and likely within the same city as you. That’s part of why ads tend to play perfectly and fast while the content can be slow. On the other hand, that obscure 200 sub guy ranting about why the square-headed screws inability to catch on is a giant American conspiracy to keep Canada from commercial dominance is almost certainly not locally cached. It has to come from Google’s video content servers way out in silicon valley.


  • Network engineer here. There’s a lot of reasons your network might not work well. None malicious.

    1. You’re watching it in high def on a slow connection. Try going back to the "good old days"of 360p and see if it’s fast.

    2. Your network may be bottlenecked somewhere. Try using speedtest (search for it) and see if you’re getting slow connection quality.

    3. You may be getting packet loss. Using the ping command, try running it indefinitely for a little while (windows key+r, cmd, “ping 8.8.8.8 -t”) see if there are blips of failures.

    Remember! Never ascribe to malice what can be attributed to incompetence. Your isp, Google, and yes, even Microsoft, don’t want you to have a bad experience using your computer. Lots of people with 0 networking knowledge but a bone to pick with the system will give you unhelpful advice.



  • grandkaiser@lemmy.worldtomemes@lemmy.worldIt feels wrong
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    4 months ago

    I’m skeptical that you’re giving the full story

    No, you’re right. There’s a much bigger story here. I was just trimming out a lot of it since I don’t normally run into people who can follow along easily. Akamai, for example, uses the proprietary AKAMAICDN record to allow the functionality of a CNAME. For example: foo.com AKAMAICDN’s to foo.com.edgekey.net (edgekey.net of course being the Akamai edge server suite). So someone using Akamai can do that to allow them to use the apex (but will still very likely have a www.foo.com CNAME foo.com setup to catch people who did a www anyway) Cloudflare uses CNAME flattening to “cheat” the CNAME rules by doing the CNAME DNS lookup internally and pretending to be authoritative for the request.

    You don’t typical have your webpage itself delivered by CDN, you have your static assets delivered by CDN. Why can’t you put your static assets in a subdomain that gets a CNAME?

    You can most certainly put static assets in a specific subdomain (and in fact, that’s how most setups are), but the CDN itself often requires handling the entire request at the beginning. You don’t want, for example, an A record at the apex pointing directly at your origin servers (terrible idea for security & performance; kind of defeats the purpose of the CDN), instead you want the user to connect to an edge server and have that edge server immediately serve the static content while the origin is contacted by the edge server for any non-static content that the user needs. This allows the CDN to do their cloud magic while your origin servers can do as little work as possible with as few people as possible. Effectively, you can block all requests to your servers that are not from your CDN. Many CDNs these days are also a major security feature.