• 94 Posts
  • 866 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle


  • Great comment!

    There’s similar legal issues with the “right to a private copy” many European countries have. Those laws were made to allow people to make a copy of their media, in case the original breaks. Important to note is that those private copies weren’t allowed to be distributed to anyone, not even lent to a friend.

    This worked well at the time for cassettes and VHS, which did break occasionally.

    But at some point most CDs came with copy protection, which got broken pretty quickly. But at least in Germany, they are still considered “working copy protection” and thus are illegal to circumvent, even for a otherwise legal private copy.

    The same is the case with Switch games: Copyright owners use copy protection to make otherwise legal use cases illegal.

    E.g. Nintendo made it so that Switch games can only be played by decrypting the ROMs, which is illegal for anyone except Nintendo.

    At least that’s their standpoint which was never tested in court but it’s not unlikely that it’d be accepted.





  • Chewy@discuss.tchncs.detoLinux@lemmy.mlImmutable Distro Opinions
    link
    fedilink
    arrow-up
    12
    arrow-down
    2
    ·
    edit-2
    17 days ago

    NixOS is immutable and atomic, but it isn’t image-based.

    Immutable simply refers to how the running system configuration can’t be changed by simply putting a file somewhere (e.g. copy a binary to /bin, which is a bad idea).

    For example, Fedora Atomic and derivatives are image based, although they are more flexible than the A/B types like SteamOS.

    OpenSUSE MicroOS uses btrfs snapshots to apply updates atomically, and is more flexible than most image based immutable distros.

    Edit: But I don’t think those terms have a single definition, so how would you differentiate these terms?






  • It depends on what trackers you’re on and how much storage you have, and how risk averse you are.

    First of all, binding your torrent client to the VPN interface should prevent all leakage.

    Additional precautions like running your torrent client behind a container like gluetun should make it pretty much impossible to leak your IP to adversaries. Or if you have a plain Linux server, running the torrent client in it’s own network namespace also achieves the same result.

    The other big reason to get a seedbox is to be able to maintain your ratio. This depends on your tracker.

    E.g. I have enough storage for a large enough seeding size and enought torrents to get sufficient bonus points. Combined with a bit of upload here and there, I get enough upload/buffer to snatch what I want.

    On many trackers, large enough torrents are often freeleech, so they don’t count towards the download stat anyway.

    tl;dr

    If you bound your torrent client to the VPN, I’d seed with your NAS unless you don’t get enough upload to maintain your ratio on your specific private trackers. Storage is way cheaper on your NAS.


  • Semi-private just refers to how easy it is to join them. E.g. rutracker is considered a semi-private tracker, because it requires an account, but always allows registrations and does not enforce any ratio.

    In that sense I was wrong in calling TL a semi-private tracker, because TL does require maintaining a ratio. But given it is possible to simply join via their seedbox offerings, it is not as private as some other trackers, which require proofs of good behaviour on other trackers and/or an application process.

    Edit: Public: no registration required
    Semi-private: registration required, but always possible; lax ratio rules
    Private: registration required, mostly through invites/applications; anti-leech ratio rules



  • Semi-private trackers like TorrentLeech are a great step up from public trackers and they are relatively easy to join (e.g. seedbox promo). More content is available and well-seeded for longer periods of time.

    It’s not difficult to keep your ratio, even with a 50MBit/s connection (torrents > 15GB are freeleech anyway), as long as you seed 24/7. Or buy a seedbox for a while, build a few TB of buffer (autobrr) and never worry again.

    Edit: Usenet is great because it’s fast, and depending on your (non-english) language, it’s a completely different league than public trackers. But I’d argue for english content TL (and a few others) is good enough.


  • With I2P each user is a node/router, so it does not rely on central nodes like Tor.

    The only issue is it’s slow, because most users don’t allocate/have much bandwidth. Because of it’s garlic routing (similar to Tor’s onion routing) traffic is encrypted multiple times with multiple hops which also impacts throughput and latency.

    The good thing is it’s already suppported by qBittorrent (and BiglyBT), but setting it up is a manual process.

    Also, qBittorrent doesn’t support DHT over I2P yet, so it’s necessary to use an i2p tracker like tracker2.postman.i2p.

    But that would be pretty easy to squash, wouldn’t it? I mean a network only set up for piracy, it will get it’s main operators taken down pretty fast.

    As long as there’s reasonable doubt that i2p is only used for piracy, it shouldn’t get blocked. Similarly, Tor isn’t only used for trading drugs, so it mustn’t get blocked by democracies.



  • Yes, ~/.local/share/flatpak includes all user installed flatpaks, while /var/lib/flatpak includes all system wide installed flatpaks. Both include repository information and required runtimes (i.e. dependencies).

    This does not include user data, which is stored in ~/.var/app.

    Make sure to test your backup just in case on another system/VM.