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.

nothing happens on click

@julian thanks for your help. we'll jump on that 2moro and report any issues

Found a bug in the: {browserTitle} {function.buildMetaTag} They are not HTML rendering correctly. Its output is rendering: <title>Groups | JBrown&#x27;s Place</title> <meta name="viewport" content="width&#x3D;device-width, initial-scale&#x3D;1.0" /> <meta property="og:site_name" content="JBrown&#x27;s Place" /> <meta property="og:title" content="JBrown&#x27;s Place" /> Also why are there 2 \n or <br /> in the rendering. <title>Groups | JBrown&#x27;s Place</title> <meta name="viewport" content="width&#x3D;device-width, initial-scale&#x3D;1.0" /> <meta name="content-type" content="text/html; charset=UTF-8" /> <meta name="apple-mobile-web-app-capable" content="yes" /> <meta name="mobile-web-app-capable" content="yes" /> <meta property="og:site_name" content="JBrown&#x27;s Place" /> <meta name="msapplication-badge" content="frequency=30; polling-uri=https://jbrowns.com/sitemap.xml" /> <meta name="theme-color" content="#ffffff" /> <meta name="msapplication-square150x150logo" content="/assets/uploads/system/site-logo.jpeg" /> <meta property="og:image" content="https://jbrowns.com/assets/uploads/system/site-logo.jpeg" /> <meta property="og:image:url" content="https://jbrowns.com/assets/uploads/system/site-logo.jpeg" /> <meta property="og:image:width" content="512" /> <meta property="og:image:height" content="768" /> <meta property="og:title" content="JBrown&#x27;s Place" /> <meta property="og:url" content="https://jbrowns.com/groups" />

I don't know what I am doing wrong. 33 hours just in the sidebar and I am not even closer than when I started. If I can just get 1 thing to work, I can figure out the rest. But nothing is working. Anybody wants to give it a go: https://www.github.com/girls-whocode/nodebb-theme-codename Basically, I am trying to make it with the same modules as https://codenamejessica.com the dev site I am building this on is https://jbrowns.com

@baris if the dark theme exposes a sass variable then perhaps markdown could read it

@eeeee The reason for this complexity is that servers require additional configurations to prevent abuse, such as sending spam in bulk. Unlike when you send an email through Yahoo or another email service, where the browser interfaces with their pre-configured servers, NodeBB operates on your server, which takes on the responsibility of sending the email. This means the server needs to be properly set up to handle outgoing email, including authentication, port configurations, and anti-spam measures. As for your home setup, it’s important to note that home labs are not typically suited for production environments. Professional server farms give administrators full control over incoming and outgoing traffic. However, most residential ISPs impose strict controls on what can pass through their network. Unless you purchase a dedicated connection like a T1 line (which can cost approximately $8,000 per month in the U.S.), your home server will be subject to your ISP’s policies and limitations. EDIT: (Sorry, I had to reword all of that, it was a mess).

@eeeee there are a few fixes in the pipeline and there's always work on polish (especially for onboarding new admins), but that can really wait for v4.1 Was hoping for before 2025 but there's no rush, I will likely wait until the new year and cut the release sometime in January prior to FOSDEM.

Thanks for the fast response!

@Kosiak said in Discouragement and user discipline: @DownPW said in Discouragement and user discipline: Many trolls are very intelligent ((weird right? ) and know how to follow the rules while being extremely annoying. Maybe the problem is not with trolls, but with your rules or your idea of ​​who is a troll. Saying uncomfortable things does not mean being a bad person. I am radically against such a system, just as I am against any kind of shadow ban. If you are not happy with the user's behavior, just give him a warning. If you are not on the same page with him, block him. At least it is fair. Shadow bans and similar bullying are mean. oh no no no no. The problem does not come from me LOL You will see when spammers and trolls come to make you miserable on your forum despite the warnings, the private messages by being nice and all the possible ways of doing things well. Blocking him in his circumstances is absolutely... useless In these cases these kinds of options can save your life. The problem is not my definition of a troll but the troll itself

Hi Julian, so it sounds like our client needs to amalgamate the two emails into one so that the button to confirm is given? They've repurposed the welcome template to have a really nice intro to new users and was conscious that the confirmation message may be lost among the helpful info. In terms of what happens: User registers with email address as mandatory, opted in to emails too Admin approves user via the registration queue User gets welcome email but no confirmation email User has pending icon / X after 24h due to email not being verified. Further edit: Apologies Julian, just revisited the translations and can see that welcome.cta does have the confirm your email address prompt via the welcome template. I think there was some confusion that came about as the template was heavily modified and so that was removed...

NodeBB's topic list layout is great for written and media-light content, although it is less ideal for categories which predominately feature pictures. I recently ran into this issue with the Pics and Trips category on the OpenBeta Community. While we've made some much-needed TLC and improvements so that topic thumbnails are better handled and displayed, I did not feel they were adequately prioritised for this particular category. So I wrote the Category Masonry plugin for NodeBB! [image: 1734625210426-screenshot-2024-12-19-at-11-01-07-pics-and-trips-openbeta-forums.png] In brief: Configurable; either by category or by percentage of topics with a topic thumbnail/image Overrides the partials/topic_list.tpl template to display cards Works with custom themes (will correctly override the theme's category.tpl, or the base theme's category.tpl if your theme does not have its own)

@baris yeah, it seems you're right about pagination. They have changed their recommendation it seems. Thanks for getting back.

@julian I'm able to follow @[email protected] , now trying to mention ...

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

@busker Keep in mind that this encompasses uploaded media only. Externally linked media is excluded (so, giphy embeds would be an example that would not be included). Edit: filter:topics.hasThumbs has been added (in addition to already-added filter:topics.getThumbs) so that plugins can append images to the thumbnail list.

@[email protected] that's a good point. Both Lemmy and NodeBB implemented FEP 1b12, which is why those category/community actors share content. So yes, NodeBB's category actors also only share content, and don't produce any of their own.

I just wanted to take a moment to acknowledge how amazing all of you are in working with this system. While this little bug might be frustrating, I’m confident we can figure it out. I’m committed to finding a solution and contributing to making this one of the best systems out there! Thank you for all the incredible work you do. (Besides I like breaking things... Why is it only on a Monday though, Mondays are my busiest days HAHA)

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