Chebucto Regional Softball Club

[ska](https://community.nodebb.org/user/ska) there is an issue with category sync with Lemmy, since they do not support categories following their communities. https://github.com/LemmyNet/lemmy/issues/5354 I'll have to take a closer look at Peertube. Are you able to follow those users using your local account, not via the ACP?

[Furbland-Channel-2](https://community.nodebb.org/user/furbland-channel-2) could have a follow request time out after some time...?

[dansup@mastodon.social](https://community.nodebb.org/user/dansup%40mastodon.social) are you interested in getting reply backfill working with Pixelfed? Let's chat at FediCon cc [jesseplusplus@mastodon.social](https://community.nodebb.org/user/jesseplusplus%40mastodon.social)

[jesseplusplus@mastodon.social](https://community.nodebb.org/user/jesseplusplus%40mastodon.social) [silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) I think the ordering would be nice but even if an OrderedCollection was sent back I don't know if you can trust the order of items as received. I wouldn't want to introduce a hard requirement on it being an OrderedCollection, personally.

[jesseplusplus@mastodon.social](https://community.nodebb.org/user/jesseplusplus%40mastodon.social) yeah that's the thing. I think the solution for me is to loosen the restriction and handle cases where the object isn't represented locally.

[jesseplusplus@mastodon.social](https://community.nodebb.org/user/jesseplusplus%40mastodon.social) one technical issue I came across was that a context could potentially provide object ids that temporarily or permanently do not resolve. That caused issues because internal NodeBB logic required that every `inReplyTo` referenced a valid id... So everything following that branch didn't end up making it in. Not sure if you experienced anything similar.

[jesseplusplus@mastodon.social](https://community.nodebb.org/user/jesseplusplus%40mastodon.social) this is **awesome**!! I have to give this a spin against NodeBB tomorrow!!

> Getting a critical mass of people to create yet another account was always a major obstacle. I see and have experienced this effect time and time again, and we're getting closer and closer to the point where the protocol implementations can abstract away the messy bits. Gaining critical mass among devs is the first step!

> We have the potential to create something far more human and revolutionary than any of the ad-based mainstream platforms. Right on! That's the refrain I hear a lot from people who discover ActivityPub and then build software for it. Building something out of principle is a wonderful approach. I hope someday were in a position so that you don't have to sacrifice principles to make money.

This question was asked by [mike@flipboard.social](https://community.nodebb.org/user/mike%40flipboard.social) on Dot Social's latest episode about the blogosphere on Fedi. [johnonolan@mastodon.xyz](https://community.nodebb.org/user/johnonolan%40mastodon.xyz): "we wanted to connect Ghost blogs to each other, but then we discovered ActivityPub" [pfefferle@mastodon.social](https://community.nodebb.org/user/pfefferle%40mastodon.social): "we wanted to connect WordPress blogs to each other, and ActivityPub has been the most successful attempt" _[paraphrased for brevity]_ Did you catch the subtext? Both those answers, and **my own answer with NodeBB** contain the same seed idea... that we originally wanted to connect our software **with itself only**. We went through years of building a company and vying for profitability that it never occurred to us to work towards cross compatibility with anyone besides out own software. Then ActivityPub came along and quite literally expanded the potential for the entire endeavour a hundred-fold, because not only are you connecting your own software to each other, but every other ActivityPub enabled software in existence. Blogs, microblogs, forums, image boards, etc. all with a built-in user base ready from the get-go. It's no wonder that after discovering AP, it becomes _the_ protocol to utilise.

I suppose you're right in a way. The context owner is not supposed to be set by someone other than the context owner. It's a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn't same origin to the author, then no category is assumed.

[silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) yes, it should. Mentioning the category means it will be addressed and NodeBB will slot the received content in the first group object it finds.

[projectmoon@forum.agnos.is](https://community.nodebb.org/user/projectmoon%40forum.agnos.is) it'll work better once cross-posting is built into NodeBB I think

[silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) do you still need to if you're not using a shared inbox?

Hi [robz@toot.robzazueta.com](https://community.nodebb.org/user/robz%40toot.robzazueta.com)! This could be related to some better support for non-`Note` types introduced by Mastodon in later versions. Your instance is running v4.1.18 which is 11 months behind the latest version. That isn't necessarily cause for concern, but I think that might be why you're seeing the HTML tags?

[trwnh@mastodon.social](https://community.nodebb.org/user/trwnh%40mastodon.social) thanks, I've updated them to add the protocol. I guess you can't rely on support for protocol-relative URLs everywhere

In February 2025, I presented a topic at FOSDEM in Brussels entitled [The Fediverse is Quiet — Let's Fix That!](https://spectra.video/w/xwCSYfZh1mJY64zJ9GngbE) In it, I outlined several "hard problems" endemic to the fediverse, focusing on one particular complaint that is often voiced by newcomers and oldtimers alike; that the fediverse is quiet because you don't ever see the full conversation due to some design considerations made at the protocol level. Since then there have been a number of approaches toward solving this problem, and it is worth spending the time to review the two main approaches and their pros and cons. _N.B. I have a conflict of interest in this subject as I am a proponent of one of the approaches (FEP 7888/f228) outlined below. **This article should be considered an opinion piece.**_ ---- ## Crawling of the reply tree First discussed 15 April 2024 and merged into Mastodon core on 12 Mar 2025, [jonny@neuromatch.social](https://community.nodebb.org/user/jonny%40neuromatch.social) pioneered this approach to "fetch all replies" by crawling the entirety of the reply tree. When presented with an object, the Mastodon service would make a call to the `context` endpoint, and if supported(?) would start to crawl the reply tree via the `replies` collection, generating a list of statuses to ingest. This approach is advantageous for a number of reasons, most notably that `inReplyTo` and `replies` are **properties that are ubiquitous** among nearly all implementations and their usage tends not to differ markedly from one another. _N.B. I am not certain whether the service would crawl *up* the `inReplyTo` chain first, before expanding downwards, or whether `context` is set in intermediate and leaf nodes that point to the root-level object._ One disadvantage is this approach's **susceptibility to network fragility**. If a single node in the reply tree is temporarily or permanently inaccessible, then every branch of the reply tree emanating from that node is inaccessible as well. Another disadvantage is the reliance on intermediate nodes for indexing the reply tree. The amount of work (CPU time, network requests, etc.) scales linearly with the size of the reply tree, and more importantly **discoverability of new branches of the reply tree necessitate a re-crawl of the entire reply tree**. For fast-growing trees, this may not net you a complete tree depending on when you begin crawling. Lastly, in the ideal case, a full tree crawl would net you a complete tree with all branches and leaves. Great! Mastodon is the sole implementor of this approach, although it is not proprietary or special to Mastodon by any means. ## FEP 7888/f228, or FEP 171b/f228 Summarized by [silverpill@mitra.social](https://community.nodebb.org/user/silverpill%40mitra.social) in [FEP f228](https://community.nodebb.org//w3id.org/fep/f228) (as an extension of FEPs [7888](https://community.nodebb.org//w3id.org/fep/7888) by [trwnh@mastodon.social](https://community.nodebb.org/user/trwnh%40mastodon.social) and [171b](https://community.nodebb.org//w3id.org/fep/171b) by [mikedev@fediversity.site](https://community.nodebb.org/user/mikedev%40fediversity.site)), this conversational backfill approach defines the concept of a "context owner" as referenced by compatible nodes in the tree. This context owner returns an `OrderedCollection` containing all members of the context. A major advantage of this approach centers around the pseudo-centralization provided by the context owner. This "single source of truth" maintains the index of objects (or activities) and supplies their IDs (or signed full activities) on request. Individual implementations then retrieve the objects (or activities). It is important to note that **should the context owner become inaccessible, then backfill is no longer possible to achieve**. On the other hand, a dead or unresponsive intermediate node will not affect the ability of the downstream nodes to be processed. The context owner is only able to respond with a list of objects/activities that it knows about. This does mean that downstream branches that do not propagate upwards back to the root will not be known to the context owner. Additionally, consumers are also able to query the context owner for an index without needing to crawl the entire reply tree. The ability to de-duplicate objects at this level reduces the overall number of network requests (and CPU time from parsing retrieved objects) required, **making this approach relatively more efficient**. Additional synchronization methods (via id hashsums) could be leveraged to reduce the number of network calls further. A number of implementors follow this approach to backfill, including NodeBB, Discourse, WordPress, Frequency, Mitra, and Streams. Additional implementors like Lemmy and Piefed have expressed interest. One technical hurdle with this approach is technical buy-in from implementors themselves. Unlike crawling a reply tree, this approach only works when the context owner supports it, and thus should be combined with various other backfill strategies as part of an overall conversational backfill solution. ## Conclusion 2025 is shaping up to be an exciting year for resolving some of the harder technical and social problems endemic to the open social web/fediverse. It is this author's opinion that we may be able to make good headway towards resolving the "quiet fedi" problem with these two approaches. It is important to note that **neither approach conflicts with the other**. Implementations are free to utilise multiple approaches to backfill a conversation. Both methods presented here have pros and cons, and a combination of both (or more) could be key. Feel free to use this as a starting point for discussions regarding either approach. Does one speak to you more than the other? Are the cons of either approach significant enough for you to disregard it? What other approaches or changes could you recommend?

[scott@loves.tech](https://community.nodebb.org/user/scott%40loves.tech) Mastodon does not use summary as content warning for Articles.

[scott@loves.tech](https://community.nodebb.org/user/scott%40loves.tech) that's probably it, if it started in the past few weeks.

That's odd, we don't produce bbcode, where did it come from?