Clean up unavailable songs about torrenttunes-client HOT 8 CLOSED

Does this mean I have to add my music again every time I start torrenttunes? Or is it a one time thing for the update only?

Also, storing IPs doesn't seem like a good idea from a privacy perspective. And what if multiple people are seeding the same song?

from torrenttunes-client.

Not every time. Its a one time thing for this upcoming update. I've written most of the code and will probably be making the change within the next day or two, so people(me included) will have to click the clear clear database button, and rescan their libraries.

Also, storing IPs doesn't seem like a good idea from a privacy perspective.

I just did some thinking about this, and you're right. But I still need a way to uniquely link an uploader's computer to the songs they've chosen to share though.

I think I'm going to go with the uploader's MAC Address. That'd uniquely identify the uploader, without compromising their network location.

And what if multiple people are seeding the same song?

That's not an issue here; The original uploader is the person who creates the .torrent file, no one else can, because song's are unique. When another person clicks play, they're just grabbing the torrent file that the original uploader made.

from torrenttunes-client.

Looks like I can't get mac address, because that requires root..

from torrenttunes-client.

Thought of a way to do this. I'll hash the IP address with the users home directory location string(which I cannot know). This will make a unique computer identifier that could be stored on the server, that couldn't be decoded. I'll call the column IP_HASH

from torrenttunes-client.

This cleanup should be done by tomorrow morning.

from torrenttunes-client.

This feature is only for admins info? Respectfully I think that ip hash could be dangerous to the uploaders, could compromise their work...

from torrenttunes-client.

Another question, if user use VPN, how the app resolve the presence of two or more IPs?

from torrenttunes-client.

This will make a unique computer identifier that could be stored on the server, that couldn't be decoded. I'll call the column IP_HASH

I can't decode that column, its an anonymous unique identifier for an uploader though. Read above for why this is necessary.

If you use a VPN, it should still be fine, because the hash is made from a combination of the IP address and the user.home Dir. As long as two computers aren't using the same VPN with the same user name, they should be unique.

Even if some peoples ips change, I should still at least have groups of uploads, that I can view their timeout counts and remove their songs if necessary.

Here's the function for future reference:

https://github.com/tchoulihan/torrenttunes-client/blob/master/src/main/java/com/torrenttunes/client/tools/Tools.java#L978

from torrenttunes-client.