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

help-circle
  • Dissenting opinion - You don’t need to change your payment method, but you might want to rent a box outside your country.

    The seedbox provider is providing you sufficient cover. They’re the ones who would have to make the link between the IP you’re using and you. That’s unlikely to happen because they’ve protected themselves.


    A copyright owner (or their agent) that is interested in identifying you from your seeding would send a letter to the data center owner (OVH, Hetzner, etc) saying “Hey, one of your IPs is infringing our copyright! Tell them to stop.”

    The data center owner might forward that letter on to the seedbox provider who is renting space in their data center. Either way, the letter will be ignored and everyone goes on with their day.

    If the copyright owner is sufficiently motivated they can press the issue with some lawyers. Then the data center will provide a name, to make it all someone else’s problem. They don’t have your name though, just the seedbox provider’s, and the seedbox provider is smartly incorporated in another country, which makes litigation complicated (to say the least).

    Now, maybe the copyright owner is a cabal of publishers looking to make a point and have buckets of money to spend. (You did say you wanted to mirror Anna’s Archive.) In that case they’ll work with local law enforcement in the jurisdiction that the seedbox provider is incorporated to go after them there.

    That court case will take some years to resolve, but then your involvement will come down to whether the seedbox provider kept logs associating payers and IPs. They might or might not. If they didn’t, you’re just one person in a big pool of customers.

    If they do have logs associating you specifically to that IP at the time you were infringing the copyright… well, who’s to say your credit card wasn’t stolen?




  • On the topic of build times, it took me too long to learn that nixos-rebuild supports remote build workers and targets.

    For example, if I am editing on my laptop, want to build on my desktop, and apply the build to my file server, then I’d run…

    me@laptop$ nixos-rebuild test \
    --flake ~/wherever-it-lives \
    --build-host desktop \
    --target-host file-server \
    --use-remote-sudo
    

    The host names should match the name of the nixosConfiguration output from your flake. If they don’t I think you can specify like, --target-host .#some-machine

    Remote sudo avoids having to SSH as root.

    Bonus tip: Having Tailscale on every machine makes this work reliably from anywhere, network speed as the limit.














  • Thank you for calling that out. I’m well aware, but appreciate your cautioning.

    I’ve seen hallucinations from LLMs at home and at work (where I’ve literally had them transcribe dates like this). They’re still absolutely worth it for their ability to handle unstructured data and the speed of iteration you get – whether they “understand” the task or not.

    I know to check my (its) work when it matters, and I can add guard rails and selectively make parts of the process more robust later if need be.



  • I’d ask why they don’t make it optional (I’m not a Brave user) but it seems it was.

    Another issue is that Strict mode is used by roughly 0.5% of Brave’s users, with the rest using the default setting, which is the Standard mode.

    This low percentage actually makes these users more vulnerable to fingerprinting despite them using the more aggressive blocker, because they constitute a discernible subset of users standing out from the rest.

    Given that, I’m inclined to agree with the decision to remove it. Pick your battles and live to fight another day.