Really fast post parser, notifications, OpenTelemetry, dedicated job runner, and more!

Now with pre-built binaries for Windows, MacOS, and Linux with install scripts for PowerShell and Bash!

https://corteximplant.com/@0x0/111297237963021572

you are viewing a single comment's thread
view the rest of the comments

[–] 0x0@corteximplant.com 3 points 1 year ago (1 children)

@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@programming.dev 1 points 1 year ago

Agnosticism over protocols (maybe ActivityPub won’t be the only protocol we want to support in the future)

If that's simple to do, it's worth waiting for, but if it's trickier then I've learnt the importance of remembering YAGNI and KISS (and that database migration scripts aren't that hard). Of course, third party database queries aren't as simple to update but perhaps your API will be all implementers need.

If we can get under 16 columns, we can disable support for 32 columns in Diesel and save build time

This does seem worthwhile, just to speed up development cycles.