• 0 Posts
  • 45 Comments
Joined 3 years ago
cake
Cake day: August 2nd, 2023

help-circle






  • Back in the BERT days I had a physics major friend that stuffed a bunch of Norwegian names in a file and trained a Norwegian name generator. He also made a Moby Dick sentence generator for funsies.

    PewDiePie’s project is nothing different than a personal pet project like these cases. Nothing about being a YouTuber makes you an expert at machine learning. It should be treated the same way as any other pet project.

    If the concern is someone with large amounts of influence causing disproportionate harm with their personal projects by name alone, at least in this particular case, I feel it’s appropriate to blame someone who trusts a YouTuber’s pet project in the first place.





  • I’ve been lurking in various watch-related forums right before this release, and all the drama leading up to this has been hilarious:

    FYI: this “watch” is a collab between a brand (swatch) that makes <$100 disposable watches (the watch movement is sealed such that you can’t repair/maintain it) and a brand (AP) that makes $30k watches with a long waiting list. The collab was announced first, then the specs of the watch, then the actual watch itself (being on a keychain?). Each round of announcements led to a new wave of drama.

    1. There are people mad that this collab devalues their $30k watch brand
    2. There are people mad that the watch is an exact plastic replica of their $30k AP Royal Oak
    3. There are people mad that the collab watch doesn’t come on a strap, but is instead a glorified keychain
    4. There are people mad that said keychain comes at a price of $400, is plastic, and cannot be maintained (mechanical watches need regular maintenance, this plastic piece is destined for the trash in 4-5 years)
    5. There are people mad about the colors
    6. There are people mad that said colors devalue their $30k watch
    7. There are scalpers selling the watch on eBay before the watch was released for $3k
    8. There are strap makers making 3D printed straps for the thing as soon as the watch was announced, at the price point of the watch itself ($400)
    9. The release event almost entirely consisted of scalpers. Every reasonable watch person thinks it’s overpriced garbage
    10. This is NOT a limited release watch. These plastic watches will fill the oceans for years to come
    11. Swatch had to close stores due to public safety issues with these scalpers
    12. There are scalpers that stole a “sorry were closed today” paper sign from a swatch store and selling it on eBay

    The best part: nobody is actually interested in the watch. It’s almost all scalpers and people owning a $30k watch having a meltdown.

    Edit: if you are looking for a <$400 mechanical watch that is worth the money, I recommend the Seiko 5 or Orient Bambino instead of this plastic toy. Learn to regulate and maintain it by yourself, it’s easier than it looks. My Max Bill runs at a rate of +0.5s per day after regulation. Watching a fully mechanical minute hand sweep (as well as the date flicking over instantly at midnight) is such a joy.




    1. If your assumption is that X509 is trash, does that mean you hold the same amount of distrust to TLS?
    2. How do you propose the scaling of key management? Do you have a reasonable alternative to users blindly trusting every single key they come across?
    3. Back to my original question: what prevents a VSCode extension from stealing a private signing key (as opposed to an API key) and causing the same issues described here?

  • And how would apt help in this particular case? A supply chain attack can happen with any particular package manager. In this case, the compromised package was detected and mitigated within 93 minutes, affecting a total of ~330 users. Which is a lot better than how a lot of distros handled the xz breach last year.

    All reasonably secure package managers (and https) operate on a chain of trust. There is little that can be done if that chain of trust is broken.

    Based on this the cause was a malicious VSCode extension that stole credentials that were later used to trigger a deployment CI/CD pipeline. If there’s anything to learn from this, it’s probably to not use VSCode.