@[email protected] moved when my Framework laptop only recommended Fedora, haven't looked back!
Pop_OS! is great too, used it as my daily driver for many years.
@[email protected] moved when my Framework laptop only recommended Fedora, haven't looked back!
Pop_OS! is great too, used it as my daily driver for many years.
There have been some scattered discussions I've seen over the past year that mention that @[email protected]'s WordPress ActivityPub plugin federates their blog posts out as an as:Note
, and that the only reason this is done is because Mastodon only treats as:Note
(and as:Question
) as a first-class object and relegates anything else to a fallback handler that takes a short snippet of the content, and shows a link back to the original source, thus losing any in-app benefits (boosts, replies, etc.)
Whether this is actually true or not, I do not know. So that's why I'd like to ask Mattias — or anybody else with some context — here.
For reference:
as:Article
: Represents any kind of multi-paragraph written work.as:Note
: Represents a short written work typically less than a single paragraph in length.as:Page
: Represents a Web Page.I have also noticed that Lemmy, perhaps out of principle, sends out an as:Page
for new generated content, and only the replies federate out as as:Note
. It has unfortunately led to some assertions that Lemmy's federation is "broken", even though it is arguably not the case.
@[email protected], care to weigh in?
I don't even blame Mattias for opting to send everything out as as:Note
.
End of the day right now it doesn't matter how Mattias or Nutomic represent their higher-level collection of data, because Mastodon is the largest implementor and neither they — nor anyone else I know of, for that matter — treat anything that's not as:Note
or as:Question
specially.
But that ought to change. The question is how, but this WG is not at the point where we start throwing around decrees and making up standards.
What's important to me right now is what the landscape looks like right now, and why that is the case.
N.B. The discussion here will eventually make its way to online real-time discussion at one of the future WG meetings.
Hey @[email protected] — yes! You're around at a really great time for forums and the fediverse!
Three of the biggest names in modern forum software (NodeBB, Discourse, and Flarum) have signed on to work on ActivityPub, and we're starting to see the fruits of their (our?) labour now. NodeBB users can be followed, and Discourse and NodeBB categories can be followed.
ActivityPub and the fediverse has really enabled us to go in an exciting new direction, and we're stoked to see where it will take us.
Follow me or @[email protected] for updates
@crazycells said in Pre-Alpha ActivityPub-related bug reports:
edited federated posts are not updated on other sites?
We're sending the appropriate activity out (an Update
activity) whenever a post edit takes place.
I believe @oplik0 worked on this a bit, so if there are issues perhaps he may be able to speak to that.
However there is no guarantee that updates are properly handled across the fediverse. Best effort, I guess
@crazycells said:
originally- I just made a comment in a topic, but there it looks like I opened a new topic
That one's because SocialHub (more specifically, Discourse's implementation of ActivityPub) does not automatically traverse up the reply-chain to discover the original post. The original topic pre-dates @[email protected] and I syncing the categories together, so SocialHub does not know about the other posts in this topic. In that scenario, it will create a new topic like you saw.
Had a chance to listen to @[email protected] on WeDistribute's Decentered podcast. Surprisingly informative, and eye opening just how locked down shared hosting providers are.
Things we take for granted like the ability to mount routes on /.well-known
(they could be blocked!)... or that you can't always assume cron is available.
https://wedistribute.org/podcast/wordpress-matthias-pfefferle/
Having used a VPS for years, I would never go back to shared hosting, but you definitely cannot argue with the convenience, ease of use (CPanel, et al.), and most of all, value for money. However, those three come with significant trade-offs in terms of flexibility and power.
Kudos to you Mattias for having the patience to try to get those shared hosting providers to change. If I were in your shoes I'd just tell them to hop on over to a different provider!
@crazycells That's a good question, and not one I'm sure I have the answer for.
It's something I wonder about because it has been said that search engines will penalize sites that contain repetitive content. Does that mean we may see downweighting because federated content can be found word-for-word elsewhere? I don't know.
I think what might be a good practice would be for a site to refer back to the original site if available.
For example, if you inspect the source for this topic, you'll see that it contains a canonical reference:
<link rel="canonical" href="https://community.nodebb.org/topic/17867/pre-alpha-activitypub-related-bug-reports?page=3" />
If this topic appears elsewhere (and it does, on the ActivityPub SocialHub), then it would be better if that site also provided a canonical reference back to community.nodebb.org, but that's not a requirement anywhere at this point in time.
That way, a search engine upon encountering a site, would be able to learn the appropriate original source and weight it accordingly.
Do we start the NodeBB processes on the machine 2 and have the same redis server in the config so the processes can communicate?
Yes
Do we set isCluster to true?
You don't have to set isCluster: true
since you are running more than one process on each machine, nodebb will detect it automatically. You should set jobsDisabled: true
on machine 2 so it doesn't run digests and other cronjobs.
How do we make a MongoDB replica? Do we add the IPs of both mongo instances in the config file of nodebb on both machines?
You can use the mongo:uri
property to define the mongodb replicaset.
@[email protected] it's worth pointing out that both @[email protected] and @[email protected] are active on the fediverse, and it would be absolutely wild if — using ActivityPub — you could post to one blog and have it replicated on another blog automatically as a guest post with linkback to the source.
@xiyohag273 you can use pm2 to manage app.js
not loader.js
@xiyohag273 both are fine, you can also use the built in process handler (./nodebb start)
We recommend systemd
@[email protected] it was actually because of @
in actor IDs - the codepath for choosing a webfinger lookup over just accepting the URL as the ID only checked for its presence, and the code for webfinger lookups was only meant to run for the acct:
protocol.
So yeah, not WP fault at all, just a combination of a bug and missing feature Now both should be fixed.
@[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
@[email protected] Should be fixed now in https://github.com/NodeBB/NodeBB/commit/700016649d25ee5bc6c3fa17e03003677d7f5b5d (not yet deployed here).
The issue was that apparently for the blog actor WP sent actor URI and not username@host
- which AFAIK is perfectly valid, NodeBB just assumed the latter was always the case
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?