[@silverpill@mitra.social](https://activitypub.space/user/silverpill%40mitra.social) what's the error you see returned by Lemmy?

@silverpill@mitra.social what's the error you see returned by Lemmy?

@julian "data did not match any variant of untagged enum AnnouncableActivities"

@silverpill following you from my Wordpress account, also seems to have an issue with Accept, I haven’t dug into the logs, but the Follow is pending despite receiving your activities

@django Are you trying to follow me or the group @nomadpub@mitra.social ?

@silverpill@mitra.social are you announcing the Accept? I don't think you need to... just a direct accept like with microblogs should suffice.

@silverpill just yourself, but will try the group too!

@julian No, it is not announced. The problem is probably in Accept.object - in my case it is a URL of the Follow activity but some servers expect an embedded activity.

> @silverpill@mitra.social said:
>
> but some servers expect an embedded activity.

Resolvable activities? You compliant software, you.

You should deviate from the AP spec like everybody else

@silverpill@mitra.social @django@social.coop

Sounds similar to the effect here. Follow pending on silverpill.

@silverpill@mitra.social I'm curious to see whether this fails from NodeBB and Piefed too. Trying NodeBB...

Hmm, can't even resolve the group. Bug for me!

@julian Oh. Why it fails? I am curious because it has the same shape as the user actor, only the type is different

@django I didn't get a follow request, so this must be a different problem.

@nick @django I don't see a follow request, but there is a bigger federation problem - your server responds to all my requests with 418 I'm a teapot. So you will probably not see this message :]

@django I see this in my logs:

{"@context":["https://www.w3.org/ns/activitystreams",{"FeatureRequest":"https://w3id.org/fep/7aa9#FeatureRequest","QuoteRequest":"toot:QuoteRequest","blurhash":"toot:blurhash","toot":"http://joinmastodon.org/ns#"}],"actor":"https://mediaformat.org/author/dev/","cc":["https://mediaformat.org/wp-json/activitypub/1.0/actors/2/followers"],"id":"https://mediaformat.org/?post_type=ap_outbox&p=10998","mediaType":"text/html","object":"https://cosocial.ca/users/evan/statuses/116817212125348410","published":"2026-06-27T01:59:31.432Z","tag":[],"to":["https://www.w3.org/ns/activitystreams#Public",null],"type":"Like"}

The value of to property is not valid (contains null

"to":["https://www.w3.org/ns/activitystreams#Public",null],

@silverpill@mitra.social

Thanks for your feedback. Fetched your reply manually to hhmx.de.

Removed the IP of mitra.social from the block list, so the 418 is hopefully gone.

Did an undo on the pending follow.

Send again a follow request.

@django@social.coop

@silverpill thanks for that! Looks like the addressing didnt work as expected

@nick @django It worked

@julian

🥴 https://github.com/LemmyNet/lemmy/issues/6595#issuecomment-4829453169

Am I the only one who sends Accept without an embedded activity?

IMO embedded activity doesn't make sense. It is not my activity, so even if I embed it, the recipient must ignore the value because it can not be trusted.

It's how Mastodon does it so I assume that's what was copied.

Its not the activity itself per se. Its a re-creation of the follow activity I think.

NodeBB doesn't send the whole thing either, just a recreated subset.