@[email protected] Thanks for changing the time, as it turns out I assumed the times were in EDT when they were actually in UTC, d'oh! Time zones strike again.
On the bright side it does mean now that everybody who answered can make it!
@[email protected] Thanks for changing the time, as it turns out I assumed the times were in EDT when they were actually in UTC, d'oh! Time zones strike again.
On the bright side it does mean now that everybody who answered can make it!
@[email protected] the NodeBB community is updated to include @oplik0's commit, so you can try again
The translations are here for the post queue
https://github.com/NodeBB/NodeBB/blob/master/public/language/en-GB/modules.json#L109
https://github.com/NodeBB/NodeBB/blob/master/public/language/en-GB/post-queue.json#L8-L9
Emojis in notifications are parsed by the emoji plugin https://github.com/NodeBB/nodebb-plugin-emoji/commit/ac774fdff95d40b78c6cee71f523d1fb46ec7b9d
Node.js based forum software built for the modern web - NodeBB/public/language/en-GB/modules.json at master · NodeBB/NodeBB
GitHub (github.com)
Node.js based forum software built for the modern web - NodeBB/public/language/en-GB/post-queue.json at master · NodeBB/NodeBB
GitHub (github.com)
@[email protected] ah sorry, NodeBB cannot accept DMs at this time. Any chance you can message @[email protected] ?
@Nuran-Akimbek your nodebb log shows alot of restarts.
2024-04-24T00:37:17.878Z [4568/111463] - [31merror[39m: NodeBB address in use, exiting...
Error: listen EADDRINUSE: address already in use 0.0.0.0:4568
at Server.setupListenHandle [as _listen2] (node:net:1897:16)
at listenInCluster (node:net:1945:12)
at doListen (node:net:2109:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
2024-04-24T00:37:17.879Z [4569/111464] - [32minfo[39m: 🤝 Enabling 'trust proxy'
2024-04-24T00:37:17.879Z [4568/111463] - [31merror[39m: uncaughtException: listen EADDRINUSE: address already in use 0.0.0.0:4568
Error: listen EADDRINUSE: address already in use 0.0.0.0:4568
Figure out what's already running on those ports. I don't see any error messages other than those.
Have you updated your nginx config to serve assets statically?
@[email protected] any chance you could let me know the json you're sending during the Accept phase?
@[email protected] said:
Can you maybe give me a level where I can post more often?
Done! Your local account just needed a couple upvotes I think, so I did that now.
Hey @[email protected], I looked into it, and NodeBB can successfully resolve your instance actor via webfinger, but cannot make an S2S GET call to https://notiz.blog/@notiz.blog
I receive the following error:
{
"error":"This method requires an authenticated user"
}
Can you show us the output of free -m
?
@[email protected] @[email protected] indeed, four different implementations is not ideal. We're at the point where they're all vying for attention.
Would need to weigh pros and cons of each and see whether there is one winner we can all agree on.
@[email protected] what was the issue, are you not able to follow the blog-wide user?
May I have the handle so I can take a look?
@[email protected] categories in NodeBB are exposed via ActivityPub just like users, so they can be followed by remote users (just like how local users can "watch" a category, I suppose).
We follow FEP-1b12 at the moment, which means all posts are Announced by the category actor to any followers.
@[email protected] I think there's a bit of a push to provide a full fediverse client (that includes two-way interaction between users). That's what the NodeBB integration is trying to do — to be that all-in-one fediverse client.
But the reality is there's no reason you have to do that. Simply federating content out and maybe ingesting responses back as comments would be a feature complete integration as far as I'm concerned! Anything else is gravy.
Thanks @[email protected]! All I did was implement the protocol as many others have done. Half the credit would go to you as well for the other end of the integration!
It is really cool to be able to follow a blog from a forum. Are comments from the fediverse integrated?
Thanks @[email protected] — @[email protected] perhaps you'd be interested in listening in on the next meeting of the Forum and Threaded Discussions Working Group?
We're looking to make some great strides in moving the fediverse away from "just microblogging" to more fully featured protocol usage including richer integration for blogs like Ghost and WordPress (so @[email protected] you are also invited!)
Let me know if either of you are interested and I'll send a mention over your way when there is news.
With the current codebase, making a group hidden also removes it from the badge selection.
I think closest you can get is with the below settings. Group will be visible but you will still need to invite people.
@[email protected] Thanks! That's helpful (the link was purple, so I must've at least looked at it in the past...)
For those implementations using FEP-e232 I can then at least proactively update the anchor.
It's sounding more and more like I'll need to piece together multiple strategies:
@omega Right now in pages where there is a list of topics (e.g. /recent
, /popular
, etc.) there's a filter for "Uncategorized", which would essentially exclude everything else.
It's not as clear cut as excluding or only showing local topics, but that sort of achieves what you want. If you only want to see categorized topics, then you needn't select anything at all. By default, uncategorized topics are not shown.
What I think you're advocating for is a button to filter out ActivityPub topics even if they're categorized. That's where I think I might draw the line, because if a topic is categorized, then it is by that action it is considered (at least by the topic mover) to be related to the overall forum topic.
Thanks @[email protected] — that'd be appreciated!
@[email protected], this would be helpful in NodeBB's case where we have a web app, so rendering a link to something is just an anchor.
I could theoretically override the anchor click handler to do a backend round-trip to check whether we could load the content in-app, otherwise fall back to a regular browser behaviour (a page navigation).
For example, let's say I link out to Evan's profile here. If NodeBB knew that this link had an alternative AP endpoint, then we could redirect the user instead to the local representation of his profile