cross-posted from: https://lemmy.ml/post/89740
Today is an exciting day for the Lemmy project.
Almost one year after first enabling federation, we now federate with other projects for the first time! According to some people’s definition, this finally makes us part of the Fediverse.
It took a lot of work to make this possible, so big thanks to NLnet for funding our full time work on Lemmy, and to @lanodan and @asonix for helping to figure out how Pleroma and Mastodon federation works (it’s difficult because they have almost no documentation).
Federation code rewrite
The rewrite of the federation code started by @nutomic in August is now mostly complete. As a result, the code is much cleaner, and has tests to guarantee no breaking changes between Lemmy versions. As a side effect of this rewrite, it was now relatively easy to enable federation with other projects.
Mastodon and Pleroma users can:
- View Lemmy communities, user profiles, posts and comments
- Follow Lemmy communities to receive new posts and comments
- Replies (mentions) work in both directions, including notifications
In addition, Pleroma users can exchange private messages with Lemmy users.
Note that Pleroma and Mastodon rely on a compatibility mode in Lemmy, which means that they won’t receive events like Deletes or Votes. Other projects whose federation works similar to Pleroma/Mastodon will likely also federate.
Hardcoded slur filter removed
Lemmy finally has essential moderation tools (reporting, user/community blocking), so the hardcoded filter isn’t necessary anymore. If you want to keep using the slur filter, copy these lines to your config file when upgrading, and adjust to your liking.
Federation with Pleroma/Mastodon works automatically, you don’t need to change anything, assuming that your allowlist/blocklist configuration permits it.
Note that Mastodon and Pleroma are much, much bigger than Lemmy at this point, with a combined 3 milion users and 4500 instances, compared to 20.000 users and 35 instances for Lemmy (source). The existing mod tools in Lemmy might not be adequate to handle that at the moment.
Be aware that if you have federation enabled in the Lemmy config, Mastodon and Pleroma users can now fetch all posts and comments, to view them and share with their followers. The Lemmy blocklist/allowlist can not prevent this, it only prevents posts/comments from blocked instances to be shown on your own instance. The only solution to this problem is disabling federation, or waiting for signed fetch to be implemented.
If you want to use federation, but review new instances before federating with them, use the allowlist. You can switch from open federation to allowlist federation by pasting the output of the command below into
federation.allowed_instancesin the Lemmy config.
curl https://your-instance.com/api/v3/site | jq -c .federated_instances.linked
Follow the Docker or Ansible upgrade instructions here.
We’ve now separated our ansible install method (the preferred way to deploy Lemmy) into its own repo, lemmy-ansible. Let us know if you need help migrating existing installations over to it.
- There is now a
GetUnreadCountin the API to check the count of your unread messages, replies, and mentions.
- A full list of the API changes can be seen on this diff of lemmy-js-client: 0.13.0 -> 0.14.0-rc.1 .
- More federation compat (#1894)
- Adding clippy:unwrap to husky. Fixes #1892 (#1893)
- Remove header guard for activitypub routes
- Add federation test cases for Smithereen and Mastodon
- Reduce stack memory usage in apub code
- Remove ActivityFields trait, deserialize into another struct instead
- Check if post or comment are deleted first. Fixes #1864 (#1867)
- Correctly use and document check_is_apub_id_valid() param use_strict_allowlist
- Convert note.content and chat_message.content to html (fixes #1871)
- Upgrade background_jobs to 0.9.1 #1820 (#1875)
- Fix husky fmt hook. (#1868)
- Renaming to slur_filter. Fixes #1773 (#1801)
- Three instance inbox bug (#1866)
- Remove ansible from this repo. (#1829)
- Rewrite collections to use new fetcher (#1861)
- Dont blank out post or community info. Fixes #1813 (#1841)
- Format config/defaults.hjson before committing (#1860)
- Breaking apub changes (#1859)
- Pleroma federation2 (#1855)
- Create a custom pre-commit hook, generates config/defaults.hjson (#1857)
- Add cargo metadata to all crates (#1853)
- Add both (De)Serialize to all models (#1851)
- Adding GetUnreadCount to the API. Fixes #1794 (#1842)
- Federate reports (#1830)
- Fix saved posts and hide read posts issue. Fixes #1839 (#1840)
- Dont allow posts to deleted / removed communities. Fixes #1827 (#1828)
- Dont swallow API errors (fixes #1834) (#1837)
- Fix federation of initial post/comment vote (fixes #1824) (#1835)
- Fix clippy warnings added in nightly (#1833)
- Admins can view all reports. Fixes #1810 (#1825)
- Adding a message_id to emails. Fixes #1807 (#1826)
- Generate config docs from code (#1786)
- Trying a background_jobs fix. #1820 (#1822)
- mark parent as read on reply (#1819)
- Move code to apub library (#1795)
- Adding honeypot to user and post creation. Fixes #1802 (#1803)
- Add database host back into config file (#1805)
- Updating translations.
- Fixing unload (#487)
- Fix setup password. Fixes #478 (#484)
- Adding post comment scrolling hack. Fixes #480 #486
- Navbar links (#476)
- Try fixing crypto node bug. Fixes #473 (#474)
- Use community title and user display name for dropdown.
- Mahanstreamer userpage (#471)
- Using i18next compatibility v3 (#465)
- Show original created time tooltip (#462)
- Revert version of i18next to fix plurals. Fixes #451 (#460)
- Fixing cross-posts showing on initial load. Fixes #457 (#464)
- Show bot account info. Fixes #458 (#463)
- Very weak password check (#461)
- Simplifying getunreadcount. (#455)
The writers lodge
»Some people can read War and Peace and come away thinking it’s a simple adventure story. Others can read the ingredients on a chewing gum wrapper and unlock the secrets of the universe.« — Lex Luthor
These rules extend the server rules and are not meant to replace them!