@The-SkyFoxx okay, thanks! I'll take a look

hi @julian , although I read these two topics, they do not go away from my "unread list" and "unread count"

@crazycells Should be resolved now.

@julian yes, it is thanks...

Probably a todo more than a bug.

You cannot see posts of mastodon users on nodebb:
https://community.nodebb.org/user/oatmeal@mastodon.social/posts

@The-SkyFoxx correct, that'd be a to do

Used to have follow lists working actually, but then bots started scraping them for data, that was oddly creepy

Breadcrumbs for /world/all and /world are identical?

(clicking on a link in /world/all creates a breadcrumb fro /world)

Some tags in /word/all are not relevant to this instance

Screenshot 2024-03-13 at 10.49.26 pm.png

E.g. When you click the government tag in the link below:

https://community.nodebb.org/topic/29934340-cef1-465f-835b-2dbe293e9972/what-s-missing-from-railroad-safety-data-dead-workers-and-severed-limbs.-thanks-to-government-loopholes-rail-companies-haven-t-been-scrutinized-by-the-federal-railroad-administration-for-scores-of-alleged-worker-injuries-and-at-least-two-deaths.-new...

You are led to a no topics page: https://community.nodebb.org/tags/government

While news works: https://community.nodebb.org/tags/news

I am not sure if this is a bug, or just translations are not updated yet... This is how world and world all looks when I am not logged in...

@crazycells yes, new strings are not sent out for localisation at this point

@The-SkyFoxx Thanks for reporting — this one is related to remote topics not being added to the respective tags' lists in the database.

Yet another thing on the to-do list I'm afraid

@julian said in Pre-Alpha ActivityPub-related bug reports:

Yet another thing on the to-do list I'm afraid

Yeah I figure most things at this stage aren't bugs, but worth mentioning anyway

@The-SkyFoxx Are you still experiencing issues with following remote accounts?

For a threaded conversation, if I am following someone who created a top level post, the expected behavior is that you get to see the whole thread. For some reason, I am not getting all of the replies to the thread. I have to go to the forum to view all of them, and since they never reached my app, I can't reply to them via ActivityPub.

@scott@authorship.studio said:

For a threaded conversation, if I am following someone who created a top level post, the expected behavior is that you get to see the whole thread.

I'm not entirely sure this is the case. Expectation, 100% agreed, but in practice, I don't think that is the case.

For NodeBB to do this would mean that when Create(Note) activity is received in response to a post, that it be automatically forwarded to all the followers of the author being replied to. It can be done, but can't be properly verified because the forwarded activity's domain doesn't match the domain of the sender (me). Any reasonably secure AP implementation should automatically drop it.

I have oodles of ideas as to how to solve the topic of backfill, but message forwarding I don't know about...

@scott@authorship.studio I think I know why this is the case.

For you on Hubzilla, the message as received by NodeBB contains the following collection https://community.nodebb.org/uid/2/followers. The expectation according to the spec states that I must forward that message along to those users. This is so those users would get the whole conversation, and avoid ghost replies, etc.

NodeBB does not do that at the moment. Thanks for letting me know about it.

The thing is, while Hubzilla does this, and even if NodeBB implemented it, Mastodon does not send those collections. When a reply is received, its recipients list usually contains only the person being replied to, the author's follower collection, and anybody else who happens to be mentioned.

So that's the reason why you can't see all of the replies in the thread, because another implementor didn't send them to everybody

It's actually quite interesting that Hubzilla explicitly includes OP's follower collection in the recipient list, I was thinking of doing the same for NodeBB.

@julian It seems like account from community.nodebb.org that contain spaces in their usernames don't properly federate right now. Take @The-SkyFoxx@community.nodebb.org as an example, I am unable to see or manually fetch any of the posts they've made to this thread. In fact I'm not even able to see their profile, I've tried viewing it from Mastodon and kbin, but no luck.

Another issue I noticed is that I am unable to follow @general-discussion and @nodebb-development from kbin. It only seems to be a problem with kbin because I was able to follow those two categories without any problems from Mastodon. Following @activitypub from kbin worked fine though.

@AltCode@social.vivaldi.net thanks! @The-SkyFoxx already stated that they had issues following others, so I think this is directly related.

I'm not sure what the issue is with kbin but I'll have to register an account and find out

@AltCode@social.vivaldi.net in fact, it seems they both could be related to the same bug related to spaces. Interesting.

I have a feeling this might be a one-liner fix

#famouslastwords

@AltCode@social.vivaldi.net said in Pre-Alpha ActivityPub-related bug reports:

It seems like account from community.nodebb.org that contain spaces in their usernames don't properly federate right now.

@julian I tried removing spaces from my username.

But I am still unable to follow anyone right now

Edit: Seems I can now follow. (Maybe changes take a while to propagate?)

However, when I added a space to my username and upper case, I am still able to follow.

TLDR: Fiddling with my username now allows me to follow. But restoring my username to what it was still allows me to follow