General Discussion

Your English is written fine, but I'm not sure what you are trying to do? For example, to see all your posts I can click on your profile, then click posts and see everything you have posted. That might not be what you mean? I'm wondering if you are saying: 'show the opening post, but hide replies?' or 'keep replies anonymous' maybe? But why would anyone want that? Can you explain more on what you are wanting to achieve?

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

I'm not sure Sylvester speaks for everyone (or at least me), and I want to offer my perspective. Personally, I think NodeBB is an amazing product. I've probably installed it 20 times or more across various environments; Ubuntu, RHEL, OpenSUSE, and even created a Docker instance for testing. It’s a fantastic piece of software with a lot of potential. That said, my needs eventually led me in a different direction. I was looking for something more enterprise-ready, more sysadmin-oriented, and a bit more aligned with my development style. The NodeBB team is incredible, and they were very supportive during my time using it. But ultimately, time was a critical factor for me, and I needed a platform that I could build on quickly without hitting too many roadblocks. Since I had an extra $500, I decided to give Invision Board a shot. In just a few days, I was able to build a custom template in about 2 hours, create webhooks, make API calls, and develop a few applications. I even put together a IPS database viewer that interacts with a PHP script to pull database info, convert it to JSON, and display it in a way that allows me to track changes, drill down into data, and generate reports. NodeBB is definitely going places, and I still think it’s a great platform. However, for my specific use case, building features like Clubs, Articles, Blogs, Galleries, Coding Snippets, Wikipedia API integrations, and more, I needed something that offered those tools out of the box or with customization that I can develop with. I spent a week trying to build a custom template in NodeBB and couldn’t get it right, whereas I built one for Invision in just two hours, and I had my additional features up and running within four days. At the end of the day, it comes down to finding the right tool for the job. NodeBB is a fantastic project with a bright future, but Invision was a better fit for what I needed right now. Please don't hate me NodeBB peeps... I will be using this system on my clients (with a subscription so I don't have to host it ) and still give the praise!

@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.

The 2024 IFTAS Needs Assessment Report is Here!We are pleased to to announce the release of the 2024 Fediverse Trust & Safety Needs Assessment Report. This annual report is a cornerstone of our mission to support the decentralised social web with evidence-based research and actionable recommendations for moderators, community managers, and administrators.This year’s report reflects the insights of 183 services spanning platforms like Mastodon, Lemmy, and Peertube, collectively hosting over 4.3 million accounts. This year we also heard from volunteer independent moderators on Bluesky. By analysing the experiences and feedback of these moderators and admins across the Fediverse, the report highlights the challenges and opportunities within this rapidly evolving ecosystem.We will follow up with an analysis of what we’ve seen change since last year’s report, as well as key resources we think can help solve some of the needs identified.Key FindingsResource gaps – only 16% of communities have 24-hour moderator coverage, and nearly half of moderator teams lack formal guidance. That said, we see roughly one moderator for every 1,200 active accounts.Top ranked priorities – moderators need tools for CSAM detection, spam prevention, and legal guidance for compliance with regulations like GDPR.Burnout is a persistent issue – one in five moderators report experiencing trauma or burnout this year, underlining the need for wellness and resilience resources.Financial struggles – most communities operate on donations, and overall our survey participants are not generating enough money to cover costs. Very few moderators are receiving any compensation for their labour.IFTAS InitiativesInformed by last year’s findings, IFTAS has developed several solutions and programs, including a Fediverse CSAM scanner, a comprehensive Moderator Handbook (coming soon), and the creation of FediCheck for automated denylist management. Moving forward, we aim to expand resources for moderator wellness, launch our CSAM scanner for broader use (please register your interest), improve tooling for non-consensual image detection, and introduce new community guidelines templates.We encourage everyone in the Fediverse community to read the full report for a deeper understanding of the challenges facing decentralised moderation and the innovative solutions underway.️ Read the Full Report HereGet InvolvedIFTAS thrives on collaboration. Join our community of practice at IFTAS Connect, use our resources, or support our mission with a charitable donation to help make the Fediverse a safer, more inclusive space for all.Let’s work together to empower moderators and create a stronger, safer social web!#TogetherStronger #ActivityPub #BetterSocialMedia #Bluesky #Fediverse #TogetherStronger

Try now, if it doesn't work. Then log out and log in, it should work then

@baris wonderful! it works. Thanks.

I've added this to a template I am building. Nice work. Simple, yet effective!

@codenamejessica no problems. It's standard GET and POST variable passing which works fine with same-origin