Re: [RELEASE] EARN YOUR RELEASE
Posted: Thu Jul 26, 2018 2:08 pm
can anyone tell me how i can get the file ? do i need to make a mega account ? and if so how would i find it afterwards. thanks in advance
not sure what was offensive, but here are an attempt to get the vid out there again on meganz (fingers crossed)book_guy wrote: Sun Jul 15, 2018 9:28 pm Glad to see the file is available again.
May I suggest, someone might upload it to Mega, changing whatever is necessary such that it will no longer offend those who might previously have been. Once it's available on Mega let me know the link, I'll transfer and re-share the improved version. I would try to upload, but, as I've mentioned elsewhere (see link in .sig) I don't always have reliable uploading time or connection.
Yes, this is an intelligent way to minimize space while helping sharing, and that's how I understand Mega would work, too. But if a first someone puts up a file, then a second someone else "gets" that file, then the first person takes that file down, the file SHOULD remain on Mega because the second person still wants it. As long as the file is "copied" to the second person's Mega cloud, rather than merely "shared" there, the file shouldn't be removed. This was the case, as far as I know, yet the file got removed anyway. In other words, abstractly speaking, Mega pro-actively propagated a removal task to all locations where a file might have been secured, rather than merely re-actively removing an original file that had been linked to a variety of locations. So to speak.wellrested wrote: Fri Jul 27, 2018 1:37 pm Not sure if it helps, but I understand someone like Mega will only store one copy of a file. If two files are exactly the same then they save space by keeping just one copy. However if one file gets taken down then actually all copies of that file are taken down. I've seen some people zip up their file and add a random text file into it to make their file different to avoid this.
I'm vague on the details though
Most likely, each account has a pointer to where the file is stored. As long as at least one person has a pointer to the file, they keep it around. When you delete the file in your account, you just delete your pointer to it. But when they get a takedown notice, they just delete the file, making all pointers invalid. Maybe that’s what you meant to indicate, but that would at least be a sensible way to run that kind of system. So they wouldn’t need to propagate really, other than removing the invalid pointer, which would probably be handled as part of regular automation anyway. I don’t work at Mega, obviously, so I don’t know that that’s how they do it, but I do have close to two decades of experience as a software engineer and I have built similar systems in the past, so I think I at least partially know what I’m talking about. :)book_guy wrote: Sun Jul 29, 2018 12:36 amYes, this is an intelligent way to minimize space while helping sharing, and that’s how I understand Mega would work, too. But if a first someone puts up a file, then a second someone else “gets” that file, then the first person takes that file down, the file SHOULD remain on Mega because the second person still wants it. As long as the file is “copied” to the second person’s Mega cloud, rather than merely “shared” there, the file shouldn’t be removed. This was the case, as far as I know, yet the file got removed anyway. In other words, abstractly speaking, Mega pro-actively propagated a removal task to all locations where a file might have been secured, rather than merely re-actively removing an original file that had been linked to a variety of locations. So to speak.wellrested wrote: Fri Jul 27, 2018 1:37 pm Not sure if it helps, but I understand someone like Mega will only store one copy of a file. If two files are exactly the same then they save space by keeping just one copy. However if one file gets taken down then actually all copies of that file are taken down. I’ve seen some people zip up their file and add a random text file into it to make their file different to avoid this.
I’m vague on the details though
That is my understanding too - if mega gets a takedown request that is asking it to remove the file from mega, not remove the file from a single user of mega.3xTripleXXX wrote: Sun Jul 29, 2018 1:01 amMost likely, each account has a pointer to where the file is stored. As long as at least one person has a pointer to the file, they keep it around. When you delete the file in your account, you just delete your pointer to it. But when they get a takedown notice, they just delete the file, making all pointers invalid. Maybe that’s what you meant to indicate, but that would at least be a sensible way to run that kind of system. So they wouldn’t need to propagate really, other than removing the invalid pointer, which would probably be handled as part of regular automation anyway. I don’t work at Mega, obviously, so I don’t know that that’s how they do it, but I do have close to two decades of experience as a software engineer and I have built similar systems in the past, so I think I at least partially know what I’m talking about. :)book_guy wrote: Sun Jul 29, 2018 12:36 amYes, this is an intelligent way to minimize space while helping sharing, and that’s how I understand Mega would work, too. But if a first someone puts up a file, then a second someone else “gets” that file, then the first person takes that file down, the file SHOULD remain on Mega because the second person still wants it. As long as the file is “copied” to the second person’s Mega cloud, rather than merely “shared” there, the file shouldn’t be removed. This was the case, as far as I know, yet the file got removed anyway. In other words, abstractly speaking, Mega pro-actively propagated a removal task to all locations where a file might have been secured, rather than merely re-actively removing an original file that had been linked to a variety of locations. So to speak.wellrested wrote: Fri Jul 27, 2018 1:37 pm Not sure if it helps, but I understand someone like Mega will only store one copy of a file. If two files are exactly the same then they save space by keeping just one copy. However if one file gets taken down then actually all copies of that file are taken down. I’ve seen some people zip up their file and add a random text file into it to make their file different to avoid this.
I’m vague on the details though
Thank you for your kind words.smargerbarg wrote: Sun Dec 16, 2018 6:41 pm Will you be making a second version of this? Absolutely the best cock hero made!!
I really do hope that you will be able to finish “Earn your Release 2” it looks to be even greater than the first! I wish I could help in some way, if there is any way I may be of assistance please let me know!!Thank you for your kind words.
Sadly not. I have burried the project "Earn your Release 2" two months ago. I've had a very detailed concept for a 12 round (100min) monster and prepared all the footage, but it was simply too much work for me alone. I tried to find help but without luck.