Service Tokens in 3rd party Miiverse applications

[undone compass]

Okay, so I did ask this in #pretendo, however it got buried, so I'll ask it here. Sorry in advance if I shouldn't, I checked the FAQ and didn't see anything against this.

I am making a Miiverse frontend for Android, and I would like to support the use of Juxt with it. One of my big things to implement is service tokens, and I found this project (https://github.com/MatthewL246/Miiverse-PC) on Github that might serve as a good example to implement them, however I'm wondering if the methods it uses are subject to change or if it's mostly set in stone at this point.

So, ig the TL;DR: Is this a good example of how to implement service tokens in my app, or no?

[placid rune]

why tag account issue

[undone compass]

Because it has to do with service tokens, which are an account thing afaik

#1067162922989662360 Isn't exactly structured for inquiry things like this, so I just roughed it

[near yacht]

I took a quick glance at this project, and it looks like it just mimics the same requests the console uses. These likely wont ever change, but it is technically unintended usage. Not that we really care all that much rn

To be clear when I say "likely won't ever change", what I mean is that the actual endpoints will never changed, since the console needs them to login, but the protections we have on those endpoints are subject to change. Right now we don't really care who accesses those endpoints, but that may change at any time if there are issues

[undone compass]

I want my app to be as faithful to a console Miiverse client as possible, so... Aight.

[undone compass]

That's what I was wondering

[near yacht]

So long as you pass the right data to the endpoint then it will Just Work

[wild kindle]

Those endpoints check for a console certificate, so I'm not sure if they are usable like that for a third-party project

[near yacht]

But that project as-is won't work from what I can see

[fiery copper]

You maybe should create an API for 3rd parties wanting to use one or multiple pretendo network functions

[undone compass]

Cause rn I have it directly accessing the API and parsing the returning XMLs

[undone compass]

Miiverse had an API fwiw

[near yacht]

ye you ninja'd me on that :P That's what I meant by the message right after yours

[near yacht]

We plan to have an entire integration and app system eventually it's just very low on the priority list

[undone compass]

Yeah I might have to require users to provide their own console certs at some point

[near yacht]

We have. Many. Plans

[undone compass]

At least, based on what the Miiverse revival I'm currently using does (NoNameVerse)

.

So, from what I gather, to support Juxt, a user will need to have their console cert?

(Which is the same one dumped for use in Cemu?)

[fiery copper]

Yeah, since pretendo network security is like nintendos

[undone compass]

Ok

[fiery copper]

Its the same problem as the cemu one

To connect to juxt you need a whitelisted console cert which you can extract from a whitelisted wii u

[undone compass]

Yeah, I know about the whitelisting and I'm not gonna mess with trying to bypass it (nor can I, really)

The user is only gonna be able to do what they can can usually do from their Wii U console, maybe with some minor QoL things like downloading paintings/screenshots

[fiery copper]

Its securely implemented server side so you cant

[undone compass]

(nor can I, really)

[fiery copper]

Oh yeah i replied too early

[near yacht]

The whitelist only applies to the 3DS now, we don't have a whitelist for the WiiU anymore. Server access is entirely dictated by the PNID in those cases. We store the console details separately to be used for bans and some cert checks just to make sure the cert hasn't been tampered with, but not for a whitelist

The issue with Cemu is that the applet itself has a URL whitelist, and Cemu has a half-baked olv implementation atm

I've gotten Cemu to load Juxt just fine, however, by switching to Tiramisu and using Martini to hard-patch the applet and the olv RPL, then dumping my entire MLC and letting Cemu use that

[undone compass]

Ok

[near yacht]

#announcements message

[undone compass]

Common Linux W

[fiery copper]

So in other words juxt for cemu is held together by tape

[near yacht]

Nah Cemu is really solid, it's just that olv support is a really low priority most likely. It's not required for 99% of games to function, and Miiverse is officially shut down so there's not a massive need to implement it. Exzap has implemented a good amount to get some demo stuff running but by "half baked" I don't mean bad, I just mean literally only a small part of it is implemented

That's why I needed to use the patched applet and RPL, since Cemu will use the RPL instead of it's own implementation in those cases

[fiery copper]

At least cemu is solid, not like citra

[glass brook]

is this still required to get Juxt working on Cemu? I only followed half that.

[glass brook]

well, now I know what the RPL jargon was about after I got the home menu working in Cemu, but Miiverse crashes in Cemu. I don't know if that's just because Cemu broke the crap out of it in an update or if its because it isn't patched for Juxt. Incidentally, I can't patch miiverse with Martini in Tiramisu. It just returns an error. Error Code: 678-1008