Hi all,

I've been running my Lemmy server since 2023 with minor issues, however I recently had my server go down for about two weeks due to a drive failure (should have been a RAID array, I know, but when I set this up originally I wasn't sure if it would be a mainstay and then I never revisited my design).

So, this has brought about a couple different problems, first and foremost federation seems completely broken? My proxy configuration and cloudflare stuff has been unchanged, so I don't think that is the issue. However, I'm not receiving new posts, comments, or upvotes (after what gets synced initially).

Here are the logs from the lemmy backend:

2025-10-14T21:05:39.429156Z  WARN lemmy_server::root_span_builder: CouldntFindPost: CouldntFindPost

   0: lemmy_api_crud::post::read::get_post

           with data=Query(GetPost { id: Some(PostId(1495861)), comment_id: Some(CommentId(4689293)) }) local_user_view=None

             at crates/api_crud/src/post/read.rs:18

   1: lemmy_server::root_span_builder::HTTP request

           with http.method=GET http.scheme="http" http.host=lemmy:8536 http.target=/api/v3/post otel.kind="server" request_id=f47caa4f-2ef1-4bff-a7fa-f8d27c75294b

             at src/root_span_builder.rs:16

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_person', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_comment', message: '' }

{ name: 'couldnt_find_post', message: '' }

{ name: 'couldnt_find_post', message: '' }

The second question I have, and I fear there may be nothing i can do about this, is since I had to recreate my lemmy db I don't have any of the posts from my users on here anymore. They were all to other servers, so I assume there is some sort of copy out there. Is there a way that I can get them to federate back to my server? Or are they just lost to the ether of posts?

EDIT: The plot thickens...

I connected to the database, and I can see a ton of recent posts/comments/interactions, but those aren't showing up in the frontend? Maybe there is something messed up in my config, but its more or less what was in the docs (only changes were to make it work with my proxy vs the built-in nginx)

We were excited to see the recent release of Ghost 6 with ActivityPub features. The Ghost team have been an active participant in our Long-form Text project. And Mallory’s newsletter the Internet Exchange just published about why they use Ghost. John O’Nolan, founder and CEO of Ghost.org, was kind enough to answer our questions about the software and its community.

SWF: For our readers who don’t know Ghost, how would you describe the platform?

JO: Ghost is an independent publishing platform for people who take writing seriously. We’re open source, non-profit, and built to give creators complete ownership of their content and their audience. We’ve helped indie publishers generate over $100 million in revenue from sustainable modern media businesses like 404Media, Platformer and Tangle News.

SWF: Tell us about your user community. Can you paint a picture of them with a broad brush? What kind of people choose Ghost?

JO: Ghost attracts people who care about owning their home on the internet, rather than having another profile on a social media platform. Our publishers range from solo journalists and creators, to established news outlets and large businesses. They value independence, and they’re willing to do the work to maintain control of their brand, distribution, data, and relationship with readers.

SWF: What is it like to be a Ghost user in 2025? What kind of problems are your users facing today?

JO: The big challenge today is the same one that’s haunted independent publishers for two decades: discovery. You can own your platform and serve your audience beautifully, but if people can’t find you, none of it matters. Email newsletters have been a solid answer, but they’re still dependent on deliverability and inbox placement. Algorithms on social platforms actively suppress links now, so sharing your work there is like shouting into a hurricane.

SWF: Tell us about your experience with ActivityPub. Why did you decide to add ActivityPub support to your software?

JO: Ghost has had support for delivering content by email newsletters for a number of years, and email has remained an unassailable distribution platform for publishers because it’s an open protocol. No company controls your email list except you, so it’s one of the best investments you can make. ActivityPub is now doing the same thing for social technology. It allows publishers to own and control a distribution channel that allows their work to spread and be discovered by others. For the first time, you can publish independently and grow faster than ever before.

SWF: What stack is Ghost built on? What development tools does your team use?

JO: Ghost is all built in modern JavaScript; mainly Node and React. Our ActivityPub service is built on Fedify, and everything we build is released under an open source MIT license. Our development tools are constantly evolving, and now more quickly than ever before with the advent of AI tools, which seem to change on a near weekly basis.

SWF: What was the development process like?

JO: Challenging, honestly. ActivityPub is beautifully designed but the spec leaves room for interpretation, and when you’re building something new, there’s no roadmap. Building interoperability between other platforms, who’ve all interpreted the spec in their own unique ways, has been a real challenge. The approach we took was to ship early versions as quickly as possible to beta testers so we could learn as we go, using real-world data and issues to guide our process. We’re in a good spot, now, but there’s still a lot to do!

SWF: Ghost produces long-form blog posts, articles and newsletters. How was the experience adapting Ghost articles to the microblogging interfaces of Mastodon and Threads?

JO: In some ways really easy, and in other ways quite tricky. We’re at a pretty early stage for long-form content on ActivityPub, and the majority of other products out there don’t necessarily have interfaces for supporting it yet. The easy part is that we can provide fallbacks, so if you’re scrolling on Mastodon you might see an article title and excerpt, with a link to read the full post – and that works pretty well! The dream, though, is to make it so you can just consume the full article within whatever app you happen to be using, and doing that requires more collaboration between different platforms to agree on how to make that possible.

SWF: You’ve been an active participant in the ActivityPub community since you decided to implement the standard. Why?

JO: ActivityPub is a movement as much as a technology protocol, and behind it is a group of people who all believe in making the web a weird, wonderful open place for collaboration. Getting to know those humans and being a part of that movement has been every bit as important to the success of our work as writing the code that powers our software. We’ve received incredible support from the Mastodon team, AP spec authors, and other platforms who are building ActivityPub support. Without actively participating in the community, I don’t know if we would’ve gotten as far as we have already.

SWF: Ghost has implemented not only a publishing interface, but also a reading experience. Why?

JO: The big difference between ActivityPub and email is that it’s a 2-way protocol. When you send an email newsletter, that’s it. You’re done. But with ActivityPub, it’s possible to achieve what – in the olden days – we fondly referred to as ‘the blogosphere’. People all over the world writing and reading each other’s work. If an email newsletter is like standing on a stage giving a keynote to an audience, participating in a network is more like mingling at the afterparty. You can’t just talk the whole time, you have to listen, too. Being successful within the context of a network has always involved following and engaging with others, as peers, so it felt really important to make sure that we brought that aspect into the product.

SWF: Your reader is, frankly, one of the most interesting UIs for ActivityPub we’ve seen. Tell us about why you put the time and effort into making a beautiful reading experience for Ghost.

JO: We didn’t want to just tick the “ActivityPub support” checkbox – we wanted to create something that actually feels great to use every day. The idea was to bring some of the product ideas over from RSS readers and kindles, where people currently consume long-form content, and use them as the basis for an ActivityPub-native reading experience. We experimented with multiple different approaches to try and create an experience with a mix of familiarity and novelty. People intuitively understand a list of articles and a view for opening and reading them, but then when you start to see inline replies and live notifications happening around those stories – suddenly it feels like something new and different.

SWF: If people want to get a taste of the kind of content Ghost publishers produce, what are some good examples to follow?

JO: Tough question! There are so many out there, and it really depends on what you’re into. The best place to start would be on ghost.org/explore – when you can browse through all sorts of different categories of creators and content, and explore the things that interest you the most.

SWF: If I’m a Fediverse enthusiast, what can I do to help make Ghost 6 a success?

JO: Follow Ghost publishers and engage with their content – likes, replies, reposts all help! Most importantly, help us spread the word about what’s possible when platforms collaborate rather than compete. And if you’re technical, our ActivityPub implementation is entirely open source on GitHub – contributions, bug reports, and feedback make the whole ecosystem stronger.

I had a random idea I wanted to throw out there and see what people think:

Imagine a federated platform that works kind of like Discord, but in the sense of Lemmy, Pixelfed, Mastodon, etc.—with different instances hosted by different people.

The twist is that none of the instances would be connected to each other.

Each instance would function like a regular Discord server: channels, chats, roles, and all the usual stuff, but the instances themselves wouldn’t federate with each other.

The interesting part is that these instances could still federate with other platforms—like Mastodon, Lemmy, Peertube, Pixelfed, Loops, etc.—just not with each other.

It seems like it could be a way to have smaller, self-contained communities while still integrating with the wider Fediverse in some ways.

My only sticking point is figuring out signup/login mechanics—how would a user navigate multiple isolated instances efficiently without it becoming a nightmare?

Would love to hear thoughts, improvements, or whether anyone thinks this is a terrible idea.

It's been a busy month, with a lot of work to add new features to lemmy-ui which were already added to the Lemmy backend before. There were also a lot of bug fixes for the development version. We are gradually getting closer to a 1.0 release.

While the API changes for 1.0 are mostly finalized, we still have many more lemmy-ui 1.0 tasks to complete.

Some of the major additions:

• Simplified lemmy-ui development.
• Audio file support in lemmy-ui.
• Added comment locking (which also locks children). Thanks to @flamingos-cant)
• Post time filtering, with a smart dropdown.
• Added ability to block all users from an instance (separate from blocking all communities)
• Added ability to make a note for a person, and view the vote totals you've given to them.
• Fixed remote RSS feeds.
• Added ability to do actions on report items, from the reports page.

::: spoiler Full list of changes by user

salif

• Fix data URL syntax in webmanifest

Meri-Dax

• Saving video width and height alongside embed_video_url

flamingos-cant

• Use more standard AP fields for community tags
• Don't populate embed fields when the Opengraph tag is empty
• Add urls for moderators and featured collections on local communities
• Comment lock

MV-GH

• Restore deprecated apk post processing config
• Regenerate baseline profiles
• Bump to Android SDK 36
• Fix too large images in comments being cutoff
• Add option to disable video auto play

dessalines

• Fixing missing shortcode from emoji updating.
• Validate saving default_items_per_page local user setting.
• Fixing show_scores -> show_score DB name.
• Fixing LockComment and ModLockCommentView
• Fixing local_user table column order.
• Adding type_ to PostOrCommentOrPrivateMessage enum.
• Fix post like not decrementing vote totals.
• Add ability to mark a notification as unread.
• Changing rss inbox feed -> notifications
• Fixing admin list users not using query.
• Adding ban_expires_at to views
• Adding a post undelete delay to fix federation tests.
• Add voyager development as the default test server for test.sh
• Adding default posts_per_page setting.
• Add ability to lock comments
• Adding post time filtering with defaults.
• Upgrading pnpm to 10.16
• Collapse removed comments that have no children by default.
• Updating to new 1.0 names.
• Adding ability to visit a random community.
• Highlight new comments using the last read comments time.
• Fixing scheduled publish time.
• Adding read and hidden content for your profile.
• Add ability to show banned users and all users.
• Fixup notifs
• Add @nutomic to codeowners
• Fix profile radios spacing.
• Add ability to block all persons from an instance.
• Add ability to create a note for a person, and view vote totals
• Add ability to resend verification email.
• Use the getCommentsSlim variant for post comments.
• Fixing build tools to version 36.0.0

Nutomic

• Include error message for rate limit error (fixes #6019)
• Proper null check for mod-reason-mandatory (fixes #6021)
• Update dependencies, use latest diesel-cli
• Set image_mode: None for development
• Correct name for instance default theme
• Avoid unnecessary requests to w3.org (fixes #5999)
• Fix remote user/community rss feeds (fixes #5997)
• Dont allow write api actions for banned user
• Exclude LocalSite.multi_comm_follower from public api
• Let banned users login
• Make reason mandatory for mod actions (fixes #1948)
• Remove local_user.enable_keyboard_navigation (fixes #5988)
• Rename FederationState.next_retry and NotificationType
• Rename person banned columns
• Show most used languages first
• Restrict max length of community title
• Reenable plugin hook (fixes #5925)
• Sorting for instance list
• Print diff-check errors to stdout (fixes #5937)
• Avoid regenerating metadata for unchanged post url (fixes #5956)
• Dont allow removing only mod/admin, remove leave_admin endpoint
• Provide federation context collection (fixes #5283)
• Add report actions (fixes #501)
• Convert buttons for view all, show context to links (fixes #3229)
• Enable various lints
• Enable alt text for videos (fixes #2779)
• Fetch emoji data separately (fixes #3470)
• Downscale proxied thumbnails (fixes #2591)
• Insert emojis at current cursor position (fixes #1983)
• Simplify translation code
• Fix Arabic user/community names (fixes #2207)
• Correct name for instance default theme (fixes #2371)
• Fetch similar posts when copying suggested title (fixes #2029)
• Fix community link in modlog title (fixes #2209)
• Properly render multi-line deny reason (fixes #3103)
• UI changes if current user is banned (fixes #989)
• RSS feed should use local domain (fixes #2012)
• Add button to expand all images (fixes #1273)
• Remove env var LEMMY_UI_DEBUG, use NODE_ENV instead
• Add new modlog filters
• Extend readme
• Improve development instructions to use remote instance
• In search results show number of posts/comments for users/communities
• Add checkbox for title only search (#3220)
• Use params instead of string concat (fixes #1350)
• Setting for community/post notifications
• Extend admin user list with more info
• Allow blocking community that banned you (fixes #3267)
• Multiple language input using checkboxes (fixes #1935)
• More details about crossposts (fixes #3386)
• Instance list changes (fixes #3261)
• Respect link target for post domain (fixes #3256)
• Show community languages in sidebar (fixes #1009)
• Implement donation dialog
• Hide bio for banned users (fixes #961)
• Indicate when registration is disabled (fixes #2070)
• Add icon to indicate new accounts (fixes #2389)
• Remove outline for username button