Wouldn't it be nicer for plugin authors to always show 'compatible' with the last release that the plugin was compatible with?
I think I would be reluctant to add a badge to my READMEs that tells my potential users that this plugin doesn't (yet) work with a NodeBB version that has just been released.
Just a thought
When using Redactor as composer, clicking 'New Topic' or 'Reply' button will create multiple GIF button. See screenshot below:
The GIF button multiplies every time I close the composer and reopen it. It doesn't happen if I'm using the default Composer.
Anybody face the same issue?
In case anyone is interested to make the panel darker with the night mode plugin, we have this modification to CSS
background-color: #333 !important;
background-color: #333 !important;
@julian said in Advanced Editor Plugin:
You'll probably want to use the Quill Composer, which is our official (in development) WYSIWYG composer.
You should be able to download it from the plugins list.
Don't you use markdown here?
Well looks like I was an ID10T on this one. npm install pulls the original Annihil version cuz that is where package.json tells it to grab it from.
Manual installation of Julian's/NodeBB 3rd Party forked version, available here: https://github.com/NodeBB-Community/nodebb-plugin-email-blacklist
Coupled with my URL query string update above and ... voila! Now works dandy w/both manually added addresses and istempmail.org API key.
The function isTempMail's path var needs to be thusly:
path: '/api/check/Your-API-Key-Here/' + email
Or maybe I neglected the trailing slash first time around. In any event, geronimo, there ya' go.
So you want your static Gatsby site to be dynamic. Heh, you are not the only one to have given this some thought...
But... where's the "win" here?
Security: Well, the moment you go dynamic you open the door much wider to crackers. Maybe some small win that your static content is "safe" and only comments system exposed.
Narrow minded to only analyze a single vector though so lets take speed and performance. Well, a static article might load faster since now main potential bottleneck is backend db and script glue.
On to stability: Maybe a bit more stable to only make comments dynamic?
Maintenance: I question whether this pans out on the cost/benefit front because the moment you go dynamic you add a LOT to your stack. Admin that stuff takes time so you may as well leverage it for other stuff.
So ye' needs to be rollin' up yer' sleeves and experiment to find where your sweet spot lies. I think I would be inclined to go with dynamic blog such as ghost (definitely not WP). Ditto on the wiki front.
NodeBB is awesome sauce for sure but seems overkill for a blog comment system. Disqus sucks privacy & copyright wise but there are other 3rd party offerings w/less egregious terms, e.g. Muut and a couple others I don't recall off top of my head. Personally, I just do w/o comments. No interest/need in becoming an Internet Personality. I just toss some stuff "out there" for whatever it may be worth to whomever. Yeah, maybe missing some back and forth, contribs, etc. but when it comes to bloggin' I would rather spend my time writing than maintaining and sweating the next zero day exploit. Yeah, I am a freak.
Be all that as it may....
Perhaps these are the droids yer' looking for:
Reflections on the Digital Sabbath
New to nodeBB, was curious if there were any existing plugins that had functionality similar to the Donut App for Slack? In short it essentially is an app that randomly pairs people either within a specified channel (would be groups for NodeBB) or across multiple channels. I think this would be a cool way to go about building connections within a distributed online community.
Tried to search through the plugins on npm list but didn't see much in that regard.
Update for #3 hashtag system!
We found this plugin for hashtags:
It replaces tags system in NodeBB, and does search with the hashtag. We are still testing but so far looks ok. I think @Andrea-Dragotta made it, so thanks Andrea... we were looking for something like this...
I suggest this should be an intrinsic property of NodeBB, old tag system should be replaced with modern hashtag system where hashtags can be written anywhere in the text and turn blue, and can be searched as tags.