✅ GUI layout
🔶 Basic documentation
❌ Installers for
❌ Finalised documentation
❌ "Final release" (project is done, but will be continuously updated and supported for a while)
#FediBooks can now verify instances, making sure that they're not just random words or non-fedi websites! it's able to identify every majorish instance server out there, except for GNU social, which has been abandoned for nearly half a decade (but i'm still considering supporting it!)
what use is software designed for user friendliness without a manual? #FediBooks will have an extensive manual to explain everything you can (and can't!) do with it, from the basic stuff to the really advanced.
you can browse the manual in its current (very unfinished) state here: https://github.com/Lynnesbian/FediBooks/blob/master/MANUAL.md#introduction
#FediBooks progress made yesterday and today:
- GUI pretty much done (first draft, anyway)
- working main menu
- bot creation wizard can:
- animate while processing (multithreaded UI)
- verify that a given URL is a fediverse instance of some sort (GNU social isn't supported yet though)
- direct the user to the account creation page of any given instance
- work started on mastodon/pleroma app support (posting, downloading posts, etc)
- documentation for the project as a whole, as well as the bot creation wizard in specific, provided as a manual
- donation links
#FediBooks needs to support multiple authentication methods, and it does that by switching what its GUI looks like depending on your instance type.
diaspora* users are asked for a username and password.
mastodon and pleroma users get OAuth with codes that need to be copied and pasted into the program.
misskey uses the authentication page, which doesn't actually require typing or pasting anything at all!
@lynnesbian Lynne, have you considered starting a localhost web server to receive the OAuth callback?
@ben i could, but that'd require importing a server library, and also checking whether or not there's anything running on :8080 (so then we'd neet to use a different port)
@ben it's worth the effort though... i'll give that a shot
@lynnesbian start the server on 127.0.0.1 (port 0) and the OS will pick the port for you.
Since you only need to receive one request ever, you don't need to record that port number once you've used it to generate the redirect URL.
@ben can you really do that? ooh that's cool
@ben any idea what server library i should use? i don't really want to use something like django for this
@lynnesbian for weblegends, I rolled my own, and I feel like what you need is even simpler than what weblegends needed.
@ben it looks like i'll want something like this: https://docs.python.org/3/library/http.server.html
@lynnesbian ah, if it's in the standard library, definitely use that.
@firstname.lastname@example.org's anti-chud pro-skub instance for funtimes