I have a problem with "a borken topic" .... don't know why and how but it does not look good.
Can't edit/change/delete a post anymore.
[image: 1733228075389-ee0188a5-ebd6-46df-a76c-da01b313a28a-image.png]
How can I resolve this?
Not always but most of the time the posts look weird and cannot be accesed through the ... menu anymore.
Also the post has then a * in before.
[image: 1733228277438-56d70931-b907-4e84-b87c-0ccea7023eb8-image.png]
I often ponder what would constitute a "good" editor? Even for formats like BBCode, Markdown, and XHTML, which are variations of traditional editors, they rely on various buttons to insert code that ultimately expresses the final edited result as displayed on the page. Despite the advent of WYSIWYG (What You See Is What You Get) editors and Markdown's writing preview, I still feel that something is missing. So, I've been thinking whether there could be some changes or perhaps an editor—or input method—that is more user-centric, with "almost" zero learning cost for the user.
In essence, I am envisioning an editor that bridges the gap between ease of use and functionality, offering users an intuitive experience without the need for them to learn complex syntax or commands. This editor would focus on making the content creation process seamless and accessible to everyone, regardless of their technical background.
Idea 1 ——Kill all text type buttons
This is a classic editor interface
[image: 1733229457778-%E6%9C%AA%E6%A0%87%E9%A2%98-2.png]
[image: 1733229893223-3.png]
The pink areas are function buttons
[image: 1733229977938-4.png]
The blue area is user input area
When we typically use the posting feature, especially for the first time, the first thing we need to do is get familiar with the row of buttons at the top. Sometimes, you might even encounter users who press these buttons randomly, not fully understanding their functions.
This experience highlights the learning curve associated with traditional editors, where users must invest time in understanding how each button works and what effect it will have on their content. It can be particularly challenging for new users who may feel overwhelmed by the array of options available to them, leading to potential misuse or confusion about the editor's capabilities.
What I'm considering is eliminating all preset buttons.
[image: 1733230435502-5.png]
By removing the preset buttons, the aim is to simplify the interface and reduce the initial learning curve for new users. Instead of overwhelming users with a variety of options they may not immediately understand, this approach seeks to provide a more intuitive and user-friendly experience. It challenges the traditional design of editors that rely heavily on buttons for formatting and instead explores alternative methods that could make content creation more accessible and straightforward.
This concept might involve using context-aware tools, natural language processing for commands, or an intelligent assistant that understands user intent and formats the content accordingly. The goal would be to create an environment where users can focus on their content without needing to learn a set of rules or syntax, thereby achieving a nearly zero learning cost while still allowing for rich text editing capabilities.
For more information on how my idea was realized, please continue reading....
Idea 2——Preset the article as multiple paragraphs
My thought process is like this: What is the purpose of an editor that we need?
Or, what is the purpose of having buttons on an editor?
The answer is quite simple: it is to make the content more readable. For an article to be easily readable, it must necessarily include punctuation (obviously), paragraphs, images, charts, as well as various quotations, annotations, and so on.
[image: 1733231300111-6.png]
So, we could design it in such a way that the article is divided into multiple paragraphs. Users would add paragraphs as needed and choose what content to fill in each paragraph. This approach allows for a more structured writing process where users can focus on one section at a time, ensuring that each part of their content is well-developed and organized.
[image: 1733231702948-7.png]
[image: 1733232413881-8.png]
Here, I roughly divide the commonly used elements into four groups (though in practice, there could be many more): Text Paragraphs, Image Paragraphs, Quote Paragraphs, and Custom Button Paragraphs.
Let's take a text paragraph as an example
When we choose to insert a text paragraph
[image: 1733232934146-9.png]
[image: 1733233333801-10.png]
text paragraph example
[image: 1733234869473-11.png]
Once users opt for a Text Paragraph, they are presented with a clean, button-free interface where they can begin typing their content immediately. This minimalist approach minimizes distractions and allows users to focus on writing without worrying about formatting at the outset. After the user finishes typing and selects the text they wish to format, a contextual menu automatically appears
Of course, this is just my own idea, and I'm considering it from the perspective of a complete novice user who has no experience with Markdown or other markup languages.
This approach aims to make the editing process as intuitive and user-friendly as possible for individuals who may not be familiar with coding or complex formatting languages. By simplifying the interface and postponing the introduction of formatting options until after the text is input, it caters to users who might feel intimidated by traditional editors filled with buttons and commands.
By prioritizing ease of use and minimizing the initial complexity, the editor can empower users to express themselves more freely and confidently, ultimately leading to better and more engaging content creation.
[image: 1733235133325-12.png]
image paragraph example
[image: 1733235487058-12.png]
This is a demonstration of an Image Paragraph.
About Edit post
When it comes to editing articles, we can also opt to edit paragraphs directly instead of editing the entire article. This method provides much greater flexibility.
[image: 1733236798669-13.png]
[image: 1733236804850-14.png]
Of course, these are all just my own ideas, and I welcome any opinions or suggestions from others for discussion.
i'm using NodeBB v3.10.3. Popular work well when i start to use.
In the one day, i don't know why Popular don't work although i try to click to topics for update topics views.
Site don't show any data when i chose: day, week, month
[image: 1733200643197-5161646d-203a-441a-b031-788314c75d08-image.png]
When i chose: All time, site response data but it's not true by views.
this is my congfig:
{
"url": "https://mywebsite",
"secret": "{mykey}",
"database": "mongo",
"mongo": {
"host": "{ip}",
"port": "27017",
"username": "nodebbv3",
"password": "mypass",
"database": "nodebbv3",
"uri": ""
},
"port": ["4567","4568","4569"],
"bind_address": "0.0.0.0",
"isCluster": "true",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "mypass",
"database": "2"
},
"upload_path":"/public/uploads",
"session_store": {
"name": "redis",
"host":"127.0.0.1",
"port":"6379",
"password": "mypass",
"database": "1",
"tls": {}
}
}
Warning: 635 repetitive deprecation warnings omitted.
Run in verbose mode to see all warnings.
2024-12-03T01:15:32.156Z [4567/2042] - info: [build] admin control panel styles build completed in 8.101sec
2024-12-03T01:15:32.156Z [4567/2042] - info: [build] templates build started
2024-12-03T01:15:33.038Z [4567/2042] - info: [build] templates build completed in 0.882sec
2024-12-03T01:15:33.038Z [4567/2042] - info: [build] languages build started
2024-12-03T01:15:34.966Z [4567/2042] - info: [build] languages build completed in 1.928sec
2024-12-03T01:15:34.966Z [4567/2042] - info: [build] Bundling with Webpack.
279 assets
733 modules
ERROR in ./build/public/scripts-client.js 1211:2-1269:4
Module not found: Error: Can't resolve 'composer/drafts' in '/home/NodeBB/build/public'
ERROR in ./build/public/src/modules/topicThumbs.js 104:6-106:8
Module not found: Error: Can't resolve 'composer' in '/home/NodeBB/build/public/src/modules'
webpack 5.96.1 compiled with 2 errors in 8926 ms
2024-12-03T01:15:44.447Z [4567/2042] - info: [build] Asset compilation successful. Completed in 32.953sec.
[root@bsd /home/NodeBB]#
I have https which is a certificate from Cloudflare.
My Nginx server has the configurations from the documentation.
When I have enabled: “url: “http://forum.example.com” - login works.
When I set in config.json
“url: “https://forum.example.com” - error
Error message:
Login failed.
Login failed, probably due to session expiration. Try again.
In the URL, there is an error: "https://forum.example.com/login?error=csrf-invalid"
It needs https because, without it, the Google SSO plugin doesn't work for me
my nginx:
server {
listen 80;
server_name example.com;
return 301 https://forum.example.com;
}
server {
listen 80;
server_name forum.example.com www.forum.example.com;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://127.0.0.1:4567;
proxy_redirect off;
client_max_body_size 10M;
# Socket.IO Support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
I do my first steps with activity pub. It looks like a really interesting piece of software.
Now i can follow some user and so on. Works fine.
Next i will, when i post on the Fediverse that this post landed in an category (NodeBB).
In documentation i find this.
Whether a remote user can create a topic in that category by mentioning it
So i send this post.
#ActivityPub Testing
@Radfahren
Now i think that this post will be move to the category Radfahren
The post will only be landed in /world.
What i do wrong?
Agenda preparation for the December ForumWG meeting can be found at this public link (anyone can make comments for review.)
Monthly meetings are held on the first Thursday of each month, at 1700 to 1800 UTC. You can find them listed in the SocialCG Calendar. The next meeting will be held on 5 December 2024.
We will be continuing onwards with:
FEP convergence (re: conversational contexts) and a proposal re: baseline usage of as:context as a grouping mechanism
updates by WG members re: non-as:Note support in Mastodon
As always — time permitting — if you'd like to speak or inquire about a certain topic, comment in the agenda or reply here, the floor is open!
Note that I said "quoted posts", not "quote posts", don't @ me!
After the last WG meeting @[email protected] @[email protected] and I chatted a bit about how NodeBB handles quoted posts, but also in relation to quote posts. I thought that it was an interesting chat that merited further discussion; also because some of it was over my head.
When asked how NodeBB handles blockquotes specifically, I replied that blockquotes themselves are rather simple. We set a copy of the text wrapped in <blockquote>.
The rationale is simple: forums typically represent content in a linear fashion, and quoted posts are a handy way to reinforce subcontext within a topic. A typical topic/thread could have many separate discussions all happening together (aka thread drift), so quotes help others know what you're responding to. We don't have special handling or references to our blockquotes because there is a history in forums of edited blockquotes.
Perhaps you want to have a block quote and add some emphasis?
It's also better netiquette (god, that term is old) to trim down the quote to only the relevant parts.
Another upside is that a copy-paste of a post preserves that post to history. That can be useful if the quoted user tries to edit their post later, etc.
vis-a-vis the concept of "quote posts", which I take to mean an embedded post within a post, allowing for replies, likes, etc. How that is represented via ActivityPub is probably detailed in some FEP, but NodeBB doesn't implement that yet. It's a more complicated mechanism that requires a lot more thinking through, and to be honest, we haven't had the need for that in the 10+ years we've been building NodeBB.
I have a problem with uploading images, because in order for people to upload images from their phones, usually they can weigh 2-3MB - cropping images works by itself,
but the problem is that after upload image there are two left on the server, the original one and the cropped one, which leads to quickly running out of space on the server.
How to disable the option to keep the original images after upload?
I’ve been playing around with community.nodebb.org, in anticipation of 4.0’s launch, and I’ve noticed that the Lemmy groups I’ve followed don’t appear to be showing up. I can see posts from Mastodon (and whatever else) users that I’ve followed in World, but not Lemmy groups.
Is this expected or intended? Following nodeBB topics from Lemmy has worked OK, so I thought it would be bidirectional.
Though, now that I’m comparing this post on lemmy.ca to that on the mothership, I see that replies from nodebb.org users aren’t showing up on the remote instance, either. Just those from off-site users. I’m caught somewhat off guard by that, too. Is that behaviour expected?
You may have noticed me testing some rich embeds on this forum, or perhaps you've noticed that on this board, pasted links automatically expand/unfurl into a pretty little box instead of staying as a plain anchor.
This is due to the Link Preview plugin, which I started working on last month!
Link Previews
... wait, why did I just paste a boring ol' anchor like that?
https://github.com/NodeBB/nodebb-plugin-link-preview/
SHAZAM!
You can install this plugin by running npm install nodebb-plugin-link-preview, or via the plugin manager. It should show up on any NodeBB v3 instance.
Hello,
I've recently encountered something of the most weird kind : user accounts are mixed up. What I mean is that for example, a user A can login to their account, with their username and password, but will have access to an account B, including settings, emails, posts and more.
It is a profound security issue, and is also causing great confusion.
I've had to restore a backup of the database a few months back, and this issue did not appear at the time. Some accounts do no appear to be affected, as mine for example is normal.
Did anyone else have this issue ? Can I do anything to resolve it ?
I was thinking of deleting all the accounts and re-creating them and inviting the users to reset their passwords en masse, for example by exporting all the users to a CSV and then re-inviting them, but I am not sure it will resolve the issue.
It seems as if the user's ID have been linked to two accounts. A strange case of data schyzophrenia.
The forum is also extremely slow and shows a very high mongoDB usage.
Thank you for your help,
Cheers
I'm currently running NodeBB 3.9.0.
I get the nodebb-plugin-composer-quill from github, and the configuration is no problem
[image: 1730097857290-dff81bb8-da8a-4203-b767-0bf9d348f540-image-resized.png]
However,when I want to create a new topic and click it,the composer cant use.
It is like this
[image: 1730098070605-b8a13611-6536-4cfa-bd62-7dafcd4676f7-image-resized.png]
I must solve the question, what should I do?
-
General Discussion
A place to talk about whatever you want
-
NodeBB Development
Stay tuned here to hear more about new releases and features of NodeBB!
-
Feature Requests
You have a cool idea about NodeBB? Post it here.
-
-
NodeBB Themes
A public listing of community themes created by the NodeBB community. -
Technical Support
Need help with installing or configuring NodeBB? Look here.
Copyright © 2024 NodeBB | Contributors