ActivityPub Plugin

Plugin
,
409

EDIT

Following issue is connected to @a.gup.pe user. Every federated categories find user @koirat@a.gup.pe and follows it showin status waiting. Changing the page and returning back shows nothing, that following has disappeared.

Categories can follow real humans, though.

That actor is de facto a bot, and Discourse can’t follow bots — but AFAIK it doesn’t identified itself as a bot. And even the issue would be the bottiness (is that even a word :flushed:) Discourse shouldn’t let me follow it in the first place (unless Discourse doesn’t know that in that moment). Anyway, it should not terminate following without telling me. Or did it… I haven’t check out logs, my bad.

EDIT2

This was all I found.

failed to deliver to https://a.gup.pe/u/koirat/inbox 
[Discourse Activity Pub] https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd failed to deliver to https://a.gup.pe/u/koirat/inbox
--- !ruby/hash:ActiveSupport::HashWithIndifferentAccess
id: https://foorumi.katiska.eu/ap/activity/e05428a3d5d0d9637c8b191bc4556063
type: Follow
to: https://a.gup.pe/u/koirat
published: '2025-02-23T07:11:19Z'
updated: '2025-02-23T07:11:19Z'
actor: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
  id: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd
  type: Group
  updated: '2025-02-20T08:03:45Z'
  url: https://foorumi.katiska.eu/c/koiramaailma/33
  name: 'Katiska.eu: koiramaailma'
  inbox: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd/inbox
  outbox: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd/outbox
  followers: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd/followers
  preferredUsername: koiramaailma
  publicKey: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
    id: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd#main-key
    owner: https://foorumi.katiska.eu/ap/actor/b37cda0cddecb02465691872595307dd
    publicKeyPem: |
      -----BEGIN PUBLIC KEY-----
     (This isn’t relevant, I guess. It’s just taking space)
      -----END PUBLIC KEY-----
  icon: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
    type: Image
    mediaType: image/png
    url: https://cdnfoorumi.katiska.eu/original/1X/c51c0a678551648d73e3f8729ec95ecd1fc0bb73.png
  "@context": https://www.w3.org/ns/activitystreams
"@context": https://www.w3.org/ns/activity...

Webfinger finds that a.gup.pe-user, so that can’t be reason for that.

—

Is this an edge case, or am I again trying to do something strange?

Discourse can’t follow Mastodon-lists (and those have own issues in Mastodon too). So I tried a.gup.pe ”pseudo user” instead.

I created @koirat@a.gup.pe by following same user in my instance — it will collect toots where is used tag #koirat (dogs in Finnish, BTW). That went well.

Then I send a message from Mastodon and both, tag and user, were mentioned. It pop up into list, that followed guppe-user.

In my Discourse I asked category X to follow user @koirat@a.gup.pe. I have another category Y following my actor @jagster@kvarkki.nexus, it was in status waiting. So I was expecting to get that message twice, one from me and one via guppe (oh, for f sake, is that the problem :thinking:).

The message sended by my actor was published in category Y, as expected. Category X didn’t get anything delivered by guppe-actor.

When I opened federation of category X, it wasn’t following @koirat@a.gup.pe anymore.

So what are guesses:

  • @a.gup.pe works some different way and Discourse can’t understand it
  • I tried to publish two identifal topics from Mastodon (this I can try easily, will take few moments)

This isn’t purely academical issue, because it would solve out list-problems of Mastodon.