Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

What is the current state of Discourse to threadiverse federation?

Fediverso
15 10 60
  • I found this article from earlier this year: https://blog.discourse.org/2025/04/discourse-and-the-fediverse/

    However, I haven't come across that much content from Discourse platforms over here on Lemmy/Piefed. Is there more work to do with the plugins, or should we work with organizations running Discourse to help them connect with us?

    For example, the threadiverse communities for OpenStreetMaps is relatively small, and being able to see / contribute to community.openstreetmap.org would be amazing.

    From a few(3) places that I have asked, It's either they can't due to enterprise hosting requirement on discourse servers or they don't want to due to controversy (CSAM).

  • I found this article from earlier this year: https://blog.discourse.org/2025/04/discourse-and-the-fediverse/

    However, I haven't come across that much content from Discourse platforms over here on Lemmy/Piefed. Is there more work to do with the plugins, or should we work with organizations running Discourse to help them connect with us?

    For example, the threadiverse communities for OpenStreetMaps is relatively small, and being able to see / contribute to community.openstreetmap.org would be amazing.

    First of all it's opt in so they have to enable it. Second it's currently broken federating with lemmy. I think they developed it with mastodon in mind. I've already reported how it doesn't federate properly to them last year

  • I found this article from earlier this year: https://blog.discourse.org/2025/04/discourse-and-the-fediverse/

    However, I haven't come across that much content from Discourse platforms over here on Lemmy/Piefed. Is there more work to do with the plugins, or should we work with organizations running Discourse to help them connect with us?

    For example, the threadiverse communities for OpenStreetMaps is relatively small, and being able to see / contribute to community.openstreetmap.org would be amazing.

    As far as I can see, you can ask questions and follow categories if the admin sets this up.
    Here is an example: events@forum.fedimins.net

    You can only post if you connect your Fediverse account to the forum.

  • I found this article from earlier this year: https://blog.discourse.org/2025/04/discourse-and-the-fediverse/

    However, I haven't come across that much content from Discourse platforms over here on Lemmy/Piefed. Is there more work to do with the plugins, or should we work with organizations running Discourse to help them connect with us?

    For example, the threadiverse communities for OpenStreetMaps is relatively small, and being able to see / contribute to community.openstreetmap.org would be amazing.

    Discourse decided to do its thread context in a way that's currently incompatible with projects like Mbin or Lemmy. Those expect threads to be represented by some kind of post (Page, Article, Image, etc objects), while Discourse decided to use an OrderedCollection, with the first item being the opening post.

    Even if Lemmy decided to add support for OrderedCollection threads, there's another issue though: the barrier for initial federation is too high. Discourse only gives you the fediverse handle of its categories, but to federate them in, you need their JSON-LD URL, not the handle. And Discourse decided to use separate URLs for its HTML and JSON-LD pages, with no way to derive the latter from the former. So to initiate federation with a Discourse category, you have to manually do a WebFInger query to get its URL to then give it to your instance. I think most people probably fail this hurdle, either out of laziness or lack of know-how.

    Also, I don't know about Lemmy, but the Mbin instance I'm using seems incapable of processing Discourse categories anyway. Not sure why that is.

    That means Lemmy is entirely reliant on Discourse users replying to posts that are visible to Lemmy, similar to Lemmy-Mastodon interaction. But with less users, hence less overall interaction frequency.

  • As far as I can see, you can ask questions and follow categories if the admin sets this up.
    Here is an example: events@forum.fedimins.net

    You can only post if you connect your Fediverse account to the forum.

    Do you see any content on that page? I'm looking at !events@forum.fedimins.net but I don't see anything except the title and icon

  • Discourse decided to do its thread context in a way that's currently incompatible with projects like Mbin or Lemmy. Those expect threads to be represented by some kind of post (Page, Article, Image, etc objects), while Discourse decided to use an OrderedCollection, with the first item being the opening post.

    Even if Lemmy decided to add support for OrderedCollection threads, there's another issue though: the barrier for initial federation is too high. Discourse only gives you the fediverse handle of its categories, but to federate them in, you need their JSON-LD URL, not the handle. And Discourse decided to use separate URLs for its HTML and JSON-LD pages, with no way to derive the latter from the former. So to initiate federation with a Discourse category, you have to manually do a WebFInger query to get its URL to then give it to your instance. I think most people probably fail this hurdle, either out of laziness or lack of know-how.

    Also, I don't know about Lemmy, but the Mbin instance I'm using seems incapable of processing Discourse categories anyway. Not sure why that is.

    That means Lemmy is entirely reliant on Discourse users replying to posts that are visible to Lemmy, similar to Lemmy-Mastodon interaction. But with less users, hence less overall interaction frequency.

    Thank you for the detailed explanation, that makes sense :)

  • I found this article from earlier this year: https://blog.discourse.org/2025/04/discourse-and-the-fediverse/

    However, I haven't come across that much content from Discourse platforms over here on Lemmy/Piefed. Is there more work to do with the plugins, or should we work with organizations running Discourse to help them connect with us?

    For example, the threadiverse communities for OpenStreetMaps is relatively small, and being able to see / contribute to community.openstreetmap.org would be amazing.

    @otters_raft I suggested on a few forums that I belong to that using the plugin might be useful and federating content would be a good idea - What I got back was fairly negative feedback - e.g people thought it would cause people who don't have accounts on the relevant forum being able to spam the forum and get around repuation requirements (not true I understand) - but also a kind of - query why federation would be useful - with an assumption people would just come to the forums and monitor them directly.
  • Discourse decided to do its thread context in a way that's currently incompatible with projects like Mbin or Lemmy. Those expect threads to be represented by some kind of post (Page, Article, Image, etc objects), while Discourse decided to use an OrderedCollection, with the first item being the opening post.

    Even if Lemmy decided to add support for OrderedCollection threads, there's another issue though: the barrier for initial federation is too high. Discourse only gives you the fediverse handle of its categories, but to federate them in, you need their JSON-LD URL, not the handle. And Discourse decided to use separate URLs for its HTML and JSON-LD pages, with no way to derive the latter from the former. So to initiate federation with a Discourse category, you have to manually do a WebFInger query to get its URL to then give it to your instance. I think most people probably fail this hurdle, either out of laziness or lack of know-how.

    Also, I don't know about Lemmy, but the Mbin instance I'm using seems incapable of processing Discourse categories anyway. Not sure why that is.

    That means Lemmy is entirely reliant on Discourse users replying to posts that are visible to Lemmy, similar to Lemmy-Mastodon interaction. But with less users, hence less overall interaction frequency.

    Hey! Thanks for the concise reply. There's a lot of technical stuff I can say about Discourse and such, but because I am the maintainer for NodeBB it is probably in my best interest to keep my mouth shut as we directly compete!

    Anyhow, the OrderedCollection stuff is actually all from me. I've been working as part of the Threadiverse working group to bring intercompatible formats to all threadiverse software, which besides Discourse and NodeBB, includes Lemmy, Piefed, and Mbin.

    The OrderedCollection enables software (like NodeBB) to quickly backfill entire topics. This is a huge problem on the microblog-side of the fediverse, and is not really a problem on the theadiverse, since there is already strong support for synchronization. However, smaller instances often do run into issues where they can't ever "catch up" on old posts because there's no way to get those posts. (e.g. start following a new community, you can't read any of the old content)

    To that end, Lemmy and Piefed have (or soon will) ship code to allow software to backfill using OrderedCollections. They don't use them yet, but they will provide them. It helps software like mine because I will then be able to see entire threads from communities I don't even know about or follow. It's a huge boost to discovery! :smile:

    > while Discourse decided to use an OrderedCollection, with the first item being the opening post.

    NodeBB also does this, but they're not incompatible per se. You'll see NodeBB topics showing up just fine on Lemmy and Piefed (see activitypub@community.nodebb.org or general), and that's because NodeBB does the extra step of announcing OP and replies, just like Lemmy/Piefed.

    Importantly, Discourse does this too, but because of the inability to find Discourse categories, I don't think it's easy to follow them. Chicken and egg, really. The way the AP integration in Discourse is built-out, it is more insular by design. Threads from Discourse only ever go out to the fediverse, you can't post in from the fediverse. That makes those communities much more insular by design and severely limits discovery.

  • Nodebb is the forum that federates

    Heckin' yeah it is. :sunglasses:

  • @otters_raft I suggested on a few forums that I belong to that using the plugin might be useful and federating content would be a good idea - What I got back was fairly negative feedback - e.g people thought it would cause people who don't have accounts on the relevant forum being able to spam the forum and get around repuation requirements (not true I understand) - but also a kind of - query why federation would be useful - with an assumption people would just come to the forums and monitor them directly.

    This is an important thing to consider, and why NodeBB decided to even pursue federation at all.

    It's arguable that we've reached the point at which forums cannot organically grow due to the ubiquity of social media. Depending on who you ask, we've reached that point 10+ years ago already.

    It's becoming increasing imperative that forums federate or risk dying due to attrition. Forums used to be the social network for niche topics. Facebook (with Groups) and Twitter (with hashtags) started competing, and Reddit (with subreddits) made another huge dent.

    There are some communities that fear integrating with AP will cause their local communities to become flooded with just anybody. Those fears are unjustified, but understandable.


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    13 Views
    Every major version is a milestone, and 8.0.0 is no exception. Your WordPress blog just became a two-way street in the Fediverse. Visitors can like and boost your posts directly on your site. Media from federated replies is handled more reliably, and new block patterns make it easy to drop ActivityPub features into your pages.Like and Boost, Right From Your BlogThe Fediverse Reactions block now has optional Like and Boost action buttons, inline with each reaction group. When a visitor clicks one, a modal opens where they can enter their Fediverse handle or copy the post URL to interact from their home server.The plugin remembers the visitor’s profile in their browser, so the second time around it’s even faster. And for folks who aren’t familiar with how the Fediverse works, each modal now includes a collapsible “Why do I need to enter my profile?” help section that explains the open social web in plain language.This dramatically lowers the friction for cross-platform engagement.Block Patterns and TemplatesSetting up a Fediverse-ready profile page used to mean manually assembling Follow Me, Extra Fields, and Followers blocks. Not anymore.We’ve added a “Fediverse” block pattern category with four pre-configured layouts:Author Profile with Follow, a compact profile card.Fediverse Follow Page, a full-page follow experience.Author Header with Follow, great for author archive headers.Fediverse Sidebar, drop it into any sidebar or widget area.If you’re running a block theme on WordPress 6.7+, there’s also a new Author Archive (Fediverse) block theme template ready to go.Publish Smarter With Post Format SuggestionsA new pre-publish panel now analyzes your post content and suggests an appropriate post format when your object type is set to “Post Format.” Got a post that’s mostly images? It’ll nudge you toward the Image format. A video post? Video format.This matters because media-focused Fediverse platforms like Pixelfed and Vernissage display Notes differently than Articles, so choosing the right format means your content looks its best everywhere it lands.Community SnippetsWe’ve added a snippets/ folder to the GitHub repository, a home for lightweight, community-contributed extensions that don’t belong in the core plugin but are too useful to lose. The first batch includes:FediBlog Tag, automatically adds #FediBlog to standard blog posts for better Fediverse discovery.Locale from Tags, derives post locale from taxonomy tags.Bot Account, marks your profile as automated and displays a “BOT” badge in the Fediverse.Blockless ActivityPub, renders Fediverse reactions as pure server-side HTML, no JS required.Photon CDN, serves cached remote media through Jetpack’s Photon CDN for faster delivery.Got a snippet of your own? Check out the snippets folder and send a PR.Smarter Media CachingUnder the hood, we’ve rebuilt how the plugin handles remote media, avatars, emoji, images, audio, and video from across the Fediverse. Instead of importing everything into the WordPress Media Library at insert time, media is now wrapped in custom blocks and cached lazily at render time.What does that mean for you? Faster processing of incoming content, less disk usage, and better rendering of audio and video attachments. Original remote URLs are preserved in block attributes, so caches can be regenerated without data loss. If you’re using Jetpack’s Site Accelerator, that works too, the new system is built filter-first.For site admins, there are new CLI commands to keep things tidy:wp activitypub cache statuswp activitypub cache clearMinimum PHP 7.4With WordPress 7.0 deprecating PHP 7.2 and 7.3, we’ve raised the minimum requirement to PHP 7.4. This lets us clean up compatibility polyfills and use more modern PHP features going forward. If you’re still on an older version, update your PHP before updating the plugin.ChangelogAddedAdd a help section to interaction dialogs explaining the Fediverse and why entering a profile is needed.Add a notice on the Settings page to easily switch from legacy template mode to automatic mode.Add a pre-publish suggestion that recommends a post format for better compatibility with media-focused Fediverse platforms.Add a Site Health check that warns when plugins are causing too many federation updates.Add backwards compatibility for the ACTIVITYPUB_DISABLE_SIDELOADING constant and activitypub_sideloading_enabled filter from version 7.9.1.Add bot account snippet that marks ActivityPub profiles as automated accounts, displaying a “BOT” badge on Mastodon and other Fediverse platforms.Add Cache namespace for remote media caching with CLI commands, improved MIME validation, and filter-based architecture.Add federation of video poster images set in the WordPress video block.Add Locale from Tags community snippet.Add optional Like and Boost action buttons to the Fediverse Reactions block, allowing visitors to interact with posts from their own server.Add pre-built Fediverse block patterns for easy profile, follow page, and sidebar setup.Add snippet for blockless fediverse reactions.Add wp activitypub fetch CLI command for fetching remote URLs with signed HTTP requests.ChangedImproved active user counting for NodeInfo to include all federated content types and comments.Improve language map resolution to strictly follow the ActivityStreams spec.Superseded outbox activities are now removed instead of kept, reducing clutter in the outbox.The minimum required PHP version is now 7.4.FixedAccept incoming activities from servers that use standalone key objects for HTTP Signatures.Fix a crash on servers where WordPress uses FTP instead of direct file access for media caching.Fix a crash when receiving posts from certain federated platforms that send multilingual content.Fix automatic cleanup of old activities failing silently on sites with large numbers of outbox, inbox, or remote post items.Fix comment count to properly exclude likes, shares, and notes.Fix follow button redirect from Mastodon not being recognized.Fix modal overlay not covering the full screen on block themes.Fix outbox invalidation canceling pending Accept/Reject responses to QuoteRequests for the same post.Fix QuoteRequest handler to derive responding actor from post author instead of inbox recipient.Fix reactions block buttons inheriting theme background color on classic themes.Fix reactions block layout on small screens and remove unwanted button highlight when clicking action buttons.Fix signature verification rejecting valid requests that use lowercase algorithm names in the Digest header.Fix soft-deleted posts being served instead of a tombstone when the post is re-saved.Improve compatibility with federated services that use a URL reference for the actor’s public key.Improve handling of all public audience identifiers when sending activities to followers and relays.Prevent private recipient lists from being shared when sending activities to other servers.Get ItDownload from WordPress.org or grab it on GitHub. Remember to check your PHP version first — 7.4 or higher is now required.A huge thank you to everyone who contributed code, testing, bug reports, and ideas to this release. Special thanks to @kraft, @jeremy, and @futtta for their snippet contributions.Update, try out those Like and Boost buttons, and let us know what you think — what’s the feature you’ve been waiting for? What would you like to see next?
  • 0 Votes
    12 Posts
    65 Views
    Woo hoo! Glad to hear it, and welcome to the threadiverse!
  • 0 Votes
    9 Posts
    31 Views
    @CathyBikesBook yes it does: https://social.coop/@afewbugs/115939671693725591
  • Nice video from @docpop

    Fediverso fediverse
    1
    0 Votes
    1 Posts
    18 Views
    Nice video from @docpop What is the #Fediverse ?https://www.youtube.com/watch?v=QzYozbNneVc