Test with Kbin

Calling https://kbin.social/m/drupal , https://kbin.social/m/drupal/followers, https://kbin.social/m/drupal/followers?page=1 with the application/activity+json accept header gives a json response, so AP is enabled indeed. The oubox URL is empty though, but that's not necessarily a problem.

I've send a follow request from my own Drupal instance to https://kbin.social/m/drupal and the request was confirmed, but I don't see myself (yet) in the AP followers request. However, the number of subscribers is not 33, and, if I remember right, a few minutes ago it was 32.

So now I have to wait when something arrives in the kbin to see if it arrives to my instance then. Fingers crossed :)

So, good news: messages are arriving in my inbox, cf screenshot

Note: no messages from the microblog, but those area probably not federated. I'm not sure exactly either how these end up on kbin, is that some sort of internal feed it's getting content from ?

I don't see the messages in the main timeline of my reader module. They do show up in the 'local' timeline. To 'fix' that, I probably need to add some code in the AP module, but also in the reader module to query the messages from what I would call a 'group' or so? (Basically, the actor of the incoming messages is not kbin/m/drupal but the actual users, e.g. https://kbin.social/u/symfonystation

I'm going to send a reply on an article which I find interesting somewhere this week.

Updated the issue summary after some initial testing so that I don't have to reread all comments all the time.

THANKS! kbin.social is just coming back online now, but I'll dig into this as soon as their upgrade is complete.

> is that some sort of internal feed it's getting content from ?

As far Kbin's terminology, it is confusing. Lemmy's terminology makes more sense to me personally, but the tech stack (Rust/TypeScript) makes less sense... so here we are.

Kbin Microblogs are basically aggregated content from the fediverse posts (Mastodon = Toots, Kbin = Articles, Lemmy = Posts), based on the hashtags a Magazine user is configured to follow. In this case, you can follow @drupal@kbin.social on Mastodon. A Kbin Magazine = Reddit sub or Lemmy community. When creating a new magazine, it automatically displays the hash of the m/name. In this case everything #drupal. Everyone using that hash shows up as active members of the Magazine even if they have no idea it exists. What Kbin adds to the Mastodon posts is the ability to upvote. Those are Kbin specific and require a Kbin.social account to do... while replies, boosts and favorites are all federated.

To "prime the pump" on Kbin, I've been manually creating Articles with a links to everything appearing in the Planet feed. I've also created https://feedsin.space/feed/drupal-planet, but I'm intentionally using only #planetdrupal to avoid duplicate posting.

Now people like have started posting @kanapatrick@techhub.social have started posting Articles about their own Drupal related blogging themselves https://kbin.social/m/drupal/t/131850/Challenges-and-Concerns-Holding-Ba....

I'm assuming most people are aware of https://techcrunch.com/2023/03/13/wordpress-com-owner-automattic-acquire.... I'm seeing more content in the fediverse coming directly from WP posts. I'm hoping to add some logic to a Drupal instance as Drupal Planet reposter. So rather than posting everything in the RSS like https://feedsin.space/feed/drupal-planet, it would look at the Magazine/Community to see if the URL had already been posted.

What I'm hoping to do is the opposite of what I did with the original post of https://dev.to/kreynen/change-my-view-d8-isnt-the-best-upgrade-path-for-... where I directed users to r/drupal to discuss. What I'd like to see is the conversation about Drupal related content taking place outside of 3rd party comment services like https://disqus.com/ or the blog/CMS itself where yet another account is likely required to participate in the conversation.

It seems unlikely that Twitter will ever adopt ActivityPub, but with Meta's Threads launching this seems like it would give everyone an opportunity to participate in the discussion regardless of the client/services they choose to do it on.