• 1 Post
  • 75 Comments
Joined 2 年前
cake
Cake day: 2023年6月20日

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.













  • You can’t build a box that will survive long without your help. You’re maintaining a living system, not a sculpture. It needs someone at the wheel making decisions. Updates will have breaking changes. Tokens and certificates will expire. Eventually hardware will fail.

    The best you can do is provide an easy way to export the important data into a digestible format for your loved ones to manage with the skills they have. If that means pushing it into a managed service owned by Big Tech, so be it. You don’t want to tacitly hurt them for their lack of interest in self-hosting.