General Discussion

Congratulations! For Wiki more like next 10 years in the editors queue.

@[email protected] reply from nodebb to see if there's an 'actor' in the Create activity

Which theme are you using? With Harmony I still have the menus on the sidebars. And on mobile it is present on the bottom.

I wrote down my reasons for choosing NodeBB in 2020 based on our requirements and the points are still valid. https://forum.faforever.com/topic/1/welcome-to-the-new-faforever-forum/2?_=1737332556769 On top of that it even improved: Read/Write API are now part of core and there is an official OAuth plugin, soon our need for an adapted own plugin will be gone.

Hi, I have another situation where I have different config.json confusing me now. $ cat config.json { "url": "https://oldname1.com", "secret": "xxxxxxxx", "database": "mongo", "mongo": { "host": "127.0.0.1", "port": 27017, "username": "", "password": "", "database": "nodebb", "uri": "mongodb://nodebb4556:xxxxxx@localhost:27017/nodebb" } And... $ cat ../nodebb/config.json { "url": "http://localhost:4567", "secret": "xxxxxxxx", "database": "postgres", "postgres": { "host": "127.0.0.1", "port": "5432", "username": "nodebbgttt56", "password": "xxxxx", "database": "nodebb", "ssl": "false" }, "port": "4567" Both were used, the second is the current one. Both worked but which one is right? The new version is using postgres. Based on your comment, it should be like this; { "url": "https://www.domainname:4567", << nginx proxy port "secret": "xxxxxxxx", "database": "postgres", "postgres": { "host": "127.0.0.1", "port": "5432", "username": "nodebbgttt56", "password": "xxxxx", "database": "nodebb", "ssl": "false" }, "port": "4567" Am I going wrong somewhere even if this works?

Good afternoon, no decision has been made? Perhaps there is someone who can suggest how to make bypasses some solution? What would not be visible deleted posts of users, maybe they can be somehow automatically moved to another section?

@eeeee [image: 1736910127891-83a537a7-3117-4b6f-a978-11d1bd1fd5ab-image.png] I need a way to view only the message of the sender

Friendica, Hubzilla, or streams? All have Facebook-like groups, events, photo albums, etc...

Just a note for those that are using CloudFlare. You may find your site CSS gets wonky after removing some plug-ins. Mine was some that dealt with the editor. No matter what I removed/added back in and rebuilt the editor was really displaying in bad form. Then it dawned on me that CloudFlare does caching. Flushed the CF cache and the editor looks like it is supposed to.

You can use the tag whitelist feature. This limits users to only the whitelisted tags by admins

@eeeee said in Emails still not sending, 535: This is where I get stuck, where is the DMARC/SPF/DKIM configured and what should it be configured as? As mentioned, they are DNS entries. In fact, if I remember correctly (it has been a while since I set up the last ZoHo domain related email) the provide the entries that you need to enter into the DNS listing entry area with whomever you are hosting your DNS with. For DKIM they have help documentation https://www.zoho.com/mail/help/adminconsole/dkim-configuration.html You also have to create your MX entries. [image: 1736590722154-screen-shot-2025-01-11-at-4.17.38-am.png] I think there are SPF guides for ZoHo also, but this is mine and should work as a TXT entry in your DNS control panel for your root DNS entry (sometimes shown as @ in the dns entry panels). "v=spf1 include:zohomail.com -all"

I have seen the environment variables for reading the project, but I still need to initialize the project using these environment variables. const envConfMap = { CONFIG: 'config', NODEBB_CONFIG: 'config', NODEBB_URL: 'url', NODEBB_PORT: 'port', NODEBB_ADMIN_USERNAME: 'admin:username', NODEBB_ADMIN_PASSWORD: 'admin:password', NODEBB_ADMIN_EMAIL: 'admin:email', NODEBB_DB: 'database', NODEBB_DB_HOST: 'host', NODEBB_DB_PORT: 'port', NODEBB_DB_USER: 'username', NODEBB_DB_PASSWORD: 'password', NODEBB_DB_NAME: 'database', NODEBB_DB_SSL: 'ssl', }; What is the docker-composer.yml used for startup networks: 1panel-network: external: true services: nodebb: container_name: ${CONTAINER_NAME} deploy: resources: limits: cpus: ${CPUS} memory: ${MEMORY_LIMIT} environment: - TZ=Asia/Shanghai - NODEBB_PORT=4567 - NODEBB_URL=http://127.0.0.1:4567 - NODEBB_ADMIN_EMAIL="[email protected]" - NODEBB_ADMIN_PASSWORD="xxxxxxx" - NODEBB_ADMIN_USERNAME="admin" - NODEBB_DB="postgres" - NODEBB_DB_HOST="127.0.0.1" - NODEBB_DB_NAME="nodebb" - NODEBB_DB_PASSWORD="xxxxxxx" - NODEBB_DB_PORT=5432 - NODEBB_DB_USER="nodebb" image: ghcr.io/nodebb/nodebb:3.12.2 labels: createdBy: Apps networks: - 1panel-network ports: - 4567:4567 restart: always volumes: - ${NODEBB_ROOT_PATH}/node_modules:/usr/src/app/node_modules - ${NODEBB_ROOT_PATH}/build:/usr/src/app/build - ${NODEBB_ROOT_PATH}/uploads:/usr/src/app/public/uploads - ${NODEBB_ROOT_PATH}/config:/opt/config - ${NODEBB_ROOT_PATH}/setup.json:/usr/src/app/setup.json What I hope for is to achieve unmanned installation

@ANONYMOUSKOREAN the Dockerfile is maintained by the community, since we don't use it at NodeBB ourselves. That said, it would be very appreciated if you were to help keep the file updated

@VE2UWY @Vivaldi DDG is a good choice, but if you want Google results, you might be able to use Startpage or Ecosia as well.

@julian Peertube account follows are now working, but I did not get any video from @[email protected] in my feed yet. Ready to wait a few more days for that. However, (meta) Threads accounts seems to be unfollowable even now.

As the title says. I don't have money to buy a server.

@bboctt Nice nice nice. Okay, here are my thoughts on it... there are some applications for print view even in 2024/2025. One of those is reader mode. For whatever reason, NodeBB doesn't format well at all when sites try to remove extraneous elements and keep just the post text. if you don't care so much about getting the entire topic history, you could just get the existing topic data on-page by querying ajaxify.data. You can retrieve additional pages by passing ?page= param.

Just a shuttlecraft based toy activitypub server running on github workspace

@bboctt oh lord!! The ever-lasting battle between compatibility and adoption of new features. At the end of the day, supporting older browsers gives us enough developer friction as to become a no-go. That's not to mean that it isn't important, but unfortunately that the market share isn't there for us to spend a significant amount of time on it. But let's say... if a big bank came to us and said "This forum needs to work on IE11!!", and was going to spend the dollars to get the software there, then that is a different story. On the upside, though, there are a couple small things we can try to address. The site's client-side js shouldn't immediately crash... stuff should work. It may be worth investing some time into getting the baseline functionality working, if it isn't already.