@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?
@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?
Hi @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.
@[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.
@[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.
@[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.
@[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.
@[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.
@[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:
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.
@[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 no inReplyTo
or is unprocessable.
@eeeee said in Do you have limited or full access to your host?:
I did have this conversation previously with @phenomlab, and I recall we were looking at around $40 a month upwards for a dedicated host
If you're fine with Oracle and willing to ensure there is some constant load on your server (from my experience just running Mongo+Redis with some cache for NodeBB will do fine for their usage detection), Oracle Cloud Infrastructure is still waving a huge free tier carrot in the form of 4 ARM64 cores w/24GB of RAM w/200GB total disk space (you can distribute these across up to 4VMs)
Otherwise - Hetzner has a great offer. NodeBB deployments are mostly RAM-bound, so I'd personally go for ARM here too - since NodeBB doesn't really have any x86-specific dependencies (also, if you want to save a buck, or rather €0.60, you can put an IPv6-only server behind Cloudflare and get IPv4 connectivity for free ).
You really don't need dedicated unless you really have a lot of users - it may be worth it if you want to host many services (since you can run your own VMs there) or if you actually need a full CPU-worth of performance, but again - the heaviest part of NodeBB is typically the database (and maybe caches), you're almost certainly not using that much processing power to serve a forum
(As for the experience topic, I'm not sure if I can really comment when I'm still in my early 20s, below the lowest concrete number thrown here )
@[email protected] this is a political fork, like that time io.js was a fork of node.js (and humorously, another fork called ayo.js, too).
@[email protected] @[email protected] a federated StackOverflow would be an excellent use case that would benefit directly from the work ForumWG is doing (yes, "Forum and Threaded Discuss Task Force" is the official name, but ForumWG rolls off the tongue better, no?)
Dan, if you're interested, the WG meets up first Thursday of every month, 11am Mountain Time.
The built-in email service is an SMTP emailer. So you'll need to set up SES via SMTP:
Send email through Amazon SES by using the SMTP interface.
()
I haven't used the SES preset, you may need to set custom SMTP settings manually instead.
(BTW, it's not a plugin, it's built into core)
First off, I don't recommend using sendmail. It's very likely to be caught in spam filters.
How do you know that an email wasn't sent? Have you checked the mailbox on your server?
@[email protected] right. I think functionally I'll never encounter a Delete
, check the origin, and find that the note hasn't actually been deleted, but stranger things have happened!
@[email protected] yes! I've had great success with http://vanilla-js.com
@[email protected] I am building ActivityPub integration into the next major version of NodeBB. It is still in development but moving towards an alpha release soon
@[email protected] what you're experiencing is a protocol that is largely still in development. The specification is largely solidified but implementations differ widely for numerous reasons.
I implore you not to write off the fediverse for those reasons, ActivityPub is still in a nascent, growing stage, and rough edges will be smoothed over in time.
To expect a panacea is naive at this time, but the optimism and potential are both there.
@eeeee said in Reconciling ActivityPub Deletes with NodeBB deletion:
The only thing Delete then Purge does is add extra step to removing something!
Technically they needn't be two steps. You could just go straight to purge.
We toyed with the idea of removing deletes altogether... not sure where we landed haha @baris?
@[email protected] — interesting idea, but my gut feeling is no, because post visibility (which at present, NodeBB doesn't even support at all) and deletion are two separate properties in ActivityPub.
One is defined in the object itself (to
, cc
, etc.), whereas if a post is deleted, it simply ceases to exist or becomes a Tombstone.