Oh, yeah. Sorry. That was in a private thread. But the gist of it was simply to allow the creation of bot access tokens that can be used as credentials to control a bot characters. This would also be used to properly tag bot characters so that other players may know if they are interacting with a bot.
True! Always better with security instead of trust!
What would the URL be that Mucklet should redirect back to?
Back from a little vacation and looking more into this.
So good news is that now android builds are pushed to play store automatically. Bad news is that re-login somehow got very broken. Nothing more exciting than debugging authentication flows!
smh. the mobile doesnāt report reconnect failures on mobile. I spent hours trying to debug it and it doesnāt seem like thereās any reasonable workaround.
Thatās when flutter doesnāt feel fun anymore
Good news though is that I cleaned up the routing and navigation so itās easier to work on other features.
Iām back from a mini-vacation and had some stress testing (or rather, my stress-tester did).
In general the connection stability is better in the app than the website now, although there are times where WS is closed but isnāt reported as such. Iām not quite sold on that to be a the close-wait situation because it just behaves weird (and is iOS only as far as we could repro).
I donāt think any backgrounding is feasible at all on iOS now, and I donāt want to spend time implementing it for Android alone so Iāll skip that bit altogether. IMO itās much neatly solved server side with server-initiated push.
@Accipiter you once told me about that hack where I can use http/rest to get the same things as the res provides. Couldnāt find it in the docs, but can it be used to send things (ctrl.out)? I think thereās a major improvement in message delivery if you POST them instead of relying on the questionable WS semantics (also thatās how discord does things and they sure know how to handle large chats).
There is no way to get events (such as ctrl.out events) using HTTP.
However, it is possible to retrieve chat log events with HTTP directly from the log service.
POST https://api.wolfery.com/api/log/events/get
Body:
{
charId: "YOUR_CHAR_ID",
puppeteerId: "YOUR_PUPPETEER_CHAR_ID", // May be omitted if not using a puppeteer
startTime: 1661336415895 // Unix timestamp in milliseconds
}
Just be aware that the log service only keeps logs for a limited while.
Disclaimer: Above call has not been tested. Should work though, as long as you have an access token in your HTTP headers.
So I finally noticed the app on the Play store, congratulations!
Though I canāt seem to figure out what server address itās looking for to connect with. Iāve tried wolfery.com, api.wolfery.com, wolfery.mucklet.com, api.wolfery.com/api/, mucklet.com, all with and without a leading https:// and wss://, those without protocols all returning a 404 error, and those with explicit protocols giving a Failed host lookup leading me to believe it doesnāt want the protocol.
Is there an issue? Or am I just missing the correct address?
ā¦ okay so whatās the app called? Iām not finding anything related to wolfery, ravenry, mucklet, or anything else I could think of on the Play Store.
Itās ravenry.vfp.in. The idea was to type something so that the play store reviewers couldnāt just land in the station park. The config it looks for just points back at wolfery.
Yeah, you need to email me your playstore/appstore email at ravenry-dogfood@googlegroups.com so I could add it to the list (itās a closed beta so that the app wonāt be randomly accessible on the play store).
Itās an app for the Wolfery, not the forums. Iāve been using it for a couple months, and while it lacks a bunch of stuffs it makes at least the chatting experience much better.