Maybe a basic question, but Im not sure, until theres a pre-release of Nodebb v4 (which I cant wait for!)
But will my forum fediverse account be enough for an all in one solution, so I wont necessarily need my Mastodon account too?
The reason Im asking is because, at times, ideal Mastodon hosts can be hard to find. I ran my own instance for a while, and many signed up - it was bursting at capacity before long 🙂
So will a Nodebb v4 forum account be complete enough to be a full fediverse solution for those who use Mastodon etc.
Can I log into the fediverse mobile apps etc?
I tried logging into a couple I have on my android phone but it didnt work.
Not sure what my nodebb fed password is, (is it mirrored from my main account) or how to reset it?
1000016862.jpg

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable 😅

Prior our last task force meeting, @[email protected] brought up the need for a common nomenclature for ease of communication between ActivityPub implementors. Rimu also took the initiative to conduct an informal survey to see what terminology was used across fediverse-capable software (and some non-federating software).

Going beyond "toots" vs "posts", it was noted (not surprisingly) that each software has their own name for things.

The most common object type passed around via the ActivityPub protocol (as:Note) could be called a comment, a post, or a reply A grouping of as:Notes could be a post (!!), a topic, a thread, a conversation, or a discussion A higher order grouping of those could be a community, a category, a forum, a (sub)tag, a group, or a magazine

The main takeaways were that while there was occasional convergence, it wasn't entirely surprising that there were more names for things than things to name. Secondly, it was fairly clear that putting forth a recommendation to align on nomenclature would be fairly futile.

What were we expecting... naming things is, after all, one of the hard problems in computing.

All joking aside, up with a common terminology — a lingua franca (thanks @[email protected]!) — definitely has some advantages.

What terms do you think communicate these levels of organization most succinctly? Let us know!

I am very new to node BB. Just installed on a ubuntu VM. I did not find a way to add external link that we see in community.nodebb.org website. "Buy Hosting" and few more links right to that. Is that possible without doing code change ?

Screenshot 2024-04-16 at 9.55.27 PM.png

i will not rest until fedi devs start using as:context properly. this is my single-issue. /hj

I'm going to setup automated Nodebb on Different Server. I need example of config.json.

I would love to see a feature where one can post messages on user profiles.

For example if a user have there birthday, anyone can post happy birthday on there profile page as status updates.

The user himself can update there status as well for example sharing there images etc.

bd5804a5-5cf4-4251-8d9d-f45abc1c9fd5-image.png

I have never really done much with email in all my years of working on the web, and now I have a need. I have the NodeBB mailer setup with an SMTP email on my domain, and it works for pretty much everything except sending to Gmail accounts, and that is a problem.

I read:

https://community.nodebb.org/topic/15072/nodebb-email-options?_=1711731561044

It hits the high points but did not really help me on next steps. Is there a good guide for diagnosing and resolving issues? Or how to best setup an email provider to make sending more successful?

All input is appreciated.

NodeBB is at this year's FediForum, and one of the breakout sessions centred around the Theadiverse, the subset of ActivityPub-enabled applications built around a topic-centric model of content representation.

Some of the topic touched upon included:

Aligning on a standard representation for collections of Notes FEP-1b12 — Group federation and implementation thereof by Lemmy, et al. Offering a comparatively more feature-rich experience vis-a-vis restrictions re: microblogging Going forward: collaborating on building compatible threadiverse implementations

The main action item involved the genesis of an informal working group for the threadiverse, in order to align our disparate implementations toward a common path.

We intend to meet monthly at first, with the first meeting likely sometime early-to-mid April.

The topic of the first WG call is: Representation of the higher level collection of Notes (posts, etc.) — Article vs. Page, etc?

Interested?

Publicly reply to this post (NodeBB does not support non-public posts at this time) if you'd like to join the list If you prefer to remain private, please email [email protected]

As an aside, I'd love to try something new and attempt to keep as much of this as I can on the social web. Can you do me a favour and boost this to your followers?

coming soon: fep-9988 "Federated Forums" -- this should get the #forasphere conversation started...

Hello all,

It's been quite a cold and rainy March and April, but with a couple nice days in between and warmer days ahead, I'm looking forward to getting outside more.

In the meantime, there's been quite a bit of compatibility fixing and incremental updates to the ActivityPub branch, so there hasn't been anything major to report, but nevertheless, we're getting closer and closer to an alpha.

@oplik0 has been helping me this month with some of the trickier aspects, so thank you!

Here's a short summary of what's been tackled on our backlog, in no particular order:

Posts from the fediverse can now be linked to, if you wish to share them with others. The "Copy Permalink" button will copy a shareable link to your clipboard, and "View Original Post" will allow you to view the content from its original source instance.

e8ed6153-9dbc-497d-b1f0-41a4d0bd2299-image.png

You are now able to see posts from remote users

Minor improvements to mentions so they don't (hopefully) get turned into link previews by Mastodon.

Updates to our link-preview plugin so that uploaded images and external links are added to the attachment property for other instances to consume.

Ability to view Popular topics known to this instance, sort of like Mastodon's "trending" feed.

Next up would be bigger items like content pruning and better reply handling.

In coordination with @[email protected] from Discourse, we are also working on our category-to-category mirroring implementation. This would be used by the SWICG Forum and Link Sharing Task Force, since we're hoping to have asynchronous discussion via the fediverse.

Finding time to test is hard given our respective time zones, but we're getting close!

Last Meeting Recording https://us06web.zoom.us/rec/share/4hGBTvgXJPlu8UkjkkxVARypNg5DH0eeaKlIBv71D4G3lokYyrCrg7cqBCJmL109.FsHYTZDlVvZXrgcn?startTime=1712254114000 Passcode: z+1*4pUB Minutes To refresh your memory, you can read the minutes of last week's meeting

The communtiy (https://forum.orleu-edu.kz/) has been taking a long time to load for a month now. I have already created several topics in order to solve my problem.

https://community.nodebb.org/topic/17887/please-help-me.-high-cpu-but-only-25-users-on-system

https://community.nodebb.org/topic/17939/after-scaling-cpu-is-still-high/8

list item

But problem not solved yet. My one process apache proxy version works better than nginx with scaling so I upload all needed screens.

7a877c24-42cd-4a5c-8535-bfbea3aa0267-image.png

c727a3c2-2e08-48d9-bea7-56427daf2b52-image.png

fe59a73c-d64c-4863-8eed-081295f4d706-image.png last logs

For information, also we have a integration between our course platform and community using nodebb read and write api. Registration, join to group, reset password, edit account processes occured using this platform

Hey everyone,

I've been encountering some issues with an API integration on my NodeBB forum lately. Whenever I try to fetch data from the API, I keep getting this persistent error message. I've double-checked my code and everything seems to be in order, so I'm a bit stumped.
I also check this : https://community.nodebb.org/topic/17758/error-permission-for-opt-config-nodebb-in-installing-with-dockerlooker But I have not found any solution.

Has anyone else run into similar API errors on their NodeBB forums? If so, how did you go about troubleshooting and resolving them?

Thanks in advance!

Some interesting feature requests can be found here:
https://github.com/NodeBB/nodebb-plugin-2factor/pull/93

In short:

proposal to move all language files to Transifex and allow translators to work on translating plug-ins (pre-installed/default/bundled plug-ins were mentioned), 123456 vs. 123 456 as common i18n problem not only for Korea and Japan, some other shortcomings from Korean user point of view. Link Preview Image Korean translation by NavyStack · Pull Request #93 · NodeBB/nodebb-plugin-2factor

First and foremost, I wish to express my sincere appreciation for the development of such an outstanding plugin. In my role as the coordinator for NodeBB's Korean and Japanese translations, I have strived to maintain consistency in wording with the primary translation project. At present, numerous default plugins of NodeBB come pre-installed. However, it appears that this applies not only to administrators but also to end-users. Therefore, it would be advantageous to enable the management of built-in plugin translations on Transifex as well. While I currently utilize NodeBB in production, there are instances where certain strings or plugins remain untranslatable, often exposing my users, who are not proficient in English, to such content. Hence, I would kindly request your consideration on this matter. Below, I have outlined several queries regarding the plugin, along with suggestions for enhancement: Some applications use a space character when presenting a 6-digit number. For instance, 123456 may appear as 123 456 when copied to the clipboard. Given the increasing prevalence of users utilizing this feature via a browser extension plugin, I believe enhancing the user experience by disregarding space characters and accepting numbers solely would be beneficial. There are instances where 2FA (Two-Factor Authentication) needs to be input more than once due to specific circumstances. For instance, upon pasting it into a browser or application, users are prompted to re-enter their username and password, even if the values are accurate. This could be due to either rapid typing or previous input. Personally, I circumvent this inconvenience by pressing and holding the CTRL key while performing CTRL + V. (But... sometimes I face Username and Password form page.)However, this workaround may prove inconvenient for the average user. While acknowledging the inherent trade-off between security and convenience, I believe there is room for improvement in this regard, particularly concerning 2FA. Occasionally, upon entering my username, password, and 2FA code, I find myself logged in as a non-member pop-up. This issue warrants attention for resolution. Your attention to these matters would be greatly appreciated, and I am confident that addressing these concerns would significantly enhance the usability and functionality of the plugin. I am currently using NodeBB in a production environment. Hence, updating without translations results in English displaying as is, akin to a bleeding edge situation. I kindly request measures to improve this. You can verify my commit timestamps, which reflect my working pace. There's ample time to pre-translate adequately for any additions. Your cooperation in presenting translation sentences prior to adding new strings would be greatly appreciated. Thanks for your support.

favicon

GitHub (github.com)

After upgrade to nodebb v1.14.0 my recent cards don't show the category image as background.

Write Api( /api/v3/) put,post, returns Forbidden,but get,head works well
78fbb041-1797-4405-bd1f-1212f251e6eb-image.png

2e5d0168-4869-4cdb-b5dd-7cf032cc0425-image.png

Okay, here's a little completely unintentional side-effect that blew my mind.

tl;dr — never miss a popular post again.

NodeBB tracks a number of metrics when the internal methods are called to create topics (or post replies). Metrics such as post counts, vote counts, view counts. It uses those to provide alternative sorting of topic lists — by post, votes, and views.

Incoming content from the fediverse/social web is also run through this same logic, and so those metrics ended up tracked too.

One of our users pointed out that remote topics were drowning out local topics in the /popular route, which makes sense given the imbalance in traffic. Unintentional, but not problematic. I tweaked the logic to filter out those topics unless explicitly asked for.

... and I ended up with this page, which allows you to see popular fediverse topics that my instance knows about. You can even drill down by day, week, month, or all time.

A common fediverse concern is that things get missed. If you live several time zones away from somebody else, you may never see their content pop up naturally in your feed. Trending posts (in Mastodon) addresses this somewhat, though.

It seems without any additional effort, NodeBB has already taken a step towards resolving this issue.

Always wanted to try one but didn't want to pay the premium.

My local co-working space has them so took it for a spin for the tail end of my workday.

Have you tried one? Would you go back?

PXL_20240412_205827831.jpg

Hey @[email protected] — would you be interested in connecting with @Jay-Moonah about having him on a show about the history of podcasting from the POV of one of the founders of Podcamp Toronto? He also founded the Toronto Independent Music Podcast back in 2005.

I was just having a conversation with him offline (how often do we do that nowadays?) and he's got an awful lot to share about podcasting and how far it's come in the years since.

RSS being an open protocol (and podcasting on top of it) sounds like it'd have some overlap with your userbase.

cc @[email protected]