@Deebster @erlend_sh the biggest blockers regarding the database schema design right now are:

• Bring-your-own-domain
• Settings and preferences
• System account (for authorized fetch mode)

That requires a lot of consideration though, and I'd also like to subdivide the accounts table more for two reasons:

• Agnosticism over protocols (maybe ActivityPub won't be the only protocol we want to support in the future)
• If we can get under 16 columns, we can disable support for 32 columns in Diesel and save build time

That's basically it. Aside from that there's not too much I'd change in an incompatible way

@Deebster @erlend_sh Yeah.. we just don't like to commit. Like just yet.

I really need to give myself a weekend to go over the database schema and find something I'm happy with that I want to keep.

That's like the biggest reason I'm not committing to anything but "pre"s yet :blobfoxmeltsob:

Just my life has been rather chaotic over the last few months. And now a new job soon and everything.

inb4 making it on https://0ver.org/ soon

@gabe yes! a UI beyond that is planned but progress is rather slow on that component.

i want to invest some more time into that soon though

login already works and it refreshes the oauth tokens correctly, now we "just" need to build the actual good looking components

@gabe @erlend_sh The UI is very much in progress, there is no actual UI like you'd expect yet, but we offer Mastodon API compatibility to fill the gap until the UI is in a usable state.

Pinafore/Semaphore works fine with it, Elk also kinda works (but due to the missing streaming API, it has some issues)

But this is what the landing page looks like so far: https://corteximplant.com/system/media_attachments/files/110/967/120/614/016/911/original/d2d80bda145c0e5f.png

(edit: I think I have to include the link so it's visible on Lemmy?)