🦊 (fast) federated microblogging
Not yet dogfeeding our own software. Sorry 'bout that. Still a little too funky 'n' unstable for that.
@joakimfors @Codeberg yep, it would. the only concern i have is that we have a rather heavy CI workload and i really don't want to clog volunteer run infra with it
i love codeberg and am creating new repositories for projects of mine there
@noidea good point, actually. that's why i'm right now trialing the github discussions page and thinking about reviving the section on the socialhub (a discourse instance)
Kitsune chatrooms are deprecated. Matrix channels are locked, the Discord is deleted.
More expansive post here: https://aumetra.xyz/blog/kitsune-chatsrooms-deprecation
Working on the UI a bit so it's actually usable beyond account registration.
This is what the timeline is probably gonna look like. Already features virtual scrolling, so your browser won't explode from too many posts
Because `axum-flash` is apparently unmaintained we made our own. Called `flashy`, integrates perfectly with `tower` and, optionally, ` axum`.
Soon in the Kitsune sourcetree
@jplatte incredibly painless, most time was spent forking and PR-ing upgrades for the dependencies.
Also it's nice that we can now specify custom behaviour when extracting `Option<Self>` even if it results in some light boilerplate if we just want to swallow errors (maybe an attribute macro for the `impl FromRequest(Parts)` block would work?)
https://github.com/kitsune-soc/kitsune/commit/94b5df7a520a43ced4d8df7d036c1048341b7a93
axum v0.8 upgrade for Kitsune incoming. Also filed a few PRs to dependencies of ours to make them work :3
@joakimfors @evan Thanks for notifying! I will definitely planned to go to FOSDEM 2025 already. I just need to figure out the scope of the talk I would hold
Preview for HTTP requests from inside Wasm MRFs is merged. I'm going to bed. Good night
✅ Tailwind-based restyling: merged
✅ HTTP connection pooling utilization improvements: merged
✅ User-space DNS resolvers: merged
✅ Per-default DNS-over-TLS via @quad9dns for all HTTP requests: merged
This is done to prevent possible memory exhaustion DoS attacks on instances through faulty MRF implementations. Worst case an activity gets dropped.
HTTP requests and a limit on used memory which I forgot to implement previously.
Wasm plugins can now only ever use 100MB of memory. Any more and it will error out execution.
Also regarding the Wasm MRF (message rewrite facility; basically an activity-level plugin system), it is getting support for HTTP requests.
This effort was started due to requirements by @perillamint for something she is prototyping using the MRF API 🦊