0

Pre-Alpha ActivityPub-related bug reports

preview

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable 😅

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable 😅

0

Notifications on remote interactions

preview

ActivityPub gives us the ability to send different activities (hence the name) across services.

Activities from remote users for three of those activities will now notify your local account:

  • When someone likes your post (rendered as an upvote)
  • When someone follows you
  • When someone shares your post with their followers (shown as an event in-topic)

Those items were already notifying you (with exception of the last, which had no local equivalent), but now these notifications will also occur when involving users outside of the local NodeBB.

Replies to topics you follow currently do not notify you yet, as the logic behind that calculation is a tad more complicated, but will be the next item on the docket.

ActivityPub gives us the ability to send different activities (hence the name) across services.

Activities from remote users for three of those activities will now notify your local account:

  • When someone likes your post (rendered as an upvote)
  • When someone follows you
  • When someone shares your post with their followers (shown as an event in-topic)

Those items were already notifying you (with exception of the last, which had no local equivalent), but now these notifications will also occur when involving users outside of the local NodeBB.

Replies to topics you follow currently do not notify you yet, as the logic behind that calculation is a tad more complicated, but will be the next item on the docket.

0

Hashtags are now supported in the NodeBB-ActivityPub integration

preview

Content discoverability is a topic that comes up occasionally in fediverse-related discussions, as many of the big ActivityPub implementations don't automatically curate posts for their users. Following other users is the easiest way to discover more content, but using hashtags is another, as they can be easily searched.

NodeBB supports hash tagging at the topic level, and so today's update will automatically tag any incoming topics, and federate out hashtags for the OP only.

Unlike other implementations, however, there is no local capability to tag posts, and so hashtags used in replies will not federate out.

Content discoverability is a topic that comes up occasionally in fediverse-related discussions, as many of the big ActivityPub implementations don't automatically curate posts for their users. Following other users is the easiest way to discover more content, but using hashtags is another, as they can be easily searched.

NodeBB supports hash tagging at the topic level, and so today's update will automatically tag any incoming topics, and federate out hashtags for the OP only.

Unlike other implementations, however, there is no local capability to tag posts, and so hashtags used in replies will not federate out.

0

Normalization of mention spam in the fediverse

preview

On the eve of me working on federating out mentions from NodeBB, I've started thinking again about how they're used in the fediverse via Mastodon. I've gone on at length about this before, but it bears repeating again:

I think it's absolutely bonkers that replies dogpile mentions just so participants stay in the loop.

It has the unfortunate side-effect of looping people in to a conversation merely because they were mentioned. The even worse side-effect is that if you don't follow along with this convention, the people who are left out simply aren't notified and drop from the conversation. Awful UX!

Mastodon does it because other than a follow, like, or a boost, a mention is the only other way to land a Note into your notifications. So you'll see exchanges where multiple users all start (or end) their posts with a string of mentions as they're having an ad-hoc group conversation.

@foobarbaz @barbaz @quux did you hear about the latest news out of...

This doesn't happen in forums, mostly because if you interact with a topic, the baseline expectation is that you're subscribed to that topic in the future. Replies get sent to your notification box or other dedicated UI widget, and you can easily keep track of your long-running conversations.

In NodeBB, a response within a topic causes the user to automatically follow the topic. Future actions in that topic notify all followers. We collapse related notifications to limit noise, though that is an oft-cited concern against throwing things in a notification inbox.

It sounds like I'm hating on Mastodon, and it's easy for me to do because they're the big fish in the fedi sea, but I still feel this isn't something that needs to exist. Mastodon could potentially create their own dedicated list for "conversations you've interacted with".

I will admit, though, that it is a lot easier to present that data when reply chains are grouped into topics :slightly_smiling_face:

On the eve of me working on federating out mentions from NodeBB, I've started thinking again about how they're used in the fediverse via Mastodon. I've gone on at length about this before, but it bears repeating again:

I think it's absolutely bonkers that replies dogpile mentions just so participants stay in the loop.

It has the unfortunate side-effect of looping people in to a conversation merely because they were mentioned. The even worse side-effect is that if you don't follow along with this convention, the people who are left out simply aren't notified and drop from the conversation. Awful UX!

Mastodon does it because other than a follow, like, or a boost, a mention is the only other way to land a Note into your notifications. So you'll see exchanges where multiple users all start (or end) their posts with a string of mentions as they're having an ad-hoc group conversation.

@foobarbaz @barbaz @quux did you hear about the latest news out of...

This doesn't happen in forums, mostly because if you interact with a topic, the baseline expectation is that you're subscribed to that topic in the future. Replies get sent to your notification box or other dedicated UI widget, and you can easily keep track of your long-running conversations.

In NodeBB, a response within a topic causes the user to automatically follow the topic. Future actions in that topic notify all followers. We collapse related notifications to limit noise, though that is an oft-cited concern against throwing things in a notification inbox.

It sounds like I'm hating on Mastodon, and it's easy for me to do because they're the big fish in the fedi sea, but I still feel this isn't something that needs to exist. Mastodon could potentially create their own dedicated list for "conversations you've interacted with".

I will admit, though, that it is a lot easier to present that data when reply chains are grouped into topics :slightly_smiling_face: