Is it possible to disable the @ mention on clicking reply? I share the opposite opinion as the thread author here: if I'm replying to someone, an @ mention just seems redundant: they're already going to receive a notification for that reply, right?
@TonyTony this would be best accomplished through a plugin, to restrict access to certain tags to specific users, or user groups. If you're interested in sponsoring this plugin you can reach out to us, [email protected]
Disagree w/above though. Too much added complexity. KISS.
Tough crowd, always with the tomatoes... try this one:
Let the Mods be Mods, let the Users be Users and Admins be King & Queen, forum developers could be Heros!
Granted it's more BOWIE than KISS but you get the point right? 😉
Oooh, la, la!!! Good one. Yeah, I'll take Bowie. Had the good fortune to see Bowie live way back in the day. Spectacular showman. Indeed. Followed Stevie Nicks. But I digress....
Maybe you missed that I got your point. At least w.r.t. the root causes of the issue. My point is that AI is not the solution for all things because AI, by its very nature, lends itself to becoming gamified and one consequently finds themselves in a never ending bot arms race.
A community needs to behave like an actual community and help the good guys do their jobs policing the bad guys. We need the human factor because we need the human touch and human oversight. And hopefully some human hard won wisdom as well.
The larger the community the more mods, etc. required. We all get that many lurk, fewer post, fewer yet are active contributors..... But hopefully.... on a prayer and one wing... good mods and helpers emerge. And it seems they will, in my experience, but it takes time - needs to develop organically and no real short cuts.
In the meanwhile... are we able to make a knob that actually works for that? With us rather than against us? Tough cookie, for sure. 🤔
Oh and can we have a better grammar-typo bots for my posts... 😞
Yes I'm referring to the Dockerfile. I'm no expert with Docker either, but I must admit that it's extremely handy for creating forums on the fly with different versions at the same time, and saves a lot of time.
If you're not focused on this tool I completely understand and appreciate you already providing up-to-date docker images, so I'll try to see what I can do myself and share it if it works well. This is possible by manually modifying the dockerfile but I think it's also possible in a more elegant way and easy to use, with env variables 😉
Pinned topics/posts are useful to help new users and we use them in all the categories. Some users end up directly in "unread" or "recent" and it would be helpful if we could pin topics to those as well.
a. I agree with @julian there are philosophical disagreement
b. agree, adding Google schema support could be built-in like we have seen FB open graph is built-in
c. not a forum, try other software
d. would be helpful, could be done by a plugin. Argueable could be built-in too, IMHO
e. I have nothing against but I think it would be a large project because I could picture some addition live ML and log mining needs to be developed for this to be generalized, and could complicate the core NodeBB a lot.
f. not a forum, sounds to me a social network
g. has been done by plugin and you could pretty much develop it yourself.
h. not thing against it, I think it currently works.
i. it's more of a site operating and community engagement strategy
j. not a forum
k. Good idea, could be done by plugin
l. This is already in place, right
m. good idea. I don't see why not but I assume it already works
n. same as k
The case for asciidoc from the asciidoctor folks, quoted liberally from AsciiDoc vs Markdown for purposes of discussion and analysis (i.e. Fair Use):
"The defacto lightweight markup language is Markdown. (At least, that’s what you call it at first). The
main advantage of Markdown lies in its primitive syntax: its manual and cheatsheet are one and the
same. But this advantage is also its greatest weakness.
As soon as authors need something slightly more complex than basic prose (e.g., tables, cross
references, footnotes, embedded YouTube videos, etc.), they find themselves resorting to embedded
HTML or seeking out more feature-rich implementations. Markdown has become a maze of different
implementations, termed “flavors”, which make a universal definition evasive.
The IETF has declared “there is no such thing as "invalid" Markdown.” See This Is Markdown!
Or: Markup and Its Discontents.
Here’s how the story inevitably goes. You start out with Markdown. Then it’s Markdown + X. Then
Markdown + X + Y. And down the rabbit hole you go. What’s worse, X and Y often require you to
sprinkle in HTML, unnecessarily coupling content with presentation and wrecking portability. Your
instinct to choose Markdown is good. There are just better options.
AsciiDoc presents a more sound alternative. The AsciiDoc syntax is more concise than (or at least as
concise as) Markdown. At the same time, AsciiDoc offers power and flexibility without requiring the
use of HTML or “flavors” for essential syntax such as tables, description lists, admonitions (tips, notes,
warnings, etc.) and table of contents.
It’s important to understand that AsciiDoc was initially designed as a plain-text alternative to the
DocBook XML schema. AsciiDoc isn’t stuck in a game of whack-a-mole trying to satisfy publishing
needs like Markdown. Rather, the AsciiDoc syntax was explicitly designed with the needs of publishing
in mind, both print and web. If the need arises, you can make full use of the huge choice of tools
available for a DocBook workflow using Asciidoctor’s DocBook converter. That’s why mapping to an
enterprise documentation format like DocBook remains a key use case for AsciiDoc.
And yet, AsciiDoc is simple enough to stand in as a better flavor of Markdown. But what truly makes
AsciiDoc the right investment is that its syntax was designed to be extended as a core feature. This
extensibility not only means that AsciiDoc has a lot more to offer, with room to grow, it also fulfills the
objective of ensuring your content is maximally reusable."