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

help-circle

  • The fingerprinting I’m talking about gets encoded in the screen recording too. Subtle pixel changes here or there over the entire length of the video. It’ll be lossy when it’s transcoded, but over the whole video it’s there enough times it won’t matter. Even scaling to lower quality won’t fix it and then it’ll also be lower quality.

    It’ll be like DRM, there will be people trying to remove it like anything else. They’ll break one thing and another will come along. There would still be a black market, but most people can get an unrestricted copy in exchange for money so there’s one less reason to pirate.

    Unless you’re actually pointing a camera at the screen, then OK, you do you.




  • If you’re an ssshole don’t you come back as an insect or animal? That would mean rich folks would have to do actual good to avoid that. Whatever their policies, after the first few trust fund dung beetles and assorted other multi-lifetime embarrassments, they’d probably snap out of it.

    Hey check out the cockroach yacht club guys! Lol, how did that forced birth + soul tracking debt thing work out for you!?

    Then like half their debtors would achieve nervana and fuck off to heaven or whatever.

    I think the kharma religions, this would take care of itself.







  • Up to date post. https://old.lemmy.world/post/2923697

    Doesn’t give much on who and why, more on what/how along with dispelling some myths.

    Whoever is doing it is very quickly walking through a list of expensive queries to use in their DDoS attacks. Lemmy.world is playing whack-a-mole instead of proactively rate limiting/mitigating expensive queries. It may be that all their time is spent diagnosing and fixing with none left for proactive fixes.

    The fact that the attacks are evolving and always hitting expensive queries implies that it’s a moderately skilled person/group familiar with the lemmy codebase.

    You can speculate on motives as well as I can.

    The net effect will be a more robust server and hopefully that code/knowledge is disseminated to other instances.


  • Your ISP is doing it wrong, which I guess you already know. I get a /64 net via DHCPv6 for my LAN which is pretty standard.

    +1 to dual stack. Too much of the internet is v4 only, missing AAAA, or various other issues. I’ve also had weird issues where a Google/Nest speaker device would fail 50% of the time and other streaming devices act slow/funky. Now I know that means the V6 net is busted and usually I have to manually release/renew. Happens once every few months, but not in a predictable interval.

    Security is different, but not worse IMO. It’s just a firewall and router instead of a NAT being added in. A misconfigured firewall or enabling UPnP is still a bad idea with potentially worse consequences.

    Privacy OTOH is worse. It used to be that each device included a hardware MAC as part of a statelessly generated address. They fixed that on most devices. Still, each device in your house may end up with a long lived (at least as long as your WAN lease time) unique IP that is exposed to whatever sites you visit. So instead of a unique IP per household with IPv4 and NAT, it’s per network device. Tracking sites can differentiate multiple devices in the house across sites.

    This has me thinking I need to investigate more on how often my device IPv6 (or WAN lease subnet) addresses change.