Rust

5749 readers

172 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

[email protected]

Kitsune 0.0.1-pre.4 — Lightweight ActivityPub server (github.com)

submitted 11 months ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

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

[–] [email protected] 4 points 11 months ago (1 children)

@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

[–] [email protected] 3 points 11 months 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

[–] [email protected] 1 points 10 months 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.