NodeBB v4.8.0 — Crossposting, federated moves, API changes, and bug fixes!
Fediverse
2
Posts
2
Posters
2
Views
-
cross-posted from: https://community.nodebb.org/post/106480
NodeBB v4.8.0 — Crossposting, federated moves, API changes, and bug fixes!
Hello from Canada! :flag-ca:
We're a week behind the planned release, but we're dropping v4.8.0 today, containing some changes to our ActivityPub handling, along with a new API route, and bug fixes.
Crossposting
As briefly introduced in my earlier topic on cross-posting, NodeBB v4.8.0 supports cross-posting of topics between categories. More importantly, it means topics from other remote categories can now be added to local categories, which is another way to bring conversations to your local users.
Unlike before, where administrators were the only ones allowed to move topics from cid -1, cross-posting is available to all local users. If you see a topic on the fediverse you'd like to cross-post to a local category, just hit the cross-post button (it's a button with a little upward-right pointing arrow), and share it with other users on your forum!
When you cross-post, it also shares the topic with all of your followers from outside of your forum.
Federated topic moving and removals
This was actually released with v4.7.0 but was improved slightly in the intervening versions. NodeBB now follows the Draft FEP f15d: Context Relocation and Removal and will publish
Removeactivities when a topic is moved to "Uncategorized", andMoveactivities when moved to another category.Developers of other ActivityPub software looking to implement similar mechanics are advised to read the FEP and provide feedback here: https://activitypub.space/topic/86/fep-f15d-context-relocation-and-removal
Other technical debt and bug fixes
- Post ownership websocket call was migrated to a v3 REST API call
- Notifications had issues when user display names contained commas
- Piefed v1.5 supports emoji from remote instances; incoming custom emoji from Piefed are now handled
- Nodeinfo fixes for if a NodeBB instance is not actually federating (has AP turned off)
-
cross-posted from: https://community.nodebb.org/post/106480
NodeBB v4.8.0 — Crossposting, federated moves, API changes, and bug fixes!
Hello from Canada! :flag-ca:
We're a week behind the planned release, but we're dropping v4.8.0 today, containing some changes to our ActivityPub handling, along with a new API route, and bug fixes.
Crossposting
As briefly introduced in my earlier topic on cross-posting, NodeBB v4.8.0 supports cross-posting of topics between categories. More importantly, it means topics from other remote categories can now be added to local categories, which is another way to bring conversations to your local users.
Unlike before, where administrators were the only ones allowed to move topics from cid -1, cross-posting is available to all local users. If you see a topic on the fediverse you'd like to cross-post to a local category, just hit the cross-post button (it's a button with a little upward-right pointing arrow), and share it with other users on your forum!
When you cross-post, it also shares the topic with all of your followers from outside of your forum.
Federated topic moving and removals
This was actually released with v4.7.0 but was improved slightly in the intervening versions. NodeBB now follows the Draft FEP f15d: Context Relocation and Removal and will publish
Removeactivities when a topic is moved to "Uncategorized", andMoveactivities when moved to another category.Developers of other ActivityPub software looking to implement similar mechanics are advised to read the FEP and provide feedback here: https://activitypub.space/topic/86/fep-f15d-context-relocation-and-removal
Other technical debt and bug fixes
- Post ownership websocket call was migrated to a v3 REST API call
- Notifications had issues when user display names contained commas
- Piefed v1.5 supports emoji from remote instances; incoming custom emoji from Piefed are now handled
- Nodeinfo fixes for if a NodeBB instance is not actually federating (has AP turned off)
Oh hey, thanks! You saved me from needing to crosspost it here :laughing:
... which... is frickin' ironic, isn't it, because we aren't at the point where we can crosspost between instances yet...
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Oh hey, thanks! You saved me from needing to crosspost it here :laughing:
... which... is frickin' ironic, isn't it, because we aren't at the point where we can crosspost between instances yet...
-
cross-posted from: https://community.nodebb.org/post/106480
NodeBB v4.8.0 — Crossposting, federated moves, API changes, and bug fixes!
Hello from Canada! :flag-ca:
We're a week behind the planned release, but we're dropping v4.8.0 today, containing some changes to our ActivityPub handling, along with a new API route, and bug fixes.
CrosspostingAs briefly introduced in my earlier topic on cross-posting, NodeBB v4.8.0 supports cross-posting of topics between categories. More importantly, it means topics from other remote categories can now be added to local categories, which is another way to bring conversations to your local users.
Unlike before, where administrators were the only ones allowed to move topics from cid -1, cross-posting is available to all local users. If you see a topic on the fediverse you'd like to cross-post to a local category, just hit the cross-post button (it's a button with a little upward-right pointing arrow), and share it with other users on your forum!
When you cross-post, it also shares the topic with all of your followers from outside of your forum.
Federated topic moving and removalsThis was actually released with v4.7.0 but was improved slightly in the intervening versions. NodeBB now follows the Draft FEP f15d: Context Relocation and Removal and will publish Remove activities when a topic is moved to "Uncategorized", and Move activities when moved to another category.
Developers of other ActivityPub software looking to implement similar mechanics are advised to read the FEP and provide feedback here: https://activitypub.space/topic/86/fep-f15d-context-relocation-and-removal
Other technical debt and bug fixes Post ownership websocket call was migrated to a v3 REST API call Notifications had issues when user display names contained commas Piefed v1.5 supports emoji from remote instances; incoming custom emoji from Piefed are now handled Nodeinfo fixes for if a NodeBB instance is not actually federating (has AP turned off)
-
@die4ever@thefedi.forum hi from another NodeBB! (god this will never get old)
NodeBB maintainer here. Glad to hear you're enjoying the software! I really tried to make it so that federation is rather seamless. There's a lot of work to be done with respect to discovery, so it'll only get better over time 🙂
-
That all sounds pretty gloomy, on the whole.
If Lemmy.ml's founders didn't have such a controversial reputation, I'd be a lot more sanguine about all that...
-
You seem more familiar with Mastodon than me:-).
I think there’s another wrinkle, too, about PF communities not showing up in Lemmy feeds unless a local instance user has subscribed to them.
Mostly this is just how the Threadiverse is designed to work. PieFed might do differently, but Lemmy has always been this way. That said, it is reportedly about to get worse/better (at the same time) as the choice as to what communities will show up for new instances will now fall under the centralized authority of Lemmy.ml directly - so e.g. anything defederated from it will no longer be considered part of the Threadiverse, at least by default (although that's easy enough to override by adding the community manually). It is notable though that previously I believe zero communities were added by default, at least automatically (and yet when that update deploys and some do, it will only get more confusing to find out why some instances, decided by Lemmy.ml to not be worthy by their criteria, will not be part of that). It is also far more confusing than I let on here, and in ways that I do not fully know myself, since just because an instance is "aware" of a community does not mean that it is "subscribed" to it.
There is simply no way that the federated model is anything at all like "just using email", as people claim. The defederations make it an entirely different thing where instead of having a fully connected graph we have only a partially connected one.
-
Oh this is cool!
-
Lemmy and PieFed are both part of the Threadiverse though, whereas things like Mastodon, Loops, and Friendica are not. Since none of the latter have “communities”, e.g. in Mastodon you have to follow “people”, rather than community topics to be discussed by many people.
Okay, but Mastodon does have a general feed I think, similar to the "ALL" stream. Doesn't it also allow following hashtags, too?
Even between PieFed and Lemmy there is a lot that can be sent out by the former that the latter simply is not capable of receiving properly, like hashtags, polls, user and community flairs, and so on.
I think there's another wrinkle, too, about PF communities not showing up in Lemmy feeds unless a local instance user has subscribed to them.
-
Lemmy and PieFed are both part of the Threadiverse though, whereas things like Mastodon, Loops, and Friendica are not. Since none of the latter have "communities", e.g. in Mastodon you have to follow "people", rather than community topics to be discussed by many people.
These fundamental differences can make it difficult to share content between platforms, even though it can be done. e.g. I think in Mastodon (iirc, I have never used it personally) you have to tag the community name as if it were a person.
Even between PieFed and Lemmy there is a lot that can be sent out by the former that the latter simply is not capable of receiving properly, like hashtags, polls, user and community flairs, and so on. Likewise some input can be filtered too, e.g. votes prevented on a PieFed community not only based on if someone is banned or not (from either the instance or the community itself) but whether they are a subscribed member of that community, if the community rule is set up that way (e.g. women's communities where men might not bother reading the rules, say by just seeing something while browsing by All, and attempt e.g. vote manipulation, even/especially unintentionally).
So anyway, despite all the differences, PieFed and Lemmy at least are operating on roughly the same wavelength, but e.g. Loops is an entirely separate thing.
