General Discussion

Publish your plugin to npm then install it with npm install nodebb-plugin-posters then it shouldn't get removed.

@baris said in Best solution to this:

You need something like https://github.com/NodeBB-Community/nodebb-plugin-assign-newuser-to-group, maybe fork and modify that to your needs.

Thanks a lot. I wish I could modify it but unfortunately, I can't.

Maybe someone else will see a need for the same feature.

@vijay-kumavat This is set in two places. The first is /admin/settings/user

4d836a36-d35e-412f-80fd-6e34b1727483-image.png

The other is in /user/theuser/settings

abf184f4-7cde-412d-ac67-912d9f796bab-image.png

I'm certain that the user settings override what is in the site (but I may be wrong). However, you can use the admin level to set it for everyone, but it can be overridden.

@baris Thank you so much

@baris i take your plugin "browsing-users" and create a new one "who-read-it". I hope it is okay for you 🐞

currently it looks like this:

5cde4deb-ef7d-46f6-ba70-04b7d340522d-grafik.png

the timestamp i like to have in the tooltip behind the username, but i dont know who, maybe you have a idea?

<div component="topic/who-read-it" class="d-flex gap-1"> <i class="fa fa-check fa-fw" title="Who Read It"></i> <br> {{{ each whoreadit }}} <div data-uid="{./uid}"> <a class="text-decoration-none" href="{{{ if ./userslug }}}{config.relative_path}/user/{./userslug}{{{ else }}}#{{{ end }}}"> {buildAvatar(whoreadit, "24px", true, "avatar-tooltip","title=test")}{./readtimestamp} </a> </div> {{{ end }}} </div>

@PitaJ ,

Its working now. Thank you

I select "Parse emojis in topic tiles" from Admin of Emoji setting page.
Then click on -> Build Emoji Assets -> then Save -> then Rebuild & Restart.

We try to keep master branch stable and release patch versions from there, for example 3.1.6. Develop branch is for the next minor release (3.2.0) and contains new features. Major versions contain breaking changes ie 4.x

@cagatay They did last year, but looks like there so many votes, 20i has to keep recounting them. Full sarcasm intended as they've moved the announcement date three times

https://www.20i.com/foss-awards/category/community-and-social/thank-you

Is there a good way to limit a users' or groups' threads or posts? Such as limiting to X threads per week or X posts per day? Or perhaps a workaround for Number of minutes between threads like there is for posts?

Thanks

You can also order the elements in the formatting bar with css, https://community.nodebb.org/post/66056

thank you @baris

So I've been thinking about this since 2012 as a non-coder, and @julian might remember about 3 years ago I was musing over Time Berners Lee Solid Pods concept I think based in Node.js and is now offered as https://www.inrupt.com, at the tine I found this interesting and seemed to encapsulate what i was looking for, but no one was really understanding the concept fully or why I was looking at this, but here we are now and Mastodon seems to have lit that fire under many asses at once. 🙂

I came across the activitypub recently too and it seemed to be similar kinda, but I'm not sure yet as have not fully dug into it.

My originating ideas probably better classed as user <> www <> server(s)

My main concept was a user retains all their original data in their possession, and being able to publish and control from one point, publish that info across multiple platforms all at once, and retain control over edits, removals etc., every platform could require individual negation which the user coudl manage again the permission etc. from their console app/platform (this would include a monetisation system) - is this what ActivityPub allows?

Since all those years ago, there are some offering or tapping into this original thought space. My thinking was market need (user need and traditional journalism to some degree) as publishing industry hadn't really cracked the net back in 2012 IMHO and was floundering, how to monetise content etc., well I thought, take out the publishing houses for good (middle men) and put it all in the lap of the content creator.

Eventually after the era of social media wildfire, services like substack.com and maybe tips in brave began to inhabit a similar or the same space of that original thought space. The thing that has always struck me NodeBB, it has the capacity to also be the platform for such user use cases too.

There is a focus obviously on managing more than one user, a group discussion, the original forum concept, but I would propose inverting the outlook and running a parallel track and thinking about NodeBB for the single user case applications.

As for make starting forums suck less, well some of that is considered above, but needs clear conceptual again another thing on my mind for many years, but oh boy, I'lm gonna stop right here for now. 😉

It should be

{{{ if ./teaser.user.picture }}}

It should be noted that in previous versions of the forum, the &nbsp; would not have been deleted, this is something quite new.

@baris Thank you!

FYI you were still getting the API key error when trying the built in SMTP maker probably because you didn't disable the mailjet plugin.

An emailer plugin always takes precedence.

https://community.nodebb.org/topic/10225/nodebb-plugin-reactions-reactions-plugin-for-nodebb

@baris @PitaJ Thanks a lot guys ,, My bad , i though i saw async version used by nodebb was 3.2.0

Thanks @PitaJ

I've created a plugin using @baris and your intended solution found here.

Unfortunately there is no impact to the recent cards plugin or any other teasers. No regarding error or warning found in the nodebb log. This is part of the log when I run ./nodebb dev:

verbose: [plugins] Loaded plugin: nodebb-plugin-teaser-image verbose: [plugins/fireHook] filter:teasers.configureStripTags

Plugin is as basic as it can be:

index.js:

'use strict'; var plugin = {}; plugin.filterTeasersConfigureStripTags = async function (hookData) { // Check if the "img" tag is present in the tags array if (hookData.tags.includes('img')) { // Remove the "img" tag from the tags array hookData.tags = hookData.tags.filter(tag => tag !== 'img'); } return hookData; }; module.exports = plugin;

package.json:

{ "name": "nodebb-plugin-teaser-image", "version": "1.0.0", "description": "NodeBB Plugin to show images in teasers", "main": "index.js", "dependencies": {}, "nbbpm": { "compatibility": "^1.0.0 || ^2.0.0 || ^3.0.0" } }

plugin.json:

{ "id": "nodebb-plugin-teaser-image", "name": "Show images in Teasers", "description": "A NodeBB plugin to show images in teasers", "version": "1.0.0", "hooks": [ { "hook": "filter:teasers.configureStripTags", "method": "filterTeasersConfigureStripTags" } ] }

Anything I have overlooked? 🤔

@omega when everything is !important what truly is important?