@[email protected] cool! TIL, although I don't think it's applicable for me.

@[email protected] no link yet, was just speaking hypothetically

Report that NodeBB-NodeBB edits don't federate · Issue #13085 · NodeBB/NodeBB

Likely a regression if reproducible https://community.nodebb.org/post/https%3A%2F%2Fforum.agnos.is%2Fpost%2F16

GitHub (github.com)

@[email protected] seems different for @[email protected]'s use case?

For an AS2 Object to refer to an html variant, url is sufficient, but for different languages is a whole 'nother ball game...

@[email protected] yeah it was the fact that it was all nested, so I'd start reading them from the outside in, and realize quickly I was reading them backwards.

That kind of stuff only really happens in email, which is why I was caught off guard.

@[email protected] @arachnibot I love how I want to add this to the core logic and someone beats me to it with a third party plugin.

It's absolutely fantastic, and exactly how our plugin system should work!

@arachnibot yes, offhand I think it should (although I didn't check the code).

When remote content is parsed I just call the same internal methods to create a topic.

@bh4-tech I was not aware Mastodon even supported images in private messages. They don't even support the <b> html tag.

Interesting.

@Kosiak Sure thing, v4 shipped with allow/deny lists so you can specify which domains to add to that list.

In your case, you'd be using an allow-list.

The same limitations to the content sharing model still apply. Topics and posts won't magically flow between the sites unless follow relationships exist or you set up category syncing.

Late reply but the adsense plugins supports ads.txt input since 2023 https://github.com/NodeBB-Community/nodebb-plugin-adsense/commit/8dff07d7f3bc8cf8372002099ea3a4d65502c594

Also app.alert* functions were removed so replace that with alerts.alert() from the alerts module

If you move the template to admin/plugins/characters-core.tpl and render it with res.render('admin/plugins/characters-core', {}); it should work.

The client side uses the path passed to res.render to import the module so in this case it needs to match the path you use in modules section in plugin.json.

@[email protected] awesome! Looking forward to all of these presentations... Where do I sign up for a time turner

You need to use the modules section in your plugin.json, check nodebb-plugin-quickstart for an example of how the admin page loads it's client side javascript module.

In another thread, @[email protected] talks about challenges regarding proliferation of spam (or other unwanted content) on the fediverse:

... I was talking about reddit's "posts require approval" mode. Something that might be of use for new accounts registering on pixelfed instances to prevent things like gorespam from occurring.

NodeBB has the post queue (our name for it), and it works really well to stop drive-by spammers. Most cheap spam is easily identified as such, and it's only a couple clicks to send them to /dev/null.

More recently, and especially since we've been federating posts outward, we've started encountering possibly LLM generated content entering our post queue. It could be that these accounts are legitimate users creating an account to respond to remote content, but it's equally likely that they're attempting to create plausible content in order to pass validation, before proceeding to post spam.

At least here on community.nodebb.org it's trivial to discover, because this forum is for NodeBB support/discussion, and a post out of the blue responding to a post about Trump or Israel/Palestine is very obviously not meant to be on this forum, although it's definitely one of those "hard problems" for more general instances.

@[email protected] @[email protected] "posts require approval" should he standard behavior for every fediverse instance.

NodeBB has it, although we call it "post queue". If you don't meet the threshold then it all goes into a moderation bucket. It is exceedingly good at blocking spam, because spammers don't ever really have the resources to buy hacked accounts with reputation.

With LLMs, we're seeing less overtly spammy content attempting to pass out post queue. I don't have a solution to discover whether they're legit content though.

@[email protected] sure! NodeBB has it working now if you want to poke around on BrowserPub, just paste a topic URL into it.

v4.0.0 can pull entire topics in already (assuming the remote end supports it.)

When v4.1 drops you'll be able to do this via the topic URL itself.

@[email protected] let me know if you have any questions!

Tag @support if you want to make a new general support topic

@[email protected] you are not wrong about that. @[email protected]'s approach works now, but I'm not sure how well it will scale.

It could be perfectly fine. It might not, who knows.

But it's a good thing there's more to the fediverse than Mastodon.

@[email protected] I'm not entirely sold on the replies collection traversal logic as penned by @[email protected]

It doubles down on the premise that individual notes are isolated entities whose connection to other notes is dictated solely by inReplyTo and replies.

7888 introduces the concept of a conversational context, which is maintained by the original conversation starter. When you have an ad-hoc source like this, you can just ask the context owner to supply the entire set of responses in one single call (or perhaps a few more if paginated.) No replies traversal needed.

@[email protected] just give up and embrace the fact that any given ID might not resolve, either temporarily or permanently.