Troubles joining group with Misskey

[Ranger234]

Hello,

I run into troubles joining (follow) a group with Misskey. I go to a.gup.pe, select a Group enter my account and commit the appearing question. Then The group "following status" freezes at "Processing".

Is there something i can do?

Best Regards
Thomas

[wmurphyrd]

If could could tell me your server domain I could look for something in the logs. I can see successful follows & deliveries with several misskey servers in there

[Ranger234]

My Domain is @misskey.wimmer-edv.de

[wmurphyrd]

I can see lots of successful deliveries to one user on that domain, meaning Guppe views them as a a group member (accepted follower) for at least one group.

So it's not a general compatibility issue. If you're not receiving posts from that group, you might try undoing the follow and trying again.

[Ranger234]

I followed Your advise (restarted my server to end "processing" status) and initiated the Follow Process again. The Result remains the same.
Is there any Problem to post the user and the Group here?

[wmurphyrd]

No problem from my perpsective as long as you don't mind sharing

[Ranger234]

Its a scocial media account, so sharing should be its destination. @thomas@misskey.wimmer-edv.de is the user and @askfedi_de@a.gup.pe is the account. The following status is "processing" and i do not get messages from @askfedi_de@a.gup.pe

[guysoft]

I am getting similar issues from Pleroma. Server is https://hayu.sh I can't # to the group I created @israel@a.gup.pe

[carbontwelve]

Could this be because neither Pleroma nor MissKey servers support the group actor type?

[guysoft]

What is the actor type on guppe?
I am actually implementing this trying to copy the group model here: https://github.com/yuforium/activitypub-docs/blob/main/federation.md

[carbontwelve]

@guysoft its Group:

curl -H 'accept: application/activity+json' https://a.gup.pe/u/askfedi_de

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/security/v1"
  ],
  "id": "https://a.gup.pe/u/askfedi_de",
  "type": "Group",
  "inbox": "https://a.gup.pe/u/askfedi_de/inbox",
  "publicKey": {
    "id": "https://a.gup.pe/u/askfedi_de#main-key",
    "owner": "https://a.gup.pe/u/askfedi_de",
    "publicKeyPem": "-----BEGIN PUBLIC KEY-----\nMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAvUGYkiqMxk1SdqXlipoj\nkeeLx67X/hjGRPjwcd5Q+2w4rvKKBokNvDG7kD71oZeO07rS80H1uoJ7fhANuSSq\nrI+wDMcbjuovc8o43ABwktp+fmEN7gkmcbua1D2I+yG4I4z3y6eTk9FZgF1+P1iX\nO8aNWGZUSA0E2QGDVkXnUvHWgQSmdLGsF9NkWKb/YvP1MJwhvrBrnse7UaP0exos\nBLINu+ExGHG0eADm1hIa+g2UanrpODPgs1xBtUqobqG6OxyULuXHtAYBgtf4Tpd2\n+rpeBrHgiKuo/wKRyQda8yq3bj3Jtt9PUU8vxoYX/LRYeDyYajVKqXXwX54n819N\nZLi7KICn4Q/VQIS6BRYwomfWRU4QY7wNA4LVxx++vYSXMsrJNESs2B7lBxvBzJIP\nq+9wnJHtPFKz16Jz35gUpGdXLfw7oD9tMrR3jdRSvcDlf2mR/F5o0kZJn/AK9jtN\nZ50ZH8PclDCY7P0FPoUWpYxhopKByLVmfnldfD9Tkwu4qORg/+MQl+tjrzjjw+3p\n4h9bg/2jRLGnAI8Ui3XBkgwGils05lUjMwnslaPWG054/r+a7EN+BIG1EqZKJ9Hs\nbYdJbzDxGbSWfYtBuDCZqGGWH+9jUqPfEsgWbvWNlCS20EDYAGV8BVJg891I+OYc\nrlFsgyzxREWXtnZGI3ZgWhcCAwEAAQ==\n-----END PUBLIC KEY-----\n"
  },
  "followers": "https://a.gup.pe/u/askfedi_de/followers",
  "following": "https://a.gup.pe/u/askfedi_de/following",
  "icon": {
    "type": "Image",
    "mediaType": "image/jpeg",
    "url": "https://a.gup.pe/f/guppe.png"
  },
  "liked": "https://a.gup.pe/u/askfedi_de/liked",
  "name": "askFedi_de group",
  "outbox": "https://a.gup.pe/u/askfedi_de/outbox",
  "preferredUsername": "askfedi_de",
  "summary": "I'm a group about askFedi_de. Follow me to get all the group posts. Tag me to share with the group. Create other groups by searching for or tagging @yourGroupName@a.gup.pe"
}

Actor type is set here: https://github.com/wmurphyrd/guppe/blob/main/index.js#L69

[temtemy]

I can follow Guppe groups now from Misskey 2024.3.1. I wonder if anything changed from Guppe or Misskey 🤔

[guysoft]

@temtemy I solved my issue on Pleroma, by finding out that on the DB the main instance was marked as down. And after clearing that directly entry a.gup.pe started working.
I would test against more than one guppe server to confirm that its a instance-specific issue. And not the whole guppe codebase.