@nutomic:
I made some good progress on ActivityPub compliance this week. The main task that’s left to do is correctly discovering URLs for inbox, shared_inbox etc on remote instances, which I will finish next week. Then it might actually be possible to federate with other software.
- Community outbox now contains activities (!160)
- Database structs now use Url type for better type safety (#1371)
- Published my blog post for optimising compilation time in Rust
@dessalines:
Besides helping to prepare the v0.9.0
release, this week was mostly bug fixes.
- Made sure trending shows local communities only. Added
listing_type
toListCommunities
endpoint, in order to filter byLocal
. - Fixed an issue with the modlog not showing moderator bans and adds.
- Added some recurring tasks to Lemmy, including:
- A few active user queries, showing how many users have been active on both the site, and per community, by the last
day
,week
,month
, and6 months
. This is much more useful than the subscriber count for showing how active a community is. These are re-saved every hour. - Any indexes which use our postgres
hot_rank
function seem to de-grade over time, due to me incorrectly defining it as immutable. Re-indexing periodically fixes the issue. Not having an index here isn’t an option: the indexed query is <20ms
, while the un-indexed is >2s
. I’d def like to hear some ideas on other ways to do this, because it doesn’t seem like postgres can officially handle indexing any time-based function. - Our
activity
table is a copy of all incoming activities, and is the largest table. Added a task to periodically clear out activities older than 6 months.
- A few active user queries, showing how many users have been active on both the site, and per community, by the last
- Fixed post title height being too large in lemmy-ui.
- Added a max length to a password field.
- Fixed some release docs locations.
Hrm… I’ll think of good lines to add. Cause it’ll need to be added to
lemmy-translations
.