Oh noes, I was deducted "cool points" and now my open source project (which I maintain all by myself w/o any help or contributions in my free time) is less cool because a self proclaimed GitHub repository inspector does not like how I release my software!!!one!eleven

What shall I do? Should I delete #DOStodon? Should I delete myself? The world?

I like how they have made the effort to tell me they won't use it instead of providing a PR or help to fix it...

I pushed an update to #DOStodon (the #Mastodon client for MS-DOS):

- Updated #curl to 8.13.0
- Updated #mbedTLS to 3.6.3
- Fixed #win32 version (works on #WinXP or newer), DLLs were missing

Grab it at https://github.com/SuperIlu/DOStodon

Screenshot is showing the win32 version running on Win10.

Nachdem #DOStodon ja wirklich gut auf meinem alten Thinkpad R60 laeuft habe ich angefangen mal etwas tiefer in den Kaninchenbau rund um #dojs abzutauchen...
Javascript unter DOS ist irgendwie eine faszinierende Sache, eigentlich die logische Fortsetzung von BASIC oder anderen interpretierten Sprachen von "damals"

Plan for tonight: Install MS-DOS on the #WeeCee to publish a post on Mastodon using #DOStodon. Might be overly ambitious though—let’s see what roadblocks I encounter.

Erster toot per #DOStodon von einer unter #FreeDOS laufenden Maschine. Und ich habe ein absolut idiotisches Grinsen dabei im Gesicht

I pushed an update to #DOStodon (the #Mastodon client for MS-DOS):

- Updated README because of login-problems with Mastodon 4.3 or newer
- Uploaded #win32 version (works on #WinXP or newer)

Grab it at https://github.com/SuperIlu/DOStodon

Hunde die aufs Stöckchen starren. #vizsla #vizslalove #Jagdhund #surreal #dostodon #dogsofmastodon #Hunde #hundeliebe #vizslaliebe

My 2024 #GitHub #recap:

- Two #DOjS releases and a #win32 port

- A new release of #jSH

- Contributed #DJGPP patches to #mbedTLS and #jasper

- Updated my #BuildRoot GeodeLX repo

- Updated DOSQLite (#SQLite for MS-DOS)

- 11 Updates to #DOStodon (#MastodonClient for MS-DOS)

- Three updates to #httpDOS (#HTTPS server for MS-DOS)

.oO(#win32 and #win98 are REALLY testing my patience here. #DOStodon works fine with the win32-port of #DOjS on #Win10, but #SQLite3 and #Curl fail on #Win98)

I pushed an update to #DOStodon (the #Mastodon client for MS-DOS):

- Updated curl to 8.10.1
- Updated mbedTLS to 3.6.2
- Updated jpeg from 9e to 9f
- Updated SQLite to 3.46.1 (thanks to https://mastodon.social/@BenCollver@tilde.zone)

Grab it at https://github.com/SuperIlu/DOStodon

I updated DOSQLite (SQLite3 EXE for MS-DOS) to current SQLite version.

Thanks to @BenCollver for his work on the filename issue.

The update will also be included in the next releases of #DOjS and #DOStodon.

https://github.com/SuperIlu/DOSQLite

I’m doing some preliminary investigation into the #Macstodon login issue on Mastodon 4.3. I haven't found the specific cause of the problem, but the error message (“Security verification failed, are you blocking cookies?") seems to imply a CSRF failure.

I'm not entirely sure why the vintage Mac web browsers I've tried are unable to satisfy this requirement - maybe WebOne is mangling the CSRF cookie, I have to do more testing here.

One approach to solving this problem would be to use the "password” OAuth grant type, rather than the "authorization_code” grant type that is currently being used. Basically, you would log in to Macstodon with your Mastodon username/password directly, instead of using a web browser. This is the same approach that is currently being used by #DOStodon (https://github.com/SuperIlu/DOStodon/blob/main/mstdn.js#L220) and some other retro clients.

However, there are two problems with using the "password” grant type:

1. Not all servers support it. For example, compare the outputs of https://mastodon.social/.well-known/oauth-authorization-server and https://urusai.social/.well-known/oauth-authorization-server - and note that mastodon.social lists "password" under "grant_types_supported”, but urusai.social does not (also, that endpoint doesn't exist prior to Mastodon 4.3, so if the server is running an older version you just have to perform trial and error to see if password grants are supported)

2. MFA is not supported. If you're using multi-factor authentication with your Mastodon account, your only option is to log in using the "authorization_code" grant type. There is no option for appending your MFA token to your password.

The other option is to use a hybrid approach, where Macstodon would continue to use the "authorization_code" grant type, but would prompt for a username and password as if it were using the "password" grant type. Rather than launching a web browser, it would make the request for the login page directly, fill in the user's credentials and post the form, then screen-scrape the result for the authentication code. This is the approach currently being taken by #MastAppleII (https://github.com/colinleroy/a2tools/blob/master/src/mastodon/api/oauth.c#L14).

This approach is more brittle, and a much more challenging development effort, but it should work with most servers as well as for users with MFA.

Of course, this approach has one big gotcha of its own - older and newer Mastodon versions are less likely to work correctly due to changes in the design of the login page. Perhaps the "password" grant type should still be offered as an option (if the server supports it), and we allow the user to choose how they want to log in? Or would that be too confusing for users? Alternatively we could try the hybrid approach first, and then fall back to the password grant type if that fails.

Anyway, I'd love to hear your thoughts on how to approach this!

RE: https://oldbytes.space/@smallsco/113312004593805017