@dec_hl I tried to use dostodon with lsppp and i get an error on the console
-
@dec_hl I tried to use dostodon with lsppp and i get an error on the console:
Error: Can't resolve 'google.com': No nameserver defined
From jslog.txt:
WATTCP init: Error in PKTDRVR interface
More details:
Any troubleshooting ideas? Thanks!
-
@BenCollver I’m not sure what’s the problem. Seems like Watt32 in DOStodon has an error communicating with the packet driver.
Not sure what the issue is there...Can you provide me a copy of your setup?
-
@dec_hl Whatever the network problem was, it resolved itself. Sorry for the false start.
Now i am getting an error after the splash screen:
Error: Login failed: 400: {"error":"unsupported_grant_type","error_description":"The authorization grant type is not supported by the authorization server."}
Do you know what this means?
-
@BenCollver I'm not sure, do you have 2FA active?
Can you show me the full contents in JSLOG.TXT ?
-
-
@BenCollver yeah, the server login fails.
are you sure your email address and password are correct?
does tilde.zone support login via username/password?
-
@dec_hl I am using the account email. I see in MSTDN.JS
['grant_type', 'password']
for /oauth/token.
For this entry in the API docs i found:
"grant_types_supported": [
"authorization_code",
"client_credentials"
],
OAuth API methods - Mastodon documentation
Generate and manage OAuth tokens.
(docs.joinmastodon.org)
Theory: Maybe older server software supports grant_type of "password", but not mine?
-
@BenCollver very possible that there was a change. I have to look into the API docs again.
@smallsco did you encounter anything like this?
-
@dec_hl @BenCollver Yeah, the password grant type is being removed in Mastodon 4.4 (it’s already gone if your instance is running a nightly build). I wrote a bit about it here: https://oldbytes.space/@smallsco/113348186283238574
I thought it wouldn’t affect me since I’ve always used the OAuth authorization_code grant type in Macstodon - but Mastodon 4.3 did something with the CSRF implementation that stops the login page from working on vintage browsers, even with an HTTPS proxy in place.
So I’m going to have to rewrite the whole auth/login mechanism to use screen scraping (which is what the Apple II client is doing - https://github.com/colinleroy/a2tools/blob/master/src/mastodon/api/oauth.c#L14) - haven’t had the time to do so yet unfortunately.
This most recent update and the next one aren’t great for clients for vintage computers
-
@smallsco @BenCollver damn, so I’ll have to look into that.
Thanks! -
Pinging @andypiper
Do you know more details? This move could mean the end of most retro-clients...
-
@dec_hl @smallsco @BenCollver @andypiper
Oh I suddenly feel good that I somehow missed the password grant type. My code uses screenscraping, feel free to copy it, it's GPL 3 though.
I certainly hope the Mastodon folks won't break that on purpose. It's already inherently fragile. -
@colin_mcmillen @dec_hl @BenCollver @andypiper I love the QR code idea, provided that I can find a library to generate them that I can easily backport to Python 1.5.2
But while that solves the problem in one direction, it doesn’t help with getting the login code back to the retro machine.I’m not a fan of the screen scraping approach, given its fragility - my concern is that it won’t work for instances running older versions of Mastodon, or for instances with customized or themed login screens. But that may be the only option which involves completing the login process entirely on the retro machine, without additional dev support.
-
@smallsco @colin_mcmillen @dec_hl @BenCollver discussion noted, I don't have an immediate response and will be tied up until Monday with other things. Will do some asking / thinking, and support more when I can. NB this topic is briefly covered in the about-to-be-published dev blog for October's work. Please bear with me
