• 0 Posts
  • 271 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle
  • No problem. I just spent a few minutes prompting Gemini and requested that it provided sources. I think it’s about right, because it matches what I remember (LTT had a YT privilege to replace videos in situ, where as GN did not), but the usual AI caveats apply. Sorry if that seems low-effort, but I don’t see a rule against quoting AI, and I’m not that invested in this either. (Mods: please take this down if it’s against any rules).

    The response it gave me at first was a bit too long for this post so I asked it to summarize, and I’ve added the other sources it gave me to the bottom.

    Here is a condensed summary of the controversy:

    • The Core Issue: In August 2023, the YouTube channel Gamers Nexus (GN) published a massive 44-minute exposé criticizing Linus Tech Tips (LTT) for rushing content, which led to significant data and testing errors in their hardware reviews.
    • The “VIP” Privilege: GN revealed that instead of taking down flawed videos and losing their algorithmic momentum, LTT was using a backdoor YouTube privilege—available only to massive creators through a partner manager—to silently replace the source video file on the backend after publication.
    • The Proof: GN proved this by comparing the YouTube versions of LTT’s videos to versions syndicated on the Chinese platform Bilibili. Because LTT didn’t have the same VIP privilege on Bilibili, the original uncorrected videos containing glaring data errors were still live there, while the YouTube versions had been magically fixed.
    • The Fallout: GN argued this was an unfair advantage that allowed LTT to prioritize quantity over quality without facing the massive financial and algorithmic penalties that regular creators face when forced to re-upload. Following the intense community backlash, LTT paused their entire production schedule to overhaul their quality control labs and promised full transparency regarding future video corrections.

    Why GamersNexus Hates LinusTechTips

    This video essay provides a comprehensive retrospective and breakdown of the entire Gamers Nexus and Linus > Tech Tips controversy, providing further context on the claims and the resulting fallout.

    Sources:


  • Agreed. I don’t think I explained myself clearly enough: I want them to have a presence online. Among the reasons being exactly what you’re pointing out. However, I think at least for smaller cities with very little staff, it’s not realistic to ask them to literally self-host it (as in having a server on-prem running it). I would be fine with them outsourcing it or cloud-hosting it under their own domain. A potential solution for the small ones could be something like a state-level hosted service where municipalities can sign up and get their own accounts, for example. That would work even for something like Rittman, Ohio pop. 6,131.









  • Not so sure I want them to self host, just based on their track record for security, but I would like them to be more visible.

    Also news outlets could benefit from doing this instead of us having to rely on repost automation.

    I would also love to see peertube become more competitive to YouTube. It would probably need some kind of revenue sharing model or donation integration for that though.


  • Your diagram is almost right, but I think it will help to understand more of the details. It’s important to understand the difference between DNS (domain name lookup) and IP routing.

    To break your diagram down more, this is what happens when any computer looks up your website:

    1. The device does a DNS lookup of “example.com” using their name server, which may forward it to another DNS server (most home routers do this). I won’t go into the multiple levels of DNS lookups and caching here.
    2. Through looking it up by DNS, the device now has the final IP. DNS is now out of the picture and we’re doing IP routing.
    3. The device tries to make an HTTP connection to your external IP. HTTP is a protocol that runs over TCP/IP (UDP is used for QUIC/HTTP3). To keep things simple I’ll stick with old fashioned HTTP over TCP without SSL. I am also skipping over NAT.
    4. For TCP, it performs a handshake, which the reverse proxy will negotiate. Once the connection is established, the browser speaks HTTP to the reverse proxy. It looks something like:
    GET / HTTP/1.1
    Host: example.com
    ...lots more headers...
    <blank line>
    
    1. The reverse proxy then takes that request, maps it to an upstream (if any), and makes another request to it via the configured transport. If that part falls down, you will see a 503 error. Otherwise, you will see the response from the upstream, possibly with some modifications made by the reverse proxy (some will rewrite links and cookie paths, for example)
    2. The reverse proxy sends that response back to the client.

    That’s all very simplified, of course.

    As others pointed out, things may seem to work differently from the “inside”, if hairpinning is not available or enabled. This is not related to DNS, but to IP routing. The firewall doing NAT can get confused and not know what to do when an internal request goes to an external IP that it itself has. When it turns that around and routes it back to the internal network, that’s called hairpinning.

    One “fix” for this, often used in enterprises, is to use so-called split DNS. All that means is that if you’re asking your internal DNS server for an internal name, it will give you the internal address (192.168.1.123 for example), but an external client would get an external IP.

    TL;DR: DNS and IP routing are separate concerns and happen at different parts of the TCP/IP stack.


  • AC in the US aren’t (usually) heat pumps. The most common setup here is a furnace for heating (usually natural gas) plus AC, connected to the same central air unit. Heat pumps are pretty common, but not nearly as universal.

    Just mentioning it because “AC” isn’t usually used to refer to heat pumps here.



  • Hopefully you both have discussed getting married and have some plans for the future before popping the question. As part of your plans you may have things like saving up for a home or go traveling. Put your money towards your dreams, not the ring. Make it a nice ring, but not too nice. Do not borrow money for it. Try to figure out what she would like.

    As the father of a woman who will probably marry her boyfriend in the next few years: I think it works be a great gesture if my future son in law asked me. I won’t be mad if he doesn’t, but it shows respect and that he’s thinking of me as family as well. I think it sets a good tone for the relationship.



  • My motivation for calling for it to be the default was that it’s safer (in terms of data).

    Another UX principle is that of least surprise. I think it’s reasonable to assume that most users will expect the copy to be fully complete when the dialog closes, and that they will be surprised when their files are corrupted. Changing the behavior in the desktop to delay closing the dialog until any copying to removable media is complete should not be a controversial change.

    We’re seeing an influx of novice users to Linux. I don’t think we need a bunch “Linux ate my files” incidents if it can be avoided by a simple change, which itself can be easily reversed if you didn’t like it.