@PitaJ nice catch!
Translators
Contributors for NodeBB Internationalisation
Posts
-
Need Assistance Configuring SMTP for Email Notifications in NodeBB -
Facing Issue in Adding Custom Fields to User Profiles in NodeBB for RPG Forum@Alexis-Sanchez There's a guide I've written for working with custom user fields in the user hash, but front-end wise you're looking to have a custom theme add the fields to the profile pages.
Do you already have a custom theme?
-
Need Assistance Configuring SMTP for Email Notifications in NodeBBHi @Phill-Jones, what SMTP-based MTA are you using?
If NodeBB reports that an email is sent, then that means it has done as much as it can on its end to assure delivery. Essentially, it's handed off the letter to the mail carrier, but whether it arrives is a very different story.
It could be that the MTA didn't receive it, or received it and didn't accept it, or it routed the mail but the receiving end classified it as spam... etc.
-
Traversing the reply chain when working with topics@[email protected] said in Traversing the reply chain when working with topics:
infinite inReplyTo chain.
I think this could be solved in part by the chain traversal sanity checking to ensure that the id is not already retrieved, but I'm not naive enough to assuming that that can't be circumvented.
... so yes, in that sense a limit makes sense from a security standpoint.
-
Anyone building a federated Stack Overflow?@[email protected] said in Anyone building a federated Stack Overflow?:
Personally, the "accepted answer" is the killer feature. Dunno if NodeBB, Kbin, or others already support this.
Yes! NodeBB's been around for a decade, we have tons of stuff that got built because people wanted it.
So yeah we have a plugin that already does full question-and-answer support. We use it on our forum: https://community.nodebb.org/category/16/technical-support
Note the "solved" and "unsolved" labels, and descending into a solved topic, you'l see the accepted answer floated to the top.
NodeBB's theme and plugin engine is very flexible, so it is feasible to stand up a StackOverflow clone rapidly.
-
Well written article with many good reasons to NOT fork Mastodon.@[email protected] you don't need to fork for political reasons, that's what I'm saying.. my response was mostly flippant and tongue-in-cheek.
Especially since right after I posted it, I looked into io.js and discovered that it was actually widely considered a successful political fork. It no longer exists but achieved their goals.
-
Anyone building a federated Stack Overflow?@[email protected] @[email protected] may I pose a question?
What is the actual difference between a site like StackOverflow (or their sister sites on the exchange) vs. a forum with a question-and-answer functionality built in?
At its core, as Ben alluded to, each question is essentially a "topic/thread", with immediate replies considered "answers", and further sub replies considered "comments".
An accepted answer needn't federate, though it can always provide that information via a separate ActivityStreams property.
My assertion isn't that StackOverflow does anything different "technically", but that their network effect and centralization, along with being the only good option to ExpertsExchange, allowed them to prosper.
-
Traversing the reply chain when working with topics@[email protected] said in Traversing the reply chain when working with topics:
You could be sent a random Note inReplyTo an unrelated Note that's part of a large chain which you end up traversing for no reason.
Another legitimate concern. My counter is that traversing the chain is rather inexpensive:
XHR => (do other things while waiting) => inReplyTo? XHR...
etc.Actual note processing is done only once the chain is complete, and a positive relation is found.
... but I can see how this could lock up the process in other languages where processing literally stops when waiting for the XHR to complete.
-
Traversing the reply chain when working with topics@[email protected] said in Traversing the reply chain when working with topics:
more replies from Mastodon might be missed than is ideal
You are not incorrect. In practice the following situation happens occasionally, especially in larger/busy topics:
- You post a reply to a topic/thread (branch A), but a different branch (B) of the topic occurs outside of your view (since the activities are not forwarded to you)
- Later on, someone you do follow replies in branch B, and you receive it.
- Traversal finds 20 posts in between you missed, and they are all added at once, and you receive the notification of new posts in the topic, except now all of the "new" posts are scattered throughout the linear flow
- Additionally, some of these new posts might appear in places higher up than where you last read
So this violates the assumption (at least in NodeBB) that if you have a "read up to" point in a topic, that there will not be new content above that point.
@[email protected] said in Traversing the reply chain when working with topics:
is it still right to say that those replies are part of your topic in a coherent sense?
From a purely technical point of view, yes, they are part of the same context (at least as derived via reply chain traversal), but from a UX POV, you could make that argument.
A forum with a linear flow of posts tends to diverge less often due to the nature of the presentation of posts themselves; something threaded models don't need to contend with.
-
Traversing the reply chain when working with topics@[email protected] may I ask why you add a limit to the traversal logic?
I can see an argument made against doing so if it locks up the process, but the downside is you'd still have some cases where you don't get the full context.
Either way this may be moot if an iterable context is found, so
inReplyTo
traversal is ideal as a fallback mechanism.Edit: in NodeBB's case, we call an internal recursive method called
getParentChain
which just makes the S2S call and adds it to a Set. The method terminates when it encounters an object with noinReplyTo
or is unprocessable.