If you look at Wikipedia's list of forum software, it's all ancient except discourse, and discourse seems unlikely to ever be something great for users
Its performance is famously terrible. People often point out how unusable it is unless you have a fast phone and the founder's response to this has been to rant about how Qualcomm sucks and need to make faster processors
@jernej__s@danluu hey, I can provide some context for that. In 2014 or 2015 maybe, we wrote an article for #NodeBB on #Wikipedia, and it got AfD'd for being non-notable. Subsequent attempts to reintroduce the article were immediately deleted, and doing it the "right way" (aka, submitting a draft for review) went unanswered.
Overzealous editors have their fiefdoms and the "list of forum software" is one. No article = no entry, and when we make one we get shut down.
the best thing masto can do right now, imo, is to prioritize features & support for organizing communities.This is why facebook has society in its jaws, people are able to easily create, find, and post in any number of communities they overlap with.
if mastodon or an adjacent fediverse platform can better facilitate self-organizing communities, they will win all the spoils and then some
Shoutout to all of the contributors to SourceGraph whose work was just made closed source, big thanks to SourceGraph for pissing on them, I'm sure they really appreciate it. All those users who thought your FOSS product was really cool surely still think your product is super cool now that you've taken their rights away
@drewdevault I'm not sure why you're being so aggressive right now.
There's no exclusive right to commercialization with #NodeBB, none is expected, and someone could start a competitor with our software if they so wished.
I reached out to try to have a civil discussion about our rationale for requiring a CLA, and to explore alternative solutions, but you seem more interested in shaming others instead of talking.
@ben very neat. My only detraction from this is that it precludes other #foss projects from implementing first-class #ActivityPub support because of its paid nature (but I 100% understand the need to do so, hosting isn't free!)
Bundling the open source server in with a project also seems like it'd be complicated, so at least for #NodeBB it sounds like we may still have to forge on ahead with our own implementation.
@aral ha! As with all abominations sometimes there are places they can be helpful?
I was building out additive permissions in #nodebb when I needed to communicate to the end user that even though a specific privilege was not checked, that in reality, though the additive nature, it may as well have been. (e.g. a particular user group may not have the privilege to post new topics, but if the global registered users group does, then all other groups do too). An indeterminate checkbox was perfect 🤷♂️
Would I be a bad #ActivityPub implementor if I don't maintain a "feed"?
If a post is created, NodeBB would send the Create activity to all of the author's followers, and that post would be displayed on that app, usually in the form of a feed.
On the other hand, if other apps send Creates to me, I can save them, but there's no place to display them organically within the existing forum structure 🤔 — since they're not part of an existing topic/category/etc...
@steve@mariusor am I reading this right, that if you didn't happen to already be around to receive the Create activity from a Mastodon instance, you're SOL and you'll never be able to retrieve it (at least within the bounds of the #ActivityPub spec)?! That's ... a choice, I suppose.
As for intent in the original toot, I am referring to S2S implementation. #NodeBB will definitely have an S2S inbox endpoint.
@underlap content migration has historically been a difficult problem to solve simply because all these companies and softwares operate in pseudo-competition with one another.
For example #nodebb can migrate posts from #phpBB#vBulletin etc., but it's all custom migrators.
Something as simple as a common format for data portability would go a long way towards ease of content migration.
I am not certain many users elect to use or not use platforms based on portability though.
I'm looking forward to talking more about #NodeBB and #ActivityPub integration on here again, been distracted lately with other technical debt items — and of course — work to put food on the table 😄
Not going to lie, one of the support services is "mentoring on community building". You'd think the co-founder of a COMMUNITY BULLETIN BOARD SOFTWARE would be aces at building community, but truthfully, I really suck at it.
The fact that "build it and they will come" worked at all is miraculous.
I've said it before and will say it again, that the #NodeBB team for the past ten years has been graced with a huge amount of luck. With the right people just happening to come along at the right time, to clients taking a chance on a trio of literal nobodies, etc.
That kind of luck doesn't last forever, and so I'm very excited to work with the @NGIZero to really supercharge our #DevRel
@thisismissem@NGIZero I've been passively noting that you've been working on trust & safety in the #fediverse, is that right? Definitely something we'll want to discuss sooner rather than later — bridging #NodeBB's built-in moderation tools with fediverse standards would be a win for us all.
This #canadaday weekend, traffic increased so much on #Mastodon that I think my little cloud VPS is starting to struggle to keep up with the volume of incoming content. My feed is about 15 minutes behind, currently 😬
I think I may just throw in the towel and move on over to #mastohost
@multiverseofbadness@Jerry yeah I'm used to #NodeBB running on a potato server, so I was really surprised that a single-user instance needed such beef.
Although I guess 2GB is not a lot of beef. It's all relative 😁
I'm simultaneously excited and dreading to see how NodeBB can handle a really active inbox...
When seeking support or sharing feedback about software/website, which platform would you prefer to use? Please share your reasons in the replies (if you wish).
Still looking for responses to this one! Also I should've probably included hashtags, however I can't edit the post because that'll reset votes. I don't remember if hashtags work for replies, but probably worth a try: #Survey#Poll#Discourse#NodeBB#GitHub#Discord#Forums.
Public group chats (!!), FontAwesome Pro support, better dark mode, among much much more!
We're really happy with the latest changes to the #chats system. Who needs #Discord anymore when you can have a kickass #forum system with chats subsystem that is on-par with Discord? 😊
🌠 Did you know that #NodeBB now supports public chat rooms?
tl;dr — The upcoming 3.3.0 release will add support for public group chats and allow bigger rooms. 🎊
We've put in a whole bunch of effort to refactor the chat system to support this, bringing us just that little bit closer to replacing incumbents like IRC/Discord/Slack, check it out on our forum, or take a stroll down memory lane and read up on the history of our chat implementation 👇
Special shout-out to @nodebb for bringing this amazing #foss#opensource platform 🙂 with no strings attached.
Considering things that recently happened to #unity#unity3d it is absolutely necessary to take everything into consideration before committing into a #proprietary software.
Back in late July, we took a chance and applied for the @NGIZero NGI0 Core August 2023 call for projects. Our application dealt almost entirely with bringing #ActivityPub to #NodeBB, and we're happy to announce that we've been officially greenlit!
Looking forward to working in tandem with some other highly esteemed colleagues @helge and @tchambers with their testing suites too 🙂 (edit: @J12t too!)
The other small part of our application dealt with much-needed accessibility audits and fixes 💪
We sometimes field requests from people who want to import their existing users in from a separate user database. While we normally recommend the use of a single sign-on plugin (#sso) to act as an alternative authenticator, we also now support user import via CSV.
More updates to the chat UX (pinning, public room notifications, real-time typing notifications), improved user moderation tooling, post queue updates, and as usual, lots of bug fixes 😳