Cheevos Integration Into ES vs RA?
-
A question for @meleu , probably.
Is there any way to work the cheevos login into ES with a better gui (maybe account selection with memorized passwords) for faster account switching for multiple users as opposed to the... not so user friendly RA way of entering it? Just a thought. As purely a user and the coding for RA/ES being far above my ability I have no idea how difficult/easy this would be. I assume it would be a huge undertaking, but I also know your love for Cheevos haha.
Maybe something for @fluffypillow to consider in his Pegasus build down the line?
Anyway, thanks for y'all's work.
-
@hooperre I'm afraid it's not going to happen on EmulationStation. Look what I said in this post here and the main RetroPie developer answered below.
I already thought to code something like what you want using bash (which would look like those dialogs in RetroPie-Setup), but I didn't see many users interested on it... Maybe we can use this topic (or create a new one) to gauge interest and then I can try to code something.
Keep in mind that it wouldn't be as beautiful as EmulationStation, but has that look'n'feel like RetroPie-Setup dialog boxes...
EDIT: I would love to see this on @fluffypillow 's frontend. :-)
-
@hooperre Sure, it wouldn't be too difficult, in fact someone also requested a similar feature (if by cheevos integration you mean RetroArchievements; correct me if that's wrong!).
The only problems I see are the actual input of the user/pass, for which an on-screen keyboard would be nice, the secure storage of the login information and mapping the games to their RetroArchievement game ID, for which I've proposed doing that during scraping. None of these are unsolvable problems :)
-
@fluffypillow I think a credentials possibility like Wifi without keyboard for ES is also a good way to go. Maybe it's time for a virtual keyboard, too ;)
-
@fluffypillow said in Cheevos Integration Into ES vs RA?:
secure storage of the login information
Unfortunately security doesn't seem to be a priority when it comes to RetroAchievements. FYI:
- RetroAchievements.org PHP requests happen completely unencrypted via HTTP (no HTTPS).
- RetroArch talks to RetroAchievements server via HTTP GET method, and some sensitive data (login/password) are in the URL (which can be cached by a router/proxy or something). I think using POST would be a little safer.
- The account info (login/password) is stored in
retroarch.cfg
as plain text. - The account info on RGUI and XMB RetroArch menu is completely unmasked. Like in this screenshot:
What I mean is that maybe masking the password while typing it can be enough. ;-)
-
@cyperghost not sure what you are suggesting, but using the current method (manually edit the
retroarch.cfg
) seems to be simpler. :-) -
@meleu Haha, oh well, I guess plain text will do fine first then :)
-
@meleu As you see I'm a
cheevos-noob
;)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.