I hope I don't get accused of super bumping multiple threads tonight (really not so old threads or well not so old last post!)

On first impression, nodeBB was the ticket - without any of the technicals. It's all that matters.

It truly is all that matters. Since the majority of fourm users are not going to be technical and forum have there work cut out to drag people away from the twitters and face books of the world.

A forum can be deployed to any user base so it's application and audience is potentially as wide as you like and varied as you like, that you have to think about simple but not dumb Ui/UX and rely on the beauty of tradition, i.e. established and solid universal conventions that are universal but not afraid to push the envelope to enhance convention to the point it's at least feels innovate if not actually is.

Speed.

It's silky response. The fade out fade in transition was a genius choice, let me type that again GENIUS!

The Composer.

• It looks and is weighed better i.e. it's styled better, simple.
• It's not perfect, but it's one of the best out there.

The composer is the window to all content creation, the crucible of an entire forums everyday lifeforce. It's got to be good, it's got to always be trying to be better, by trying to be great. This is the interface that makes or breaks the user experience and thus a forum.

My UI/UX 2c:

Please consider making the composers upper top line a drag focus draggable area so it is not restricted to the black circle aligned to the left, that should really be centered (it took me too long to figure out) - it breaks a basic UI/UX expectation burned into our retinas at this point!

Yes!

As outlined in the second part to this post here - I have created this dedicated topic for the purposes of pitching this new feature and functionality for composer.

A composer that can align in one click to the right of the screen - creating a split view.

I guess if people want left they can have it but the concept is being able to easily reference posts on the right and compose on the left, keeping an unobstructed view of the entire flow of the topic posts without having to minimize the compose editor.

Meet the new contextual button that would toggle between positions.

Click to toggle horizontal position:
Click to toggle right-aligned position (split view):

As an evolution of composer core feature & function, I believe the case for, is incredibly self evident.

• I'm waiting for someone to tell me this feature is already available...
• I will edit an addition this OP with summary points and extra info if required.

Please Upvote - If you want to see this as a core feature in standard nodeBB deployment.

Updated a nodeBB to 1.13, all seems relatively fine, though, I was not paying attention and I updated to v1.13.4-3. - that's ok for now, seems to work.

However the ns-embd plugin is not embedding tweets, just leaving a blank blockquote. Youtube videos embed perfectly fine, so I suspect the watch + replace needs tweaking?

Watch

(?:<a.*?)?(?:https?:\/\/)?(?:twitter\.com)\/([^\/\"\s]*)\/status\/([^\/\"\s]*)(\/photo\/\d|)(?:.*?\/a>)?

Replace

<blockquote class="twitter-tweet"><a href="https://twitter.com/$1/status/$2?ref_src=twsrc^tfw"></a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

This is a feature I wouldn't expect in forum software, since traditionally such systems like phpBB don't have it out of the box. It also seems wrong on a base trust level even before we got to the modern era of GDPR etc. etc.

Yet Discourse has this out of the box much to my own surprise and I thought but why would you need it?

Other than tracking abuseive PM's between waring users, which could easily be stopped by the recipient being able to ban PM's form a user. I didn't initially see the valid use case.

The point was made by Atwood, Discourse creator, that for example certain types of nefarious rings might use your PM system to share illicit material undetected. Think the worst kind.

• That is a very valid point and one worth exploring.

However it's still strange being able to read anyones private messages and that users also may simply assume that their messages are private. Few think about databases and that once a person has access to a database they can in theory access any of the info but it's not frictionless access. Discourses implementation is as simple as reading your own PM.

What I felt would be a better solution, more admin friendly and simply effective at addressing the problem, would be to have a system that monitors the PM activity and volume of all user accounts.

For e.g. - A threshold is set with some criteria - then imagine a 0 post or very low post count user has more than 2 pm's a day it's reported and flagged in stats. Imagine another user has 100's of PM's per day or hour, it's flagged with more force, because such activity would be highly suspicious. A whitelist system would handle the good guys and magybe not flag (like mods) but still report their activity too, if required.

So of my 10,000 imaginary forum users how do you find the 4 or 5 who are abusing the system, with little effort but with pinpoint accuracy fast?

Second to that there could also be threshold limits set that users can only read and send x pm's per day until they clock up some rep, which would act as a massive disincentive to abuse the PM system for nefarious and illegal activities. (apologies if such a feature is already there, I'm not 100% familiar yet with all of nodeBB functionality and feature set but getting there).

Open access for admins to PM's does not mean you will easily find and therefore stop the problem. Access only helps you determine if it is a problem on a PM per PM basis, how do you even know which user acc PM's to start looking at - it is still needle in a haystack.

What you need are PM analytics as an admin in the first instance! - therefore it's not an access issue!

I find the Discourse implementation a good example of solving a real niche problem but with the wrong solution applied or at least the 50% wrong.

I would really like to see a PM report/abalytic system in nodeBB natively, as a core security feature to tackle this issue - that can auto lock crazy PM behaviour.

Warning + notices to users easily administered by default, that PM's are not publicly viewable but admin viewable if x. y and z occurs.

The crazy thing is Discourse team originally implemented this and gave moderators access.

That's just insane IMHO, even as an Admin I am not really comfortable with that once click power - it's clearly open to I would say more abuse that what it tries to solve.

@julian Cool thanks, yea poor ns-embed is not happy in 1.12.2 - I and others already flagged in that thread, still, A Great plugin!

Ok SMTP/EMAIL is fixed!

Some deeper DNS/MX work seems to have made the difference and using "encrypted" setting - initially I was using StartTLS as per email provider SMTP guide, which specified TLS - tested it again and StartTLS broke it.

Encrypted works.

@frankm

Ok great that worked, installed via CLI.

Totally forgot about it @crazycells mentioned it ages ago but it was no longer visible searching for plugin via the find-plugins in ACP.

How is this plugin long term as it seem to be archived, does this indicate no future dev, maybe it can be forked and someone can keep it alive if other plugins do not reach a solution.

This is a feature in Discourse, and when i first saw it years ago I thought, COOL!

Many years later, when actually interacting with the feature in Discourse. I realised it was generally a bad system because it was really a bad idea.

What problem was it actually solving?

Users not being able to moderator other users comments????

That is Chaos!

Why invite Chaos?

The problem you see it as is lack of staff to police the conversation. This is a problem for all busy forums. Overall auto features are too crude to deal with rising noise IMHO.

One very obvious downside of "social justice" which these days is IMHO another term or mask for mob rule, users quickly learn the weakness of the system, and actively suppress other users in a targeted fashion, so what might seem to solve the moderation burden, could end up being weaponised against ordinary users and cause serious community problems, the kind you may not recover from, as recriminations and all kinds of things could explode form a few bad turns.

The most important thing for a user first off, is to be able to report or flag a post easily, that see as problematic for whatever reason and then for that to appear quickly and very visibly to mods and admins alike.

At least a Troll is very easy to see, users who are abusing a system like this, how visible are they? You need to back up the user accounting side too. This is starting to seem like a headache.

Traditional moderation with a good team is the solution, that is sustained and enabled by a great admin/backend that make moderation of problem users fast and efficient. The better this system is the less moderation users you might need to assist in day to day moderation.

Get that right and you are winning.

Naturally moderation teams have there problem and this is often due to progress of time in my experience, so to add a crude feature like
mob down voting that kills post, does nothing to address team work and good admin policy, vision and direction.

A good report/flag system with SPAM and some other options where a user report may temporarily hide a post, is a good start - SPAM might be hidden automatically, (yes that could be abused) but since it is granular more likely it will be used in good faith most of the time (but I have seen people go absolutely nuts with report features too which is just silly), options for off-topic or disruptive might good (it might be goo to allow an admin set extra report flags and also control the action after the report, doe sit hide the post or not. Things like that, which aids the internal operation more than handing over executive powers to the mob!

Setting a downvote threshold to remove a post is basically giving your users based an achievable target to counter disruptive use or exact revenge! Trolls might also use this feature to counter also and then you have all out war.

Leave all the power in the hands of Admins, Mods and give them good control to track, control and censure problematic posts and users, that is hight visible quickly, fast and able to batch operate in comfort and then users will understand that the odd troll might get through or a bit of spam may appear but since you do such a great job of keeping the house clean, they really appreciate your efforts.

No point in making yourself obsolete now is there?

This one ain't too bad either, you can create palettes and is very hands on too

+you can apply various type of colour blindness filters to the palette to simulate how it might be perceived.

To abide by my own call to keep things simple.

I would suggest to base such a feature on report/flag action. rather than the downvote.

Downvotes are visble to users.

Reports/flags are not as a rule - this should be the trigger.

This goes some way to addressing the weakness of user mob behaviour to game the vote system to knock people out.

Ok if your moderation people are along a few hours later or no longer that 12 hours. Then using the report/flag function is perfect.

Not everyone who votes might be a good reporter and vice versa, as the two things are cognitively different actions IMHO.

I think someone who uses a report/flag feature, is able (*or we hope, but not always) to separate their personal interaction with posts versus helping keep the neighbour hood clean - maybe the way to see it is like this:

(voting) personal action vs (reporting) operational action.

Reporting/flag is a very clear functional action, because it implies that the report will be seen directly, and mod actions are expected to follow soon after or more swiftly.

Adding in extra purpose or breaking out to the voting system, into a secondary or sub role that it was not designed for, is I think, as outlined previously fraught with other issues.

Using reporting/flagging system, the Admin might benefit from be easier reports generated from reports/flags, and can plot over time... using the voting system to extra a report like this I would imagine is more complex or at least needing a lot filtering and re-stating to be useable.

User with most flags
Flags by day, month week... etc. etc.

In the admin there is already "Most Flagged" in the user, so let's go with what is already baked in and expand it out for best performance and visibility, and possibly allow combination of flags + user states to filtering user lists.

Then also if Admin can tailor flags auto-actions based on criteria, that would be sweet:

Flag action (post): HIDES POST - when user x 3> (w/100> posts) flag post - post is hidden, pending further approval/attention + user is frozen from all activity other than reading, until unfrozen, banned or whatever by mod/admin.

It would be useful say for a mod who has to freeze multiple user to be able to drill down a list of FROZEN users, to then investigate further for whatever reason or group unfreeze or unfreeze some and not the others.

User accounts could do with extra User States might be an idea with default but customisable privileges for admins to tailor, for example as above "Frozen".

Nice and very slick looking.

Hmmm... has it been hacked?

Any strange user regs before it went down?

Maybe you can review the last few users who roistered. If it is open. Just a thought. I've had NodeBB go down like that. No time to check it out. Nothing works like it should. Wasn't an important install.

How it woudl happen is, admin woudl approve a user. Since this would be an no users, this user is the first. Within about 2/3 mins of approving use.. BANG!

NodeBb goes down. Nothing is working like it should, in a similar way as to you are describing.

@bugmenot It is an intersting idea.

The initial issue I have is it appears the proposition is swap next page button for top/bottom scroll, which breaks the logic of pagination navigation.

Perhaps another equally noble approach is merely a tweak on the current implementation, that would be to put the pagination nav bar on it's own floating menu that is always on top at the bottom of the screen.

In fact there is a very compelling argument which I have been thinking about a lot the last couple of weeks, that suggestion the bottom of the screen, especially for mobile devices, could be better utilised, rather than clustering everything to the top.

Typically our hand held devices finds more often our hands at the bottom area of the device, not usually the top.

So our fingers are already positional close to that area, meaning single hand operation/interaction with the UI is more comfortable.

Also anytime elements want to push the primary content off-side in real pixel terms or purely visual balance ratios, should be very carefully considered.

Here we go, I see this one getting used from time to time to host files. Including .mov files.

https://catbox.moe

Usually (not real link)

https://files.catbox.moe/123Abc.mov

I almost have it but I don't. I'm getting a 404 in the embed window.

Replace:

(?:<a.*?)?(?:https?:\/\/)?(?:www\.)?catbox\.moe\/([a-zA-Z0-9_-]{1,24})\.mov?(?:.*?\/a>)?

Embed:

<div class='embed-wrapper'><div class='embed-container'><iframe src='https://files.catbox.moe/$1' frameborder='0' allowfullscreen></iframe></div></div>

I didn't spend to long messing with it to get it to work yet.

I should probably sit down and learn regex at this point.

@yariplus thanks for that insight. I shall not waste further time doing the impossible.

It’s good enough for me, users can adapt to a few clicks to make it work

I have another I’ll post later. I can’t figure it out.

@pitaj Solved!

You think I would have configured this right... the refresh was the clue... I forgot to set the http to https in the config.json file... thanks for pointer to look in the browser console! It was easier to observe the flip from http to https when refreshing.

@pitaj

Yea a ton of errors

FetchEvent.respondWith received an error: TypeError: Not allowed to request resource

Also web socket wss: connection failures too all resolving to the plugin folders and/or emojis folders/resrouces.

@omega

RUMBLE

Ok this combo works for me using the the Rumble Embed link that is available on a rumble videos page, e.g. below:

https://rumble.com/embed/vbenc7/?pub=4

Watch

(?:<a.*?)?(?:https?:\/\/)?(?:www\.)?rumble\.com\/embed\/([a-zA-Z0-9_-]{4,6})(?:.*?\/a>)?

Embed:

<div class='embed-wrapper'><div class='embed-container'><iframe iframe class="rumble" width="640" height="360" src='https://www.rumble.com/embed/$1/?pub=4' frameborder='0' allowfullscreen></iframe></div></div>

Not sure how to get the regex to deal with someone who pastes in a full URL for e.g.:

https://rumble.com/ve0tib-newborn-calf-takes-first-clumsy-steps-to-get-milk-from-his-mother.html

@yariplus If i could be so bold and throw up another embed puzzle.

This time rumble, and with mixed success, if you paste an embed link form rumble for e.g.

https://rumble.com/ve2ez5

This works, but currently displaying a random rumble video.

Here is the long URL for the same video for reference:

https://rumble.com/ve2ez5-airplane-returns-to-denver-after-engine-malfunction.html

This is what I have so far that works to embed and display a rumble video but misses the target video!

replace:

(?:<a.*?)?(?:https?:\/\/)?(?:www\.)?rumble\.com\/([a-zA-Z0-9_-]{4,6})(?:.*?\/a>)?

embed:

<div class='embed-wrapper'><div class='embed-container'><iframe src='https://www.rumble.com/embed/rumble_$1/?pub=4' frameborder='0' allowfullscreen></iframe></div></div>

@majr said in Cannot get emojis to work:

nodebb-plugin-emoji

Do you have nodebb-plugin-emoji installed?