Jorijn Schrijvershof

There's a new very lightweight Fediverse platform that's just been released called littleFedi. You can follow its new official account at:

🌱 @littlefedi_official

Its official website including download and source code is at:

🌱 https://littlefedi.org

LittleFedi is intended for techy people who want to create their own Fediverse server using as few resources as possible.

It's written by @stefano (who also created the weather service FediMeteo).

#Fediverse #ActivityPub #FOSS #SelfHosting

@stefano@bsd.cafe @fd0@littleone.littlefedi.social @ivory@tapbots.social

Spent a bit of time debugging with Claude based on the source code and webserver logs, and found a few reasons. See below. Claude made a few patches and Ivory works as intended now. Hope this helps, somehow :)

Let me know if you want to see the code, but since its AI; YMMV.

• Home timeline doesn't refresh.

  • Problem: the timeline cache keeps min_id/since_id results for up to timeline_ttl and doesn't clear them when new posts arrive. Ivory keeps asking for posts newer than its newest one and gets the same empty list for up to two hours.
  • Solution: don't cache min_id/since_id windows, or invalidate them whenever the viewer's home feed changes. Turning off [cache] fixes it as a workaround.

• Notifications don't refresh.

  • Problem: /api/v1/notifications and /api/v2/notifications send no Link header. Ivory builds its refresh request from rel="prev", so pull-to-refresh never reaches the server.
  • Solution: send Link headers with absolute URLs, as the timeline endpoints already do. Patch attached.

• Read position isn't saved (PostgreSQL).

  • Problem: the marker upsert refers to version without naming the table, which PostgreSQL rejects as ambiguous. Every POST /api/v1/markers returns 500, so Ivory can't sync unread state and notifications are never marked read.
  • Solution: write markers.version in the update.

• Push notifications can't be expanded.

  • Problem: the push payload has no access_token, and notification_id is the internal UUID rather than the API ID. Ivory's notification extension then fetches the full notification and gets 401.
  • Solution: send the numeric API ID, and provide a way for the client to authenticate that fetch.

New month, new feature - and this one is BIG 🎉

Tuta & @nextcloud are joining forces to enable you to fully replace MS365 and Google Workspace with a digital sovereign alternative, made in Germany. 🇩🇪

Meet the Tuta App on Nextcloud with neat integrations! 🥳

Plus, it's completely free and #OpenSource.

Check out the details: ➡️ https://tuta.com/blog/tuta-app-on-nextcloud 

#DigitalSovereignty #MadeInGermany