πŸ”Ά GUI layout
❌ Basic documentation
❌ Code
❌ Installers from :linux: :windows: :finder:
❌ Finalised documentation
❌ "Final release" (project is done, but will be continuously updated and supported for a while)


βœ… GUI layout
πŸ”Ά Basic documentation
πŸ”Ά Code
❌ Installers for :linux: :windows: :finder:
❌ Finalised documentation
❌ "Final release" (project is done, but will be continuously updated and supported for a while)


Show thread

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!)

Β· Β· Web Β· 2 Β· 4 Β· 9

also i just spent the last hour trying to figure out how to do multithreading with pyside :blobderpy:

Show thread

what use is software designed for user friendliness without a manual? 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: github.com/Lynnesbian/FediBook

Show thread

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 :blobcatwinktongue:

Show thread

i've made a fair bit of progress that i haven't posted about here, like authentication, more GUI stuff, etc

Show thread

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!

Show thread

@lynnesbian caveats: computer program does not work if you turn off computer

@lynnesbian it reminds me of the Celeste intro sequence which includes a warning not to turn off your computer during autosaves

which as far as I know is physically impossible on Windows because it takes way longer to start the shutdown process than it takes to save one kilobyte of XML.

@lynnesbian pretty sure that would also take longer than celeste autosaves take

unless you can frame-perfect unplug your computer


@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)

@lynnesbian start the server on (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 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.

@lynnesbian ah, if it's in the standard library, definitely use that.

@lynnesbian @ben doesn't Python have a SimpleHTTPServer module or something

i don't know if you can use it programmatically, i've only seen it used with like `python - m`

@lynnesbian so close (but it's an excellent theme for me to be that confused!)

Sign in to participate in the conversation

@lynnesbian@fedi.lynnesbian.space's anti-chud pro-skub instance for funtimes