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

@skyfoxx @AltCode@social.vivaldi.net I... don't know what I did, but kbin.social is down now! Oh boy.

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

Error 405 Not Allowed after trying to reply and hitting Submit button.

When you click on the world/all icon, the world/curated icon also highlights

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

ActivityPub user profile > Flag Profile window:

It looks to be an API call and returns {"errors":["Bad request"]}. /ap/actor/ae0fea90a57bf109abf03f47806c7285 tells nothing to end user so it would be nice to change it to something familiar for local community or Fediverse handle.