Live testing of remote categories

[Guest]

@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

[julian@community.nodebb.org]

@[email protected] since Hubzilla posts (incl. yours) are making it in fine I'm assuming this is only for the "forum" feature?

[Guest]

@julian right.

[scott@loves.tech]

@Mario Vavti If we exposed the original author to the Hubzilla UI as a variable and via Zot and ActivityPub, it would allow the UI to display the author of the first post instead of or in addition to the name of the forum.

I understand that on the backend it may be desirable to have the first post in a forum owned by the forum for backwards compatibility with platforms that don't support groups, but the UI does not have to display the first post with the forum as the author. We have the information about the author of the first post, so might as well display it.

[scott@loves.tech]

@Mario Vavti @julian Another compatibility issue that we may need to look at is permissions to post. Hubzilla can restrict posts and comments to only being from people following the forum, for example. It also has a moderated mode, which will accept posts from unknown actors, but will place it in a moderation queue. So it may be desirable to turn off the ability to comment if the permissions to comment are not permitted for a particular actor.

[Guest]

@Scott M. Stolz i think this would be very misleading. But this discussion does not belong here.

[scott@loves.tech]

@Mario Vavti Okay. Deleting the post.

[Guest]

@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: #^https://community.nodebb.org/topic/cbbf1640-2295-4fc5-b86f-5b1fd259cccb/test2

@Scott M. Stolz

[julian@community.nodebb.org]

@[email protected] that's wonderful to hear! Thank you so much.

[Guest]

Some of the remote categories appear to be broken now.

These are the Flipboard magazines NodeBB is currently aware of when searching "flipboard" in the search page:

• [Tech News by @[email protected]](https://community.nodebb.org/category/[email protected])
• [Musik News by @[email protected]](https://community.nodebb.org/category/[email protected])
• [Gear by @[email protected]](https://community.nodebb.org/category/[email protected])

However, that very first one (tech news by The Verge) does not work; going to it gives a 404 page instead.

---

Something else appears to have happened to the Vivaldi Blog remote category (a WordPress blog). A week ago it was working fine, but now, searching for it lists it twice in the search page. Each listing indicates a completely different number of posts and topics for the remote category.

Even weirder though most of the topics that are correctly slotted into it, they are not actually in the category page, e.g. https://community.nodebb.org/topic/a85b0eff-5219-46ba-9ad4-a5d417a7bec5/minor-update-2-for-vivaldi-desktop-browser-7.3

[Guest]

Actually, I think I know what's going on with the Vivaldi blog group actor - it's not necessarily NodeBB's fault.

Inspecting the AP objects coming from vivaldi.com/blog, all the English-written blog posts have their as:audience field set to https://vivaldi.com/?author=0.

Meanwhile, every other blog post that is written in a different language instead have it set to https://vivaldi.com//?author=0, so for Japanese blog posts, for example, it is https://vivaldi.com/ja/?author=0.

And all these URLs link to different group actors, but all of them have the same value on the preferredUsername and webfinger properties: blog, and [email protected].