Does anyone know what the most broadly implemented standard is for signalling that a web page has an alternative ActivityPub endpoint?

What I found online (and with @[email protected] and @[email protected]'s input) was to deliver a Link header and set a <link> tag, but it doesn't seem to work (at least with Megalodon)...

Oh nice! Following a #WordPress blog using #nodebb is working like a charm!

Good job @julian

#fediverse #activitypub

Link Preview Image

Simple plugin to embed tweets using tweet URL.
https://github.com/dovydaskukalis/nodebb-plugin-twitter

Hi,

I haven't been able to get group badges to work - I've added the group, added 2 members but nothing shows up in forum posts, the way there do here.

On the users' 'Edit Profile' page there's a 'Group Title' heading just below 'birthday' and above 'about me', but there's nothing else there. This only appears when the user is added to the group. My understanding is this is how users 'enable' their badges.

I've tried with both admin and non-admin users, and I don't have many plugins activated - just sendmail and dbsearch. Not the polling one that was causing other users problems with groups anyway.

The group is private and hidden because I want it to be invite only.

'Show badge' is enabled.

I'm on a fairly recent build, just one behind the latest I believe.

Any ideas?

Bye!
Mark

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 publish an error version and then i unpublish it when i find has some error. Now I have to wait 24 hours to republish the version.
I saw the plugin version is error version about this plugin on list. It will be updated after for a while or not? If not, please help me to fix it. Thanks. 😧

This might be useful for the user - what do people think?

A dedicated Activitypub filter in categories view

0 - All posts mixed in topic listing view (current default)
1 - removes activity pubs post from listing view
2 - display only Activitypub post in listing view

Right now (I never knew this till I checked), you can alt-click (Mac) whatever grouping of categories you want listed, but when you want to just take out the non-native ActivityPub stuff, I can't see how to do this.

As I type I'm wondering maybe then perhaps a grouping feature, where a user can make their own filter groups for viewing listings might be the cool solution. However I don't want to overcomplicate anything. There is similar in Discourse and I never use it.

I do think for the UX clear differentiation actions and points need to be available to the user, espcially if blending in ActivityPub content in with native forum content.

For a fast solution this perhaps this could be handled and tucked into the "All Topic" filter button, with at leat two new options:

exclude activitypub posts show activitypub post only

Maybe allowing that then be the users default until they change it.

Is anyone using WeChat to scan and log in? The plugin seems to be malfunctioning. Does anyone have a solution? Thx.
Plugin: https://github.com/NodeBB-China/nodebb-plugin-sso-wechat-web

My scene description:
If I copy content from other web pages into the editor, it is usually a mixture of text and images on the web page, and I find that images cannot be uploaded, only text can be pasted. I need to upload pictures one by one, which is very troublesome.

The help I need:
How to automatically upload pasted images after pasting content into the editor? Thx.

i will not rest until fedi devs start using as:context properly. this is my single-issue. /hj

To refresh your memory, you can read the minutes of last week's meeting.

Please see @[email protected]'s note below regarding agenda preparation for the May WG meeting

Follow up

The Social Web Community Group approved our application to turn this into a Task Force. Async work will happen across any federated platform followed by either (or both) of these categories Category on NodeBB (@[email protected]) Category on SocialHub (@[email protected])

Next Meeting
We're going to have our next meeting in the first week of May.

Time
Please vote in our meeting poll. Whatever time we decide for this one, we'll aim to keep as our regular monthly slot.

Agenda
Please see this google doc. Everyone has comment permission. Julian will incorporate comments into the agenda.

Looking forward to seeing you at the next meeting!

My apologies for the delay. Angus and I have been working these past few weeks to hammer out some federation issues between our respective forum categories (the ones mentioned above re: async work.)

Prior our last task force meeting, @[email protected] brought up the need for a common nomenclature for ease of communication between ActivityPub implementors. Rimu also took the initiative to conduct an informal survey to see what terminology was used across fediverse-capable software (and some non-federating software).

Going beyond "toots" vs "posts", it was noted (not surprisingly) that each software has their own name for things.

The most common object type passed around via the ActivityPub protocol (as:Note) could be called a comment, a post, or a reply A grouping of as:Notes could be a post (!!), a topic, a thread, a conversation, or a discussion A higher order grouping of those could be a community, a category, a forum, a (sub)tag, a group, or a magazine

The main takeaways were that while there was occasional convergence, it wasn't entirely surprising that there were more names for things than things to name. Secondly, it was fairly clear that putting forth a recommendation to align on nomenclature would be fairly futile.

What were we expecting... naming things is, after all, one of the hard problems in computing.

All joking aside, up with a common terminology — a lingua franca (thanks @[email protected]!) — definitely has some advantages.

What terms do you think communicate these levels of organization most succinctly? Let us know!

I have a clarification question for @[email protected] regarding 1b12. There are instances where a group actor may have occasion to announce multiple notes all at once. For example:

New notes discovered while traversing upwards to root — may want to announce all parent notes An existing topic/thread (containing a variable number of notes) is assumed by this group actor (e.g. it was moved to the category/forum).

What would be the expected behaviour from an implementor in that scenario? A single Announce(Collection)? Multiple Announce(Note) in chronological order?

During our testing, @[email protected]
did warn me that a collection was announced, and that caused issues because NodeBB's implementation didn't (and still doesn't) account for that. I believe he changed up the behaviour now.

@[email protected], Angus did mention offline that you warned him about this in the past!

Is there a plugin that will compress images users upload?

It'd be great if the admin can restrict who can upload images based on their reputation.

And with that comes a question. Is it possible for the admin to assign a reputation manually at this time?

Another practical issue @devnull and I faced when integrating NodeBB and Discourse is that the Discourse plugin has been publishing collections of activities to its followers if "Full topic" is enabled (i.e. all posts in a topic will be federated). I built the plugin this way to accommodate an initial publication delay after the first post is made in a topic. Other posts may be made during that delay period, so the thinking being that rather than send multiple POST requests to the followers of that actor at the time of publication, you would just send them a collection of activities. In other words Topic is created. A few posts are made. Publication delay period ends. Publish the topic's full Collection of Activities to followers. As Mastodon also supports processing a collection of activities this seemed to make some sense to me. However, as I think @trwnh warned me, this has not turned out to be popular. There might still be something in this approach, but I'm going to be moving to just publishing sequential activities, even if there are multiple to publish at one time. That said, I think there may be normative support for representing a topic (/thread) as a Collection, so the processing of Collections may become more of a practice in time.

Hi,

i'm quite sure I read a similar question here before but can't find the related topic or remember the answer. I notice that the number of active/online users differ between the online users widget and in the acp. Can someone explain this to me?

ACP:

Screenshot 2024-04-18 at 22-26-41.png

Online users widget:

Screenshot 2024-04-18 at 22-26-06 Kategorien.png

Always wanted to try one but didn't want to pay the premium.

My local co-working space has them so took it for a spin for the tail end of my workday.

Have you tried one? Would you go back?

PXL_20240412_205827831.jpg

Hey @[email protected] — would you be interested in connecting with @Jay-Moonah about having him on a show about the history of podcasting from the POV of one of the founders of Podcamp Toronto? He also founded the Toronto Independent Music Podcast back in 2005.

I was just having a conversation with him offline (how often do we do that nowadays?) and he's got an awful lot to share about podcasting and how far it's come in the years since.

RSS being an open protocol (and podcasting on top of it) sounds like it'd have some overlap with your userbase.

cc @[email protected]

This is a topic to track the FEP-400e and FEP-1b12 reconciliation, aka "How do we handle Groups". I've made this a wiki to let implementers describe their current status quo https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md https://codeberg.org/fediverse/fep/src/branch/main/fep/400e/fep-400e.md Discourse Currently Discourse implements FEP-1b12 to federate posts associated with Category and Tags, i.e. Activities are Announced by a Category or Tag actor. NodeBB NodeBB implements FEP-1b12 to federate posts associated with a category (tag actors TBD). Lemmy Lemmy implements FEP-1b12 [Add your implementation in here]