Not working. It keeps telling me I have failed to register the device and I cannot seem to go back to the code page to re-hit the key code.
Failed to register device. The link has expired or already been used....
Indeed. So you need to repeat the process and complete it before it times out.
If you use the Aegis authenticator (I think mentioned previously by Tricky) it lets you scan the QR code from a screenshot.
I changed my phone this morning, so have tried logging in on my new phone. Was all going well, then it said my email could not be registered. So I deleted both the old and new TalkBack instances off my authenticator, came back here to try reregistering and it just gave up and let me log in.
So I've undeleted the new authenticator TalkBack think off my authenticator thing and I'm hoping for the best.
Turdle was working through the whole downtime. It's continued existence swung my mindset from "tricky's had enough" to "tricky's ficked up".
(I know, tricky will say he hasn't fucked up, that it was all unavoidable. And we'll all agree. Nod nod wink wink.)
That's actually giving me 403 Forbidden, ignore what I said earlier.
Oi, I've been very clear that I'm all about the Cup this year. We have a legitimate shot at winning it and doing so wouldn't weaken our League aims, so it's the right time to go for it.
That's because you are not authenticated. Turdle kept working for you because it was cached in your browser (it only uses front end code). Now the backend is up, the browser tries to update, and because you are unauthenticated the request to the server is rejected.
Note to all. Even if things appear to work in the short term (because of a still valid session token in your browser cache), they will fall when the token expires, and you will have to re-register an authenticator to log back in.
I have managed to get this laptop working but not the mobile which is maddening. The laptop is on chrome. The phone is on safari. I may just become a massive mardy webmong as I cannot really understand why the authenticator did work for both and now only works for one now.
I am not exactly sure how the fuck this computer is working and the phone has basically told me to sod off.
Same-ish. Keep getting a “your one time code may be wrong” message.
Nvm, tried a different Authenticator and it worked(?)
I will say, having no Talkback for a few days was entirely discomforting. You're all irritating cunts but it was quite unpleasant not having you around to make me feel better about myself. Thank you for fixing it trickster.
You can only have one authenticator registration to the site. Not one on each device. To have authentication in more than one device register one authenticator, then copy the details to authenticators on other devices. This has previously been covered in my treatise on authenticators.
Your username, password, and OTP code is the same on every device. Ergo if you can log in on one, you can log in on another. If you can't: clear the cache for the site on the problematic device and try again. If you are logged in somewhere successfully, the problem is at your end, with your device/browser.
Possibly Russian interference? Likely to be ever more of a problem now that Russian foreign policy is run from a desk in the oval office.
With the outage being so long I tried messaging you via Facebook to see if you knew something but your account has some setting preventing direct messages. I was pretty certain Tricky had been dicking around or a piece of 3rd party he used was broken and that he hadn't died and been eaten by cats.
If talkback did suddenly vanish, the why and how would be a mystery to many of us.
The last bit makes sense as I was accessing turdle on my old phone. I'm now on here on my new phone that arrived yesterday morning. It can't be cached in my browser. I'm in here posting, if I go to turnstile it says I'm authenticated, but turdle is giving me 403.
It's going to happen one day. I'm not getting any younger. Did consider jacking it in this time. I do take the community aspect of TalkBack more seriously than the football.
I get the same, the little favicon thingy is now alive again rather than grey. But it says 403 forbidden. Although I was kinda enjoying having my first morning break as free time and was not planning on getting back into doing it again having gone cold turkey on it, its still annoying me that I cant, rather than choosing not too.
