During the past month, we’ve been working rapidly on adding features to lemmy-ui. We also finished up the last major backend changes. This means we can soon go to the beta phase for 1.0, which will focus on testing, bug fixing and helping Lemmy clients to start updating for the new API. After that will be the release candidate phase when version 1.0 will be live tested on lemmy.ml.

You can see the changes in action on the test server voyager.lemmy.ml (which was recently wiped). Registration is open, you are welcome to try things out. To stay up to date with our progress look at the lemmy-ui 1.0 and lemmy 1.0 milestone issues.

The major changes during October were:

• Speeding up migrations for 1.0 and reducing database size
• Notify users about moderation actions
• Default data for new instances (welcome post and popular communities)
• Card views for post listing
• Showing community sidebar on create post page
• Blurhash for images

Full list of changes by user

matc-pub

• Pick date-fns based on translation description (fixes #3483)

dullbananas

• Shrink things that are rewritten in slow migrations

SleeplessOne1917

• Re-export PersonResponse from lemmy-api-common

MV-GH

• Reduce recompositions in the comments

dessalines

• Remove special BanFromCommunityResponse in favor of PersonResponse.
• Multi-community-feeds should be at /m/ , not /c/
• Fixing a few issues with federation-view exports.
• Fix release builds by remove space in platforms.
• Add comment for is_upvote API fields.
• Make sure creator_banned uses item_creator for ReportCombinedView
• Make all the serde tagged types snake_case
• Adding read bool to mark_many_as_read API.
• Make sure create_multi_community_entry returns the community.
• Fixing admin instance block expires_at to use a unix timestamp, with a check.
• Making multi-community follow and edit return a MultiCommunityResponse.
• Add wait after delete user to fix federation CI tests.
• Changing NotePerson response from SuccessResponse to PersonView
• Adding follow_state to MultiCommunityView
• Adding creator and community indexes for post_aggregates.
• Clean up post and comment actions bars
• Adding enable_animated_images, and hide_media setting.
• Adding support for stay_logged_in to login and signup fields
• Adding community description to form and community sidebar.
• Add blurhash image using unlazy.
• Adding collapse_bot_comments setting, and doing that action.
• Upgrading for new API updates
• Adding card and small card views
• In instance settings move admin list to users tab
• Fixup instance_blocks.tsx
• Add more settings
• Fix link-dark issues
• Remove tables in favor of bootstrap columns
• Use btn-sm for post and comment actions buttons.

Nutomic

• Remove some unused code
• Small compile speed optimizations
• Revert changes to crud trait which slowed down compilation (ref #5874)
• Retry tests in ci on failure (ref #5925)
• Handle plain identifiers in markdown
• Setup default data for new instance
• Fix wrong federation error and simplify code (fixes #4363)
• Implemente federated instances view (fixes #6063)
• Expire logins after one week by default, add param stay_logged_in
• Create plugin hook for new notifications and reports (fixes #1027, fixes #5349)
• Fix for NodeBB compat and updated test assets
• Include caller information in error logs
• Include id for CommunityHasNoFollowers
• Auto-follow community when enabling notifications (fixes #6081)
• Serialize enum variants in snake_case (fixes #6062)
• Dont send duplicate notification in case of reply with mention
• Include keyword blocks and discussion languages in backup (fixes #5811)
• Use proper title for replies and mentions in RSS feed (fixes #5357)
• Private community fixes
• Add build.rs to update db migrations macro (fixes #6005)
• Allow users to view comments of deleted posts (fixes #6044)
• Multi-community fixes
• Proper error message for image upload (fixes #6042)
• Case insensitive comparison for read_from_apub_id (fixes #6037)
• Move some errors to not be translated
• ReportCombined: add missing column creator_ban_expires_at
• Allow mods to resolve removed posts (fixes #6018)
• Split apub code into multiple crates, other changes for faster building
• Notify mod actions
• Remove env var LEMMY_UI_HTTPS (fixes #3573)
• Check for untranslated error messages (fixes #3478)
• Use localhost as testhost
• Private community
• Use upstream status code for error responses (fixes #3085)
• Change format for inserted person/community links (fixes #1743)
• Consistent size for action buttons (ref #3503)
• Disable comment form if post is removed or deleted
• Revert “Add button to expand all images”
• Enable some lint rules for jsx
• Block community from context menu (fixes #3306)
• In comment search results show post and community (fixes #1959)
• Open link for markdown help in new tab (fixes #2129)
• Add rel=nofollow to markdown links (fixes #542)
• Show sidebar on create post page (fixes #1522)
• Add audio player for direct links to audio files (fixes #2529)
• Fix “show context” (fixes #3496)
• Indicate removed/deleted comments (fixes #1144)
• Use lint to disallow console.log
• Filter community selection for posting (fixes #2604)

Or see the full list of changes at the links below:

• Backend
• Frontend
• Jerboa

---

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Even so there is barely enough time in the day, and no time for a second job. The only available option are user donations.

To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate