I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable

@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...

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable

@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

@skyfoxx you sure about that? I got a follow notification

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable

New bug found @julian
When you try sorting in /world, the posts disappear:

NodeBB Community

A community to talk about development and ask questions about NodeBB modern forum software

NodeBB Community (community.nodebb.org)

@skyfoxx @julian actually, they do not disappear, but it only sorts the posts from people you follow...

@oplik0 any thoughts?

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable

hi @julian , I just wanted to bring this to your attention... I believe @crazycells@community.nodebb.org and @crazycells should not appear as separate profiles on this forum?

@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

@skyfoxx @AltCode@social.vivaldi.net I started looking into this but wasn't able to easily figure out why kbin wasn't able to find the magazine.

I'll admit I can't easily grok kbin's interface... I was able to (accidentally) add General Discussion to the list of magazines, though?

Error 404 - kbin.social

Explore Fediverse

(kbin.social)

I thought perhaps it was related to dashes not being parsed properly by their mentions matcher, but I can't be entirely sure whether the problem is on my end or theirs!

I may regret creating this topic but here goes.

If you experience a bug or other unexpected behavior while using NodeBB and its related ActivityPub integration, please post it here so it can be tracked and resolved.

No formal process as of yet, and we're still at pre-alpha so expect many things to be broken or unavailable

I'm getting this delivery failure trying to send a follow to a category inbox

[Discourse Activity Pub] POST request to https://community.nodebb.org/category/31/inbox failed: Expected([200, 201, 202]) <=> Actual(400 Bad Request)
[Discourse Activity Pub] https://socialhub.activitypub.rocks/ap/actor/797217cf18c0e819dfafc52425590146 failed to deliver to https://community.nodebb.org/category/31/inbox
id: https://socialhub.activitypub.rocks/ap/activity/02feb8d245fa780e4683d03015f1b41e
type: Follow
to: https://community.nodebb.org/category/31
cc:
- https://www.w3.org/ns/activitystreams#Public
published: '2024-04-05T18:09:14Z'
updated: '2024-04-05T18:09:14Z'
actor: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
  id: https://socialhub.activitypub.rocks/ap/actor/797217cf18c0e819dfafc52425590146
  type: Group
  updated: '2024-04-05T12:49:51Z'
  url: https://socialhub.activitypub.rocks/c/meeting/threadiverse-wg/88
  name: Threadiverse Working Group (SocialHub)
  inbox: https://socialhub.activitypub.rocks/ap/actor/797217cf18c0e819dfafc52425590146/inbox
  outbox: https://socialhub.activitypub.rocks/ap/actor/797217cf18c0e819dfafc52425590146/outbox
  followers: https://socialhub.activitypub.rocks/ap/actor/797217cf18c0e819dfafc52425590146/followers
  preferredUsername: threadiverse-wg
  ...

@Angus-McLeod did it just send a 400 or was there an error message involved in the response?

Edit: I added some additional debugging to the S2S validation logic. Can you try to follow @general-discussion@bb.devnull.land? That instance is my testing instance and is a little quieter.