Homebrew [Release] arc13's freeShop fork - open source eShop alternative

  • Thread starter Thread starter arc13
  • Start date Start date
  • Views Views 717,176
  • Replies Replies 2,534
  • Likes Likes 144

What should I do with storage bars ?


  • Total voters
    138
  • Poll closed .
Status
Not open for further replies.
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 final
Someone can always add it and make a pull request. If rejected, then people can download the other person's version instead if they want the feature.
 
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.
Your idea is still a little on shaky ground, basing the layout on that specific titlekey site. An option that may be possible and less risky would be allowing a second URL for an RSS feed of updates, and implement a more general RSS reader functionality.
 
  • Like
Reactions: Quantumcat
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 final
If the average user can put in the URL for that, hack their 3DS, even know how to install this appilication I think they would know how to do this. Plus there could be directions on the site itself.

Also it could be added, like you said freeshop is also for compatibility with other titlekey sites.

--------------------- MERGED ---------------------------

Your idea is still a little on shaky ground, basing the layout on that specific titlekey site. An option that may be possible and less risky would be allowing a second URL for an RSS feed of updates, and implement a more general RSS reader functionality.
I don't really know what you mean, you know it could just have defaults, also the bold part is basically what i'm saying.
 
Either way, I think that it seems doable, and we will have to see what @arc13 thinks.

Actually now that I think about it, you could make the separate db/txt file or whatever that is updated after each title key update and take the delta/difference between what you already have and what's new and then only show x many new titles. It won't give you date but it would still show you what you want. This way you can still use the generic enctitlekeys.
 
Actually now that I think about it, you could make the separate db/txt file or whatever that is updated after each title key update and take the delta/difference between what you already have and what's new and then only show x many new titles. It won't give you date but it would still show you what you want. This way you can still use the generic enctitlekeys.
That would be even better; having it compare the entries from the latest encTitleKeys.bin with the older one to determine newly added titles.
please, stop asking
I never asked anything, I made a suggestion and addressed others' concerns regarding it.
 
Last edited by I pwned U!, , Reason: Addressing some of Dionicio3's big bold letters.
That would be even better; having it compare the entries from the latest encTitleKeys.bin with the older one to determine newly added titles.
Ok, I have suggested the idea in the freeshop beta testing conversation, we will discuss about it, so please, stop asking
 
Last edited by Dionicio3, , Reason: Big, bold letters
If the average user can put in the URL for that, hack their 3DS, even know how to install this appilication I think they would know how to do this. Plus there could be directions on the site itself.

Also it could be added, like you said freeshop is also for compatibility with other titlekey sites.

--------------------- MERGED ---------------------------


I don't really know what you mean, you know it could just have defaults, also the bold part is basically what i'm saying.
Okay, lemme redo that last part.
Your idea is still a little on shaky ground,
1. basing the layout on that specific titlekey site.
2. An option that may be possible and less risky would be allowing a second URL for an RSS feed of updates,
3. and implement a more general RSS reader functionality.
1. freeShop is already based on the layout. Also that's why I said you could change it.
2. That's what I said.
3. I don't even know what RSS is, what makes you think the average user would know what's happening?

--------------------- MERGED ---------------------------

Ok, I have suggested the idea in the freeshop beta testing conversation, we will discuss about it, so please, stop asking
:creep:
 
Okay, lemme redo that last part.

1. freeShop is already based on the layout. Also that's why I said you could change it.
2. That's what I said.
3. I don't even know what RSS is, what makes you think the average user would know what's happening?

--------------------- MERGED ---------------------------


:creep:
1) No, it's not, right now FreeShop takes a URL to a file format dumped by any title key dumper
2) You said build a URL, based on the layout of one current active titlekey site. Not take a second full URL to an RSS feed
3) This was more for the dev, instead of basing it explicitly on the layout of a specific site, implement a generic reader.
 
1) No, it's not, right now FreeShop takes a URL to a file format dumped by any title key dumper
2) You said build a URL, based on the layout of one current active titlekey site. Not take a second full URL to an RSS feed
3) This was more for the dev, instead of basing it explicitly on the layout of a specific site, implement a generic reader.
1. True, but it still wouldn't be based around it.
2. Maybe you need to read my previous posts.
3. If this was for the dev, there'd be no point in putting the work into it for one person just to look at some rss. If it is that important, I'm sure the dev would've done it way before.
 
2. Maybe you need to read my previous posts.
You mean this one, where you said to build the URL based on the layout of the current site?
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.

3. If this was for the dev, there'd be no point in putting the work into it for one person just to look at some rss. If it is that important, I'm sure the dev would've done it way before.
My comment was aimed at the dev, where instead of parsing a specific RSS layout, make a generic RSS parser that just outputs the data in the RSS file in a friendly format...
 
You mean this one, where you said to build the URL based on the layout of the current site?



My comment was aimed at the dev, where instead of parsing a specific RSS layout, make a generic RSS parser that just outputs the data in the RSS file in a friendly format...
If I understand what you're saying, You want Arc to rewrite the title key rss data output? If I understood that right, it would be impossible. Arc doesn't own that site.
 
  • Like
Reactions: Jacklack3
You mean this one, where you said to build the URL based on the layout of the current site?



My comment was aimed at the dev, where instead of parsing a specific RSS layout, make a generic RSS parser that just outputs the data in the RSS file in a friendly format...
No, I mean this one, you know, the one you quoted?
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.

Can't he just use some onlien version? He doesn't have to implement it into the app.

--------------------- MERGED ---------------------------

If I understand what you're saying, You want Arc to rewrite the title key rss data output? If I understood that right, it would be impossible. Arc doesn't own that site.
Also I don't know if this is right but wouldn't it have to be based around that site? Meaning it would contradict was drakia was saying.
 
If I understand what you're saying, You want Arc to rewrite the title key rss data output? If I understood that right, it would be impossible. Arc doesn't own that site.
No, the output for the "recent additions" is an RSS file, a standard file format. I'm saying arc would just process ANY RSS file, and output it in a friendly manner.

The current format is like this:

Code:
<item>
  <title><![CDATA[Home Menu (Themes)]]></title>
  <link>https://<snip>/#0004008c00008205</link>
  <guid isPermaLink="true">https://<snip>/#0004008c00008205</guid>
  <description><![CDATA[0004008c00008205]]></description>
  <content:encoded><![CDATA[<snip>]]></content:encoded>
  <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/"></dc:creator>
  <pubDate>Sun, 05 Feb 2017 10:34:37 +0000</pubDate>
</item>

So, the output could just be a list based on say the <title> tag (Seems generic enough):
Code:
 - Home Menu (Themes)
 - Some Other Title
Or it could output the first tag it finds for each <item>, or it could output all the info, whatever. Just some method of showing it that isn't explicitly linked to that site.
 
No, I mean this one, you know, the one you quoted?


Can't he just use some onlien version? He doesn't have to implement it into the app.

--------------------- MERGED ---------------------------


Also I don't know if this is right but wouldn't it have to be based around that site? Meaning it would contradict was drakia was saying.
I don't think it matters, it would still have the title keys, which would mean it couldn't be hard-coded, as then nintendo could take it down.


No, the output for the "recent additions" is an RSS file, a standard file format. I'm saying arc would just process ANY RSS file, and output it in a friendly manner.

The current format is like this:

Code:
<item>
  <title><![CDATA[Home Menu (Themes)]]></title>
  <link>https://<snip>/#0004008c00008205</link>
  <guid isPermaLink="true">https://<snip>/#0004008c00008205</guid>
  <description><![CDATA[0004008c00008205]]></description>
  <content:encoded><![CDATA[<snip>]]></content:encoded>
  <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/"></dc:creator>
  <pubDate>Sun, 05 Feb 2017 10:34:37 +0000</pubDate>
</item>

So, the output could just be a list based on say the <title> tag (Seems generic enough):
Code:
 - Home Menu (Themes)
 - Some Other Title
Or it could output the first tag it finds for each <item>, or it could output all the info, whatever. Just some method of showing it that isn't explicitly linked to that site.
Sure, that's how it looks now, but if a new title key site pops up, they might not follow that format.
 
Sure, that's how it looks now, but if a new title key site pops up, they might not follow that format.
Oh yeah, it could be completely different, that's why I said go for something generic. First item, something named 'title', or just show it all.
 
Oh yeah, it could be completely different, that's why I said go for something generic. First item, something named 'title', or just show it all.
As I said earlier, Arc does not own that site, nor does he have any intention of making one. (Also, if you just want to see the latest games, couldn't you just...open the freeShop?)
 
  • Like
Reactions: Dionicio3
As I said earlier, Arc does not own that site, nor does he have any intention of making one. (Also, if you just want to see the latest games, couldn't you just...open the freeShop?)
I'm not saying change the site... I'm saying in FreeShop, just implement a generic RSS reader, something that shows just the first entry, or any entry named 'title', or just shows all the info in the RSS entries...
 
  • Like
Reactions: Subötaï
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum