@omega well I do pride myself on a well stocked fridge but maybe not that well stocked :rofl:

@[email protected] hello! Unfortunately I'm busy this coming Tuesday but would be interested to chat about doing something in the future. Something I should be clear about first though is that I'm not involved in Podcamp Toronto or really in the podcasting community at all these days. I ended my last podcast around 2010, so most of my direct experience really is "historical" lol.

Yeah, pretty much. angus: I think it would be helpful to work through an example of where this particular point of intersection may become an issue. Say you encounter an actor of type Group. You Follow the actor. You can't expect it to behave in any one particular way, but it will generally behave in one of these ways: It is a "normal" publishing actor. You will receive Create Object, Announce Object, Like Object, and so on. It is a boost bot. You will receive Announce Object for any object sent to it, mentioning it, etc. It is a 1b12 actor. You will receive Announce Activity, and other activities described in 1b12. It is a Smithereen-style actor. There will be a wall property, and it will send out Add activities where the target is that wall. The Add.object will also have a target, and this will match the Add.target as per 400e. Bonus: It is a context moderator. You will receive Add activities where the target is the object.context. It may also additionally be a "normal" publishing actor. So for any given "post", it might be a Create/Add/Announce/Announce-Create. This isn't limited to Group actors, but it is most prevalent in Group actors because of the popular (erroneous) interpretation of Group as equivalent to Facebook Groups. One final thing to note is that "normal" publishing actors and context moderators may be any type, not just Group -- there is no specific type dependency for these mechanisms, as they are the intended mechanisms. angus: So, this would result in something like: You receive Note 2 (with context A, a collection) which is inReplyTo Note 1 (with context A) You receive an Update to Note 2 and it now has context B (a collection)? OR perhaps you receive an Add of Note 2 to context B? In both 2 and 3, the inReplyTo would still be to Note 1, which would still have context A. @trwnh something like that? Yup. id: type: Note attributedTo: context: content: "I'm posting in a thread" --- id: type: Note attributedTo: inReplyTo: context: content: "This post is in a different thread but still replying to the first" --- id: type: Article attributedTo: inReplyTo: name: "Some Article" summary: "In which I reply to a forum post with an entire blog post. This is not part of any context." content: "

Lorem ipsum dolor sit amet...

"

Is there a way to enable registration queue but make it so that user's registering with admin invites are able to register bypassing registration queue and admin approval? Since it would only make sense since the admins are the ones who invited the user.

Many thanks!

@nhl.pl That's correct! That would be the GitHub repo for the new Social Web Incubator Community Group Forums and Threaded Discussions Task Force (what a mouthful!)

We're still figuring out governance and how to conduct discussions, but that's potential way.

Quill 2.0 has been released.
https://slab.com/blog/announcing-quill-2-0/

Link Preview Image Announcing Quill 2.0 - Knock Down Silos by Slab

Running weekly updates of every small improvement and bugfix to Slab that miss the headlines.

favicon

(slab.com)

You're welcome. Please spread the word about NodeBB in your country. Thank you.

AT Protocol by Bluesky offers Portable accounts (Change hosts without losing your content, your follows, or your identity) so it will end up in exporting profile at /user/yourusername/consent and using it elsewhere.

Just as an update, (incase anyone else has this problem), chatgtp was quite good sorting out, and removing older versions, and said:

The naming difference between node and nodejs primarily stems from historical reasons and package management conventions.
In some Linux distributions, including Debian and its derivatives like Ubuntu, the package for Node.js is named nodejs to avoid a conflict with another package called node. This node package is unrelated to Node.js and is used for a different purpose.
The naming convention was introduced to prevent potential conflicts between Node.js and the unrelated node package. However, this led to confusion for users accustomed to using the node command to execute Node.js scripts. To address this confusion, symbolic links or alternatives are often used to allow the node command to point to the nodejs executable.
While the naming convention can indeed be confusing, it's a result of the need to avoid conflicts and maintain compatibility with existing packages. Efforts have been made to streamline this naming difference in newer versions of Node.js, but it may still persist in certain distributions and setups.

@Rajeev-Kumar

Please check these topics:

Link Preview Image I want to add some thing like this

I want to add some thing like the following highlighted. How can I do it?

favicon

NodeBB Community (community.nodebb.org)

https://community.nodebb.org/topic/17120/how-to-create-a-new-topic-button-in-header/

Maybe one of the existing plug-ins can be modified to meet your needs.

For example:
https://github.com/combient/nodebb-plugin-medals
https://github.com/NicolasSiver/nodebb-plugin-ns-awards

Link Preview Image GitHub - combient/nodebb-plugin-medals: A NodeBB plugin which allows medals to be handed out to users.

A NodeBB plugin which allows medals to be handed out to users. - combient/nodebb-plugin-medals

favicon

GitHub (github.com)

Link Preview Image GitHub - NicolasSiver/nodebb-plugin-ns-awards: A system for rewarding forum users. The plugin allows admin to define set of awards that could be granted to users for special accomplishments.

A system for rewarding forum users. The plugin allows admin to define set of awards that could be granted to users for special accomplishments. - NicolasSiver/nodebb-plugin-ns-awards

favicon

GitHub (github.com)

Word that from would bee messed up. Can you try undoing your change and console.loging those values to see what they end up being?

@julian @[email protected]
Peeps, if we could further fill in the terminology spreadsheet and maybe use this as a start to deeper map between the platforms/protocols :- https://docs.google.com/spreadsheets/d/1tPZXywqFZe3xXx_fV9icNHLOkSrXx3_rHhPeRmMBZR4/edit#gid=0

@trwnh context is a wonderful thing 😉

@julian I am not sure but I guess so...

when I clicked the link on the first post of this topic: https://community.nodebb.org/topic/cd43b9f3-c032-44cc-adc8-f32e7ee91901/our-next-meeting/

it takes me here but gives error:

https://socialhub.activitypub.rocks/ap/object/1899f65c062200daec50a4c89ed76dc9

If I did things correctly, I should have a rudimentary two-way synchronization working now… I'm not sure if there's still a 5 minute delay between posting and federating... let's see.

Are you sure you want to use Apache web server? Even lightweight nginx working as reverse proxy can be easily overloaded with normal traffic. And you will see a result like this. Similar to attacking php-based forum with ddos-bots traffic.

Bluescreen rate-limiting high traffic will help to reduce server load so you want to leave it as it is.

A better idea is to install firewall or similar software to deny traffic from problematic IPs/countries/etc.

@Mia-smith said in Need suggestion: Experiencing Persistent API Error:

I also check this : https://community.nodebb.org/topic/17758/error-permission-for-opt-config-nodebb-in-installing-with-dockerlooker But I have not found any solution.

Do you have any other problems with your Docker install? For example NodeBB can show all users IPs as localhost if server ports are blocked (communication between Docker app and host machine).

It worked OK and stopped working?

Some interesting feature requests can be found here:
https://github.com/NodeBB/nodebb-plugin-2factor/pull/93

In short:

proposal to move all language files to Transifex and allow translators to work on translating plug-ins (pre-installed/default/bundled plug-ins were mentioned), 123456 vs. 123 456 as common i18n problem not only for Korea and Japan, some other shortcomings from Korean user point of view. Link Preview Image Korean translation by NavyStack · Pull Request #93 · NodeBB/nodebb-plugin-2factor

First and foremost, I wish to express my sincere appreciation for the development of such an outstanding plugin. In my role as the coordinator for NodeBB's Korean and Japanese translations, I have strived to maintain consistency in wording with the primary translation project. At present, numerous default plugins of NodeBB come pre-installed. However, it appears that this applies not only to administrators but also to end-users. Therefore, it would be advantageous to enable the management of built-in plugin translations on Transifex as well. While I currently utilize NodeBB in production, there are instances where certain strings or plugins remain untranslatable, often exposing my users, who are not proficient in English, to such content. Hence, I would kindly request your consideration on this matter. Below, I have outlined several queries regarding the plugin, along with suggestions for enhancement: Some applications use a space character when presenting a 6-digit number. For instance, 123456 may appear as 123 456 when copied to the clipboard. Given the increasing prevalence of users utilizing this feature via a browser extension plugin, I believe enhancing the user experience by disregarding space characters and accepting numbers solely would be beneficial. There are instances where 2FA (Two-Factor Authentication) needs to be input more than once due to specific circumstances. For instance, upon pasting it into a browser or application, users are prompted to re-enter their username and password, even if the values are accurate. This could be due to either rapid typing or previous input. Personally, I circumvent this inconvenience by pressing and holding the CTRL key while performing CTRL + V. (But... sometimes I face Username and Password form page.)However, this workaround may prove inconvenient for the average user. While acknowledging the inherent trade-off between security and convenience, I believe there is room for improvement in this regard, particularly concerning 2FA. Occasionally, upon entering my username, password, and 2FA code, I find myself logged in as a non-member pop-up. This issue warrants attention for resolution. Your attention to these matters would be greatly appreciated, and I am confident that addressing these concerns would significantly enhance the usability and functionality of the plugin. I am currently using NodeBB in a production environment. Hence, updating without translations results in English displaying as is, akin to a bleeding edge situation. I kindly request measures to improve this. You can verify my commit timestamps, which reflect my working pace. There's ample time to pre-translate adequately for any additions. Your cooperation in presenting translation sentences prior to adding new strings would be greatly appreciated. Thanks for your support.

favicon

GitHub (github.com)

@phenomlab Thanks for quick reply. I will try to fix it 👋