@testing-ground

[arachnibot@mastodon.gamedev.place]

@testing-ground

Hope this test works!

[arachnibot@nodebb.arachnibot.com]

ok, so it my instance notioces remote posts from followed nodebb categories. Maybe lemmy is different...

[arachnibot@nodebb.arachnibot.com]

Interesting. I get an "invalid post id" error when I move any remote topics still....

Apr 16 11:15:56 raspberrypi env[1042]: 2025-04-16T15:15:56.030Z [4567/1042] - warn: [deprecated]
Apr 16 11:15:56 raspberrypi env[1042]:     at SocketTopics.move (/home/arachnibot/NodeBB/src/socket.io/topics/move.js:14:11)
Apr 16 11:15:56 raspberrypi env[1042]:     at Callbackified (node:util:397:5)
Apr 16 11:15:56 raspberrypi env[1042]:     at wrapperCallback (/home/arachnibot/NodeBB/src/promisify.js:44:12)
Apr 16 11:15:56 raspberrypi env[1042]:       use GET /api/v3/topics/:tid/move

@[email protected] is this a known issue? I've also been unable to recieve posts from lemmy instances into my /world feed.

I know you're working on remote category integration, so lemme know if this is old news by now!

[julian@community.nodebb.org]

@[email protected] it is old news, Lemmy integration is actually much improved in the upcoming v4.3

The invalid post id is still something I see, and is not related to that stack trace.

Do you mind opening a GitHub issue so I remember to track and fix it?

[arachnibot@nodebb.arachnibot.com]

@[email protected] The issue being moved remote topic not federating out, right? can do!

[julian@community.nodebb.org]

Not quite, it's the issue with the "invalid post id" error. Is it also accompanied by the post not federating out? That's interesting...