Happy Tuesday!
Today we’ve updated the NodeBB community forum onto the remote-categories
testing branch, which means that users on the open social web that identify themselves as “Groups” will be rendered in NodeBB as categories. Prior to this, they looked like users.
Here are some examples of remote categories:
- Comic Strips (on lemmy.ml)
- Star Trek Social Club (on startrek.website)
- Social Web Foundation (a WordPress blog)
ActivityPub “groups” and forum categories have quite a few things in common — they don’t usually post topic themselves, they “contain” topics, and they are usually administered by a separate group of users (moderators!) In many ways, these groups lend themselves to categories much more easily than they do as users.
Notes:
- We will likely be releasing this as v4.3.0-alpha this Wednesday. Probably this means you don’t want this on a live forum just yet.
- A lot of the backend logic is complete, but a lot of the frontend UX will be worked on.
- You can “search” for categories (via “in categories” in the search page), paste the full handle in order to instruct NodeBB to pull a new category in.
- You can now no longer mention a remote category. Instead, create your topic right in that category itself. As it should be :smirk_cat: .
- Remote content coming in that is slotted into a remote category will still show up in your “world” feed. That is still intended to be where discovery of content outside the local NodeBB instance will take place.
- Report any bugs or confusing behaviours (and there will be some) here.
@scott@loves.tech Hubzilla is formatting its Notes in a manner I wasn’t expecting.
attributedTo
, which is not possible in NodeBBSo at present while I would be able to retrieve the note, without a proper backreference to the group actor, I don’t think I can slot it correctly.
Not sure why the received activity is returning a 403, as well.
@julian we have recently rewritten the addressing logic and it seems mapping the mentions to
to
for public toplevel posts has fallen short. After fixing this it seems to work fine now: #[1](https://community.nodebb.org/topic/cbbf1640-2295-4fc5-b86f-5b1fd259cccb/test2)@Scott M. Stolz
https://community.nodebb.org/topic/cbbf1640-2295-4fc5-b86f-5b1fd259cccb/test2 ↩︎
@mario@hub.somaton.com that’s wonderful to hear! Thank you so much.
@julian in Hubzilla the group actor will fork the original post with a quote reshare. Hence
attributedTo
is set to the group actor. IIRC the author of the original post is being stored for refernce but we currently do not use this info.@Scott M. Stolz
deleted by creator
deleted by creator
@Scott M. Stolz i think this would be very misleading. But this discussion does not belong here.
@Mario Vavti Okay. Deleting the post.
@mario@hub.somaton.com since Hubzilla posts (incl. yours) are making it in fine I’m assuming this is only for the “forum” feature?
@julian right.
@julian @Mario Vavti That is one thing that I wish Hubzilla did, and that is identify the author of the original note (top level post in a forum), both internally in the database and in a variable available to themes, and externally via Zot protocol and ActivityPub.
@julian I saw a NodeBB test on Hubzilla Monster. I’m guessing that was you.
In order for you to properly mention someone, the Hubzilla server needs to know about that actor first. The easiest way to achieve this is to follow (connect to) that actor. This adds the actor to the database. This only needs to be done if no one on the server is following them or being followed by them.
This does create an extra step if the actor is unknown to the server, but it does force spammers to follow unknown actors before they can mention them.
Forgot to cc @mario@hub.somaton.com re: the above.