- Joined
- Feb 26, 2017
- Messages
- 4,004
- Trophies
- 2
- Age
- 19
- Location
- Hollister, CA
- Website
- dionicio3.com
- XP
- 6,029
- Country
-
But how would the database update?On the SD card somewhere in the freeShop directory.
But how would the database update?On the SD card somewhere in the freeShop directory.
Something along the lines of connecting to the title key site and using adding new date and time information for titles from the RSS feed.But how would the database update?
But once again, that would need a direct link, and not everyone using the titlekey siteSomething along the lines of connecting to the title key site and using adding new date and time information for titles from the RSS feed.
What @Dionicio3 is saying, is that FreeShop is not designed around one specific titlekey website. It is designed to use ANY enctitlekey file, and adding features that are purely based on how one specific site behaves is going to limit things such as people hosting their own legitimate backups of their title keys.Something along the lines of connecting to the title key site and using adding new date and time information for titles from the RSS feed.
But once again, that would need a direct link, and not everyone using the titlekey site
The solution would be forcing the option to be disabled until the user links freeShop to the title key site.What @Dionicio3 is saying, is that FreeShop is not designed around one specific titlekey website. It is designed to use ANY enctitlekey file, and adding features that are purely based on how one specific site behaves is going to limit things such as people hosting their own legitimate backups of their title keys.
This is something I know atleast the original author was against, as it spoils the "Not explicitly designed for piracy" argument.
Thank you for the explanationWhat @Dionicio3 is saying, is that FreeShop is not designed around one specific titlekey website. It is designed to use ANY enctitlekey file, and adding features that are purely based on how one specific site behaves is going to limit things such as people hosting their own legitimate backups of their title keys.
This is something I know atleast the original author was against, as it spoils the "Not explicitly designed for piracy" argument.
That is a horrible solution, because somewhere in the code, there will be a sting that has the titlekey's site's nameThe solution would be forcing the option to disabled until the user links freeShop to the title key site.
can't you make it so it would set a variable and then merge it with the text.That would be impossible without having direct links to the titlekey site (which is not allowed)
can't you make it so it would set a variable and then merge it with the text.
So let's sat the website is omfgdogs.com, well that would be the {site} variable. We could do {site}/recent/index.html or something.
That is a horrible solution, because somewhere in the code, there will be a sting that has the titlekey's site's name
Again, not an option if you want to avoid takedowns or people claiming you're outright supporting illegal titlekeys. There's a difference between compatibility and coding for a specific source.The solution would be forcing the option to be disabled until the user links freeShop to the title key site.
Sorry then, I just find it funny that posting one line of address for host file could harm the site.
But that's how it is when pirates don't have its own ship.
It probably wouldn't, but they seem to think that by disallowing the posting of names or links they can appear to be against piracy(even though they clearly have forum sections dedicated to backup loading and hacking). It seems pretty hypocritical but they're doing whatever they can to keep the site up and if they think doing that'll help, I'm not going to complain.
Yeah, but not every titlekey site have the same file structureI don't think you understood. When you put in the URL, it would set the variable (let's say) {site} to that url. Then if it needs a certain webpage, it would merge the variable with the rest of the text.
I can understand that. Either way, it is up to @arc13 to decide.Again, not an option if you want to avoid takedowns or people claiming you're outright supporting illegal titlekeys. There's a difference between compatibility and coding for a specific source.
but that's not freeshops fault, that's the hosts.Yeah, but not every titlekey site have the same file structer
I already know he is not gonna add thisI can understand that. Either way, it is up to @arc13 to decide.
Ok, this is what I mean:but that's not freeshops fault, that's the hosts.
Maybe in the box where you put the URL there could be advanced options, then it would ask for directorys of files and such. Then on example.com they'd say what options to put.Ok, this is what I mean:
Lets say the titlekey site is example.com. Now lets say someone is hosting there own titlekeys (for their family/friends) on example2.com
titlekey's rss site would be something like example.com/rss.rss, but example2's is example2.com/files/rss.rss. There is no way to tell where it would be, so everyone, stop asking
Unless an option is added to specify the URL for the RSS feed, in which case example2 would just specify the URL as example2.com/files/rss.rss.Ok, this is what I mean:
Lets say the titlekey site is example.com. Now lets say someone is hosting there own titlekeys (for their family/friends) on example2.com
titlekey's rss site would be something like example.com/rss.rss, but example2's is example2.com/files/rss.rss. There is no way to tell where it would be, so everyone, stop asking
Yeah, but the average user would not how to do that, anyways, why are we arguing? I know he is not gonna add it and that's finalMaybe in the box where you put the URL there could be advanced options, then it would ask for directorys of files and such. Then on example.com they'd say what options to put.
