I’ll admit, when I first started torrent I was not really familiar with how it worked and how important seeding was. I would just use magnet links without configuration to save the torrent and seed after completion. Well… I have finally, got myself back to 1.00 after a couple months and working to try to always seed double what I get for each torrent.

Often times I was one of the few random seeders available for some of these torrents. Friendly reminder to give back because you never know when you’re one of the rare cases that can complete someones long lost file download!

  • RejZoR@lemmy.mlEnglish
    3·
    4 days ago

    Problem is how most networks are configured today that prevent HighID on eMule, severely crippling it. It used to be annoying to have LowID in the past and reconnecting usually fixes it, now it’s a given and you can’t get out of it. It’s so hard to get uploads going and it makes me sad :(

    • supervent@lemmy.dbzer0.comEnglish
      2·
      4 days ago

      The problem with HighID/LowID on eMule is the same on bittorrent or any other p2p, you need someone with port forwarding to upload/download content. In my case I am out of cg-nat and sharing 24/7.

      • RejZoR@lemmy.mlEnglish
        1·
        4 days ago

        It’s not. Bittorrent uses newer methods to connect that work with current network configurations where eMule devs stubbornly refused because it would create some overhead like we’re still stuck on 56k or ISDN era and never improved it.

        Apparently there is a way using VPN with P2P, but I’m not gonna pay for it just to run eMule…

        • supervent@lemmy.dbzer0.comEnglish
          3·
          4 days ago

          Nope, it is the same. Bittorrent have a lot more users than eMule and then you have more possibilities to find a peer with ports forwarded. 2 peers Without port forwarded can not share content.

          • RejZoR@lemmy.mlEnglish
            1·
            4 days ago

            I have ports forwarded locally to deal with my router, that doesn’t apply to my ISP down the line. And that’s the problem. I don’t know the specifics, but that’s how it was explained to me.

            • MEtrINeS@lemmy.dbzer0.comEnglish
              1·
              3 days ago

              I have ports forwarded locally to deal with my router, that doesn’t apply to my ISP down the line.

              So you are under CGNAT: https://en.wikipedia.org/wiki/Carrier-grade_NAT

              From the wikipedia link:

              Carrier-grade NAT usually prevents the ISP customers from using port forwarding, because the network address translation (NAT) is usually implemented by mapping ports of the NAT devices in the network to other ports in the external interface. This is done so the router will be able to map the responses to the correct device; in carrier-grade NAT networks, even though the router at the consumer end might be configured for port forwarding, the “master router” of the ISP, which runs the CGN, will block this port forwarding because the actual port would not be the port configured by the consumer.[7] In order to overcome the former disadvantage, the Port Control Protocol (PCP) has been standardized in the RFC 6887.

              You will only be able to upload to someone with a public ip address or with UDP hole punch (but there are some technicalities - and doesn’t work in all the cases). The same will happen if you use torrents. Maybe you don’t notice difference because of the sheer amount of people using seedboxes and vpn.