• 0 Posts
  • 193 Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle




  • Nollij@sopuli.xyztoLinux@lemmy.mlThe Mozilla layoffs ... will get worse
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    3
    ·
    7 days ago

    I think you’re massively downplaying how much of a hit this will be.

    Let’s say you make $100k/year. Think about the lifestyle it allows. You’ve just been informed that it’s now going part time, and you’ll only be making $15k/year. How far does that get you?

    Now, you’re expecting someone else to pay for that advertising spot, so it won’t be that bad. But who is even eligible? Microsoft’s Bing is the obvious answer, and probably DDG. The rest of the default search engines aren’t even general web searches.

    Do you really think that either of them are going to pay any significant amount to be the default? Especially when most people are going to change it back to Google anyway, since these are automatically people willing to change to a different browser?

    Sure, they might be willing to pay something. But it won’t be anything close to what they had before.





  • Nollij@sopuli.xyztoPiracy@lemmy.mlAI for torrenting?
    link
    fedilink
    English
    arrow-up
    2
    ·
    18 days ago

    You are comparing it to a hash, following some extra rules on what the data could be. You have exactly the length of hash before you can reliably count on duplicates (and collisions happen much sooner). In torrent v1, this is SHA-1, which has a 160-bit (or 20 byte) hash. Which means for every single additional random bit, you have doubled the number of possible matches.

    If your torrent has an uncommonly small chunk size of 256KiB, that’s 261,144 bytes. Minus the 20 from above, and you have a likely 256^261124 chunks that match your hash. That’s a number so large that Google calls it infinity. It would take you forever just to generate these chunks by brute force, since each would need to be created, then hashed, then the results stored somewhere. Many years ago, I remember someone doing this on CRC32 (32 bits/4 bytes) and 6 byte files. It took all night, and produced dozens of hash-matching files. You’re talking many orders of magnitude bigger.

    But then what? You’d still need to apply the other rules on what the data could be. Rules that are probably more CPU-intensive than the hash algorithm.

    The one trick that AI might be able to use to save the day is that it may contain in its corpus the original file. In effect, that would make the AI an unlikely seeder.








  • Nollij@sopuli.xyztoNews@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    28 days ago

    Many items are already packaged to protect them from damage in transit. If it’s already in a box with Styrofoam inserts, there isn’t as much value on wrapping it again.

    That said, there are countless items at Amazon that are not protected like that. Amazon also won’t pay their employees enough to care, nor give them the time to make any such decisions.