blckbear_
Developer
Dude I never said you mentioned that exploit, I mentioned it because it's just one of the two publicly known exploits for 90k consoles so that was the other available way of automation (for us, the unsuspecting public), if you are talking about some private shit then we obviously don't know about it, so don't act as if we should lmao.Yeah........ As far as YOU know....... You don't know what there is and what isn't!
Yes, because there is nothing else released or being worked on. That doesn't mean that there isn't a vulnerability, which can be exploited...!
...and we are actually talking (in a closed section) about multiple ideas like the history.id-stuff possibly being vulnerable and exploitable.
Did I mention or talk about that exploit??? No...
There are MULTIPLE possible entries which we are talking/writing about in a closed section...
history.id and history.old being one/two of them...
How the hell are we supposed to know about what you talk privately, and how does saying "Oh you don't know....... maybe there's something in the works.... you don't know about it yet...... maybe there will be something....." help lmao.
@kronosx had a question and we answered with what we all publicly know, and as I said before, if you have any solution/suggestion, then say it, if not, what the hell is the point of "teasing" with unreleased, theoretical, private exploits lmao. We gave solutions with the tools available and that's it.
It was already made clear that OpenTuna needs an entry point, and that it made through the browser menu (for now, because, you know, we're the dumb public, the ones who apparently "know nothing" lmao), there are no others available for our use, so again, what's your point?/suggestion?
It's obvious that any new development is completely welcome, but when there is none in public sight, we (the public) solve the problems with the other tools available. When and if the new super private entry points (assuming that's what you're suggesting is being worked on among other things) become public, then yeah, we can do what @kronosx wants to achieve in ways other than the already suggested ones.
BTW I'm done with this, bye