@[email protected] @[email protected] apologies for butting in. I'd be interested in implementing ed25519 keys instead of RSA.

Backwards compatibility is a concern, however.

I've just merged the activitypub branch of NodeBB into develop, meaning that v4 is on-track to be the next release.

It also means that v3.x has entered feature freeze, and that only bug fixes will be merged/committed at this time.

Exciting stuff!

"The New Next Generation" | Star Trek: Lower Decks | Jammer's Reviews

In-depth critical reviews of Star Trek and some other sci-fi series. Includes all episodes of Star Trek: The Original Series, The Animated Series, The Next Generation, Deep Space Nine, Voyager, Enterprise, Discovery, Picard, Lower Decks, Prodigy, and Strange New Worlds. Also, Star Wars, the new Battlestar Galactica, and The Orville.

(www.jammersreviews.com)

@[email protected]

Mastodon (aka the fediverse)

What

@[email protected]

@Kosiak shadow bans ought to be reserved for spammers.

Also, there is no email field when registering, since it's only after your account is approved that you set an email (after login).

Oh, I'm mistaken about that one. User is prompted for email before they are added to the queue.

@Jordan-Taylor Hi Jordan, can you let me know what the issue is here? Are users approved via the registration queue not properly approved?

Just for full context, welcome and verify_email templates serve an identical function, to verify the email. The copy is different only due to originating context.

That is, the former is sent when a user registers/is approved, while the latter is sent on email change.

NodeBB's topic list layout is great for written and media-light content, although it is less ideal for categories which predominately feature pictures. I recently ran into this issue with the Pics and Trips category on the OpenBeta Community. While we've made some much-needed TLC and improvements so that topic thumbnails are better handled and displayed, I did not feel they were adequately prioritised for this particular category.

So I wrote the Category Masonry plugin for NodeBB!

In brief:

• Configurable; either by category or by percentage of topics with a topic thumbnail/image
• Overrides the partials/topic_list.tpl template to display cards
• Works with custom themes (will correctly override the theme's category.tpl, or the base theme's category.tpl if your theme does not have its own)

@busker Keep in mind that this encompasses uploaded media only. Externally linked media is excluded (so, giphy embeds would be an example that would not be included).

Edit: filter:topics.hasThumbs has been added (in addition to already-added filter:topics.getThumbs) so that plugins can append images to the thumbnail list.

@darkpollo hi there, thanks for bringing this up.

I think this only happened with two language files, user.json and admin-settings-general.json

Can you check if that is the case?

@Jon-Pincus what about @[email protected] ? Testing mention

@[email protected] yeah I wasn't able to get anything across either, but I wasn't sure whether I needed to have my bsky account follow the bridge as well. So I did that but didn't receive a follow back.

Will try again tomorrow I guess!

@[email protected] ah, your instance wasn't updated yet, I was meaning testing from here. That said, I've just updated your instance now.

@busker this is now on-track to be included in NodeBB v4.

feat: append uploaded images into thumbnail set · NodeBB/NodeBB@cc65214

Node.js based forum software built for the modern web - feat: append uploaded images into thumbnail set · NodeBB/NodeBB@cc65214

GitHub (github.com)

Uploaded images are now automatically added to the thumbnail set.

@[email protected] that's a good point. Both Lemmy and NodeBB implemented FEP 1b12, which is why those category/community actors share content.

So yes, NodeBB's category actors also only share content, and don't produce any of their own.

ActivityPub introduced to NodeBB the concept of sharing/announcing/boosting, and we enthusiastically supported this as a method of content discovery.

While we were processing these activities (and publishing our own), we weren't actively tracking them internally. That has changed in the latest commits (soon to be RC5); shared content from both local and remote users are tracked internally and can be viewed in the user profile.

For example, here is c/comicstrips from lemmy.world. As it is a Lemmy community, it only shares content, and does not produce any of its own.

Here is a quick recap of how sharing is handled in NodeBB:

• When remote users boost/repost content, NodeBB interprets this as a share.
• When local NodeBB admins move topics out of "uncategorized" and into a category, it is interpreted as a share and this activity is federated out to the admin's followers.

At this time unprivileged users cannot share content.

@[email protected] did that message ever show up?

@[email protected]

@[email protected] you got it. When you publish the activity and send it to your followers, you (probably) included the as:Public pseudo recipient, that hints to the receiving server that they can add it to public lists like hashtag collections, etc.

@[email protected] you won't end up in peoples' feeds unless they follow you.

To do that, you need to follow others to start getting content, and responding to them to contribute replies, in order to earn followers

Relays can help you discover new content or seed your content to other servers, but they don't end up in peoples' feeds.