Misskey support

[hellstabber]

I can't follow the group account from my Misskey account. It's on that screen;

[guysoft]

Ok, I have a guppe server deployed, and it seem like

1. following works.
2. there are 500 error messages in the log when I started to follow it from Pleroma: https://pastebin.com/XhrVr1jh

Its ipv6 only, so if any Misskey users that have IPv6 want to test it then go ahead: https://guppe.gnethomelinux.com/

Its a test server and will go down eventually (or get redeployed)

[guysoft]

Ok, I managed to implement follow on fedigroup both for Mastodon and Pleroma.

There was one noticeable difference in how Pleroma handles the accept response - the id. Mastodon did not look at the id of the message. Pleroma did.

1. The accept activity id has to be unique each time. otherwise Pleroma log says "I already handled a follow request with this id" and discards it.
2. The request id of the object (the one that Pleroma sends to you when sending the follow request) has to match the request that was sent.
3. I confirmed that follow works even if I hide the followers list, just to make sure that is not the case.

This would mean having a look at this section and figuring out if the id is sent correctly: https://github.com/wmurphyrd/guppe/blob/main/index.js#L126

I believe Misskey might have a similar behavior

[BeeFox-sys]

Any news on if this is closed? it seems that i can't follow, nor even view boosts, from akkoma (which is a fork of pleroma so i imagine the issue is there too).

[guysoft]

Hey, Managed to fix it on my Pleroma end, it works - the issue was that the instance went down for a week and was listed as unreachable, I had to update the db entry and it works! @hellstabber it might be worth testing

it might be a good idea to check that entry on your missky server, it might be the issue

[BeeFox-sys]

This was also my issue ^

[wmurphyrd]

Thanks for the reports. Closing this as fixed