Thanks for the feedback will definitely try the SES method instead.

My mailbox definitely has no sent mails from NodeBB. So I may have set it up incorrectly or SendMail really is problematic.

Thanks a lot I will try this and see how it goes.

@[email protected] right. I think functionally I'll never encounter a Delete, check the origin, and find that the note hasn't actually been deleted, but stranger things have happened!

Yes, cover picture/photo is what I mean I think. The two images you can put on top of your profile page. One is the small round icon and the other one is like your header on FB for example. Both seem to be called cover picture.

First, I realized immediately after posting that using a plugin IS the way to not break updating and depending on the updates, the plugin would have to be updated too.

Second, yes, poorly configured security could allow someone to clickjack but using X-frame and other headers is typically used to mitigate those kinds of problems.

I'm not sure what you're suggesting however. Are you saying it would be a bad idea to use an iframe in the way I'd like to or that it can be done, just have to be careful to use good security?

My interest is basically to try making our forums a more usable and interactive environment than simply support questions being answered. I'd love to use nodebb if possible.

@clover try changing your hook function to edit postData in place and return it directly, rather than creating a new object.

@julian said in Blog comments on external blog website:

@crazycells ah sorry, I didn't respond because I wasn't sure...

But I think it should be fine. Technically according to browser security policy, nodebb.org and community.nodebb.org are essentially different sites.

So if you used a different domain the same restrictions apply, but the plugin should still work.

Thank you very much, we will try it and report the outcome then...

@NodeHam Right, so that's the thing that's different about this whole decentralized social network thing.

There's no magical engagement algorithm that allows your content to reach other people. If nobody follows you, it doesn't get sent out to other services, so the post stays local to this NodeBB forum.

To get follows, you have to follow others, and hopefully someone with many followers (like my crag.social account) will "boost" your post 🙂

You might've noticed that every time I post about ActivityPub, either my crag.social account, or the NodeBB account on fosstodon.org shares it (sometimes both). That's because those two accounts have much higher follower counts than my NodeBB account. That difference will lessen over time 🙂

There's are other reasons to have two separate NodeBB installs:

you may want to run different sets of plugins uploaded files are stored within the NodeBB directory, best to keep those separate plugins like emoji and customize store files specific to a certain forum, and all plugin files are within the NodeBB folder

@phenomlab that doesn't sound like out of the box behaviour... can you reset all plugins and see if it reproduces?

Yes, thanks both. I was confused!

Technical stuff ahead 🚨...

This is merely exposing the frontend UI to the already established backend logic.

We have two methods internally that are used for this:

Notes.assert, which when given a object url or id, parses it and attempts to resolve the parent chain all the way to the top-level post. It then creates a topic to house all of those posts. Actors.assert, which when given an object url, id, or handle, creates a local representation of the user. How come "query"/etc. didn't show up?

For both user and post searching, if the passed-in url does not resolve or does not resolve to a processable object, then we do not proceed. It's important to realize that while in an ideal world, we'd all be passing immutable identifiers everywhere, the real world is just a bit messier.

Search queries could be a post or user URL, or a webfinger handle, so additional logic was required to handle those use cases. Most ActivityPub-enabled software I've encountered handle these vanity URLs when queried via ActivityPub — it returns the appropriate representation for processing. Some do not, and so in those cases, those items will not show up in the search results.

@crazycells Thanks for the reminder. I'll take a look.

Thats how FEP-1b12 works, its necessary if you want to federate activities such as voting, deletions or mod actions and not only post creations. But Lemmy doesnt support arbitrarily wrapped activities, only specific hardcoded ones like Announce/Create/Note, Announce/Like or Announce/Delete.

@Nuran-Akimbek You are chasing solutions without knowing the reason for the problem.

Listen to what @baris asked of you here: https://community.nodebb.org/post/99346

Fix what is causing your server restarts, and you will fix your problem. You don't have to do something like migrate to Postgres.

Hi, sorry I'm new to NodeBB... can I buy this plugin (where?) and use it with the latest version of NodeBB?
Thanks 🙂

@[email protected] NodeBB now supplies context with every as:Note object, and is resolvable as an OrderedCollection.

One thing that is not currently done is what we talked about here, inheriting the authoritative context and serving that instead. I will need to think that through a bit more.

As of today, the NodeBB-ActivityPub implementation now supplies both context and audience properties with every post.

N.B. When I say context and audience, these are also terms used by the ForumWG that refer to "topic" and "category", in NodeBB parlance.

Early indications from the last ForumWG meeting indicate movement towards the inclusion of context in a low-level as:Note object (a federated NodeBB post), resolvable as an as:Collection or as:OrderedCollection. The latter is what NodeBB will send, ordered by post time.

Discussions with @[email protected] also suggest that Discourse has the ability to parse an as:OrderedCollection context if provided, but currently does not if encountered as a property in a Note.

A minor change today also updates the audience property, which used to erroneously point to the context/topic, but now points to the audience/category. This change aligns usage of this property with FEP-1b12's expectations.

This change should allow other implementors to:

automatically group objects together given a the provided context, and more thoroughly backfill a given object's context, without relying on inReplyTo traversal

@[email protected] @[email protected], @oplik0 and I took a closer look today and found the one place where IDs were not sent with Announce activities.

Let me know if you find any other oddities 🙂

Hi all,
Well this is my first time writing a plugin which involves using client side hooks...
For a start, i would want my plugin to listen to a hook which activates when the topic page is completely loaded and topic tools are loaded too.

For which I wrote this function:

'use strict'; /* globals document, $ */ $(document).ready(function () { function alertType(type, message) { require(['alerts'], function (alerts) { alerts[type](message); }); } console.log('nodebb-plugin-quickstart: loaded'); $(window).on('action:topic.loaded', notifyBox); function notifyBox() { console.log("in notify box"); alertType('success', "done") } });

but this is not working... I can only see "nodebb-plugin-quickstart: loaded" on the console.

Where am i going wrong here??