My hypothesis on why Lemmy is rejecting valid activities
General Discussion
10
Posts
4
Posters
47
Views
-
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemmy rejects my request with a 400 response with the error message above.
I tested other instances by making the following get request to the root of each instance (thank you, Daniel Sternberg for maintaining curl):
curl -v -H "Accept: application/activity+json" -H "Content-Type: application/activity+json" <url>- With the following results
- Lemmy returns an Application Actor.
- Misskey returns a 200 response in
text/html. - Mastodon returns a 406 response in
application/json. - NodeBB returns
text/html. - GoToSocial returns a 406 response in
application/json. - Mitra returns a 200 response in
text/html. - Pixelfed returns a 200 response in
text/html. - Peertube returns an empty 406 response.
My hypothesis is that Lemmy is rejecting the request because I return
text/plainand/or it cannot handle a response with that content type.To test that I am working on changing the default behavior. I will need to dynamically add a route based on
system.site.page.frontand return a 406 response in JSON. This is simple enough. If my hypothesis is correct, I can also make a merge request into drupal/activitypub module, which would have the same problem. If not, then I’ll need to go digging further. -
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemmy rejects my request with a 400 response with the error message above.
I tested other instances by making the following get request to the root of each instance (thank you, Daniel Sternberg for maintaining curl):
curl -v -H "Accept: application/activity+json" -H "Content-Type: application/activity+json" <url>- With the following results
- Lemmy returns an Application Actor.
- Misskey returns a 200 response in
text/html. - Mastodon returns a 406 response in
application/json. - NodeBB returns
text/html. - GoToSocial returns a 406 response in
application/json. - Mitra returns a 200 response in
text/html. - Pixelfed returns a 200 response in
text/html. - Peertube returns an empty 406 response.
My hypothesis is that Lemmy is rejecting the request because I return
text/plainand/or it cannot handle a response with that content type.To test that I am working on changing the default behavior. I will need to dynamically add a route based on
system.site.page.frontand return a 406 response in JSON. This is simple enough. If my hypothesis is correct, I can also make a merge request into drupal/activitypub module, which would have the same problem. If not, then I’ll need to go digging further.>Mitra returns a 200 response in text/html.
But it federates with Lemmy
>data did not match any variant of untagged enum AnnouncableActivities
Did you wrap your activity in
Announce? -
>Mitra returns a 200 response in text/html.
But it federates with Lemmy
>data did not match any variant of untagged enum AnnouncableActivities
Did you wrap your activity in
Announce?>Mitra returns a 200 response in text/html.
But it federates with Lemmy
My hypothesis is it's the text/plain is the problem, and that everyone else is doing something acceptable.
Did you wrap your activity in
Announce?Is that necessary? I could not find that in the Federation documentation. I know that Lemmy sends Announces out when it forwards activities, but to me when the documentation states
When a user creates a new post, it is sent to the respective community as
Create/Page. Editing a previously created post sends an almost identical activity, except thetypebeingUpdate.A reply to a post, or to another comment as
Create/Notethat means I should do similarly, right?
-
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemmy rejects my request with a 400 response with the error message above.
I tested other instances by making the following get request to the root of each instance (thank you, Daniel Sternberg for maintaining curl):
curl -v -H "Accept: application/activity+json" -H "Content-Type: application/activity+json" <url>- With the following results
- Lemmy returns an Application Actor.
- Misskey returns a 200 response in
text/html. - Mastodon returns a 406 response in
application/json. - NodeBB returns
text/html. - GoToSocial returns a 406 response in
application/json. - Mitra returns a 200 response in
text/html. - Pixelfed returns a 200 response in
text/html. - Peertube returns an empty 406 response.
My hypothesis is that Lemmy is rejecting the request because I return
text/plainand/or it cannot handle a response with that content type.To test that I am working on changing the default behavior. I will need to dynamically add a route based on
system.site.page.frontand return a 406 response in JSON. This is simple enough. If my hypothesis is correct, I can also make a merge request into drupal/activitypub module, which would have the same problem. If not, then I’ll need to go digging further.If I do need to wrap it an Announce, then I think I will need to do the following based on how it works on my end.
- Create my post as normal, but don’t address it to the community initially.
- Announce my own post making sure I address it to the community.
I guess that might show up as me boosting my own post on some instances (tooting my own horn? Horning my own toot?), which I would feel ashamed of.
-
If I do need to wrap it an Announce, then I think I will need to do the following based on how it works on my end.
- Create my post as normal, but don’t address it to the community initially.
- Announce my own post making sure I address it to the community.
I guess that might show up as me boosting my own post on some instances (tooting my own horn? Horning my own toot?), which I would feel ashamed of.
mradcliffe@nokoto.org no, Lemmy doesn't check the root for an Application actor (and as you discovered, NodeBB doesn't send one either, and we federate with Lemmy fine.)
Can you share a sample Create you're sending Lemmy? You should only need to have the group actor ID in
toorcc, and probablyas:Publicsomewhere in there too. -
If I do need to wrap it an Announce, then I think I will need to do the following based on how it works on my end.
- Create my post as normal, but don’t address it to the community initially.
- Announce my own post making sure I address it to the community.
I guess that might show up as me boosting my own post on some instances (tooting my own horn? Horning my own toot?), which I would feel ashamed of.
>Is that necessary? I could not find that in the Federation documentation.
The error message says that server expects an
Announceactivity. But yes, group's inbox should also accept replies wrapped inCreate, as well asLikes. -
>Is that necessary? I could not find that in the Federation documentation.
The error message says that server expects an
Announceactivity. But yes, group's inbox should also accept replies wrapped inCreate, as well asLikes.silverpill@mitra.social the group's inbox should, if the post is in local category, but what if it's a post in a remote category? It doesn't ever make it over to the remote server...
-
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemmy rejects my request with a 400 response with the error message above.
I tested other instances by making the following get request to the root of each instance (thank you, Daniel Sternberg for maintaining curl):
curl -v -H "Accept: application/activity+json" -H "Content-Type: application/activity+json" <url>- With the following results
- Lemmy returns an Application Actor.
- Misskey returns a 200 response in
text/html. - Mastodon returns a 406 response in
application/json. - NodeBB returns
text/html. - GoToSocial returns a 406 response in
application/json. - Mitra returns a 200 response in
text/html. - Pixelfed returns a 200 response in
text/html. - Peertube returns an empty 406 response.
My hypothesis is that Lemmy is rejecting the request because I return
text/plainand/or it cannot handle a response with that content type.To test that I am working on changing the default behavior. I will need to dynamically add a route based on
system.site.page.frontand return a 406 response in JSON. This is simple enough. If my hypothesis is correct, I can also make a merge request into drupal/activitypub module, which would have the same problem. If not, then I’ll need to go digging further.Hi, I had a look at the activities sent from your account. Looks like the only problem is that you are missing a
@contextfield. After adding that it parses just fine. What you serve from/is irrelevant, that one is completely optional. -
Hi, I had a look at the activities sent from your account. Looks like the only problem is that you are missing a
@contextfield. After adding that it parses just fine. What you serve from/is irrelevant, that one is completely optional.nutomic oh that's interesting, does Lemmy do JSON-LD validation? I didn't think it would.
-
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemmy rejects my request with a 400 response with the error message above.
I tested other instances by making the following get request to the root of each instance (thank you, Daniel Sternberg for maintaining curl):
curl -v -H "Accept: application/activity+json" -H "Content-Type: application/activity+json" <url>- With the following results
- Lemmy returns an Application Actor.
- Misskey returns a 200 response in
text/html. - Mastodon returns a 406 response in
application/json. - NodeBB returns
text/html. - GoToSocial returns a 406 response in
application/json. - Mitra returns a 200 response in
text/html. - Pixelfed returns a 200 response in
text/html. - Peertube returns an empty 406 response.
My hypothesis is that Lemmy is rejecting the request because I return
text/plainand/or it cannot handle a response with that content type.To test that I am working on changing the default behavior. I will need to dynamically add a route based on
system.site.page.frontand return a 406 response in JSON. This is simple enough. If my hypothesis is correct, I can also make a merge request into drupal/activitypub module, which would have the same problem. If not, then I’ll need to go digging further.Actually I was wrong, there is a context so thats fine. The problem is that
audienceshould be a simple string but you are sending an error, thats why it fails. Anyway that field is optional, so you can leave it out and put the community intoorccinstead.julian No but still the field is mandatory (mainly because that hasnt caused any problems so far).
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@mariusor@metalhead.club That's great context; thanks!
-
@silverpill@mitra.social That makes sense. I guess I was getting a little bit spun around by the idea that the keyId is not the Actor id and thinking too hard about it.
-
@jdt the fragment in a JSON-LD document IRI has a semantic meaning that goes back to RDF: https://www.w3.org/TR/rdf11-concepts/#section-fragID
> a secondary resource that is usually a part of, view of, defined in, or described in the primary resource, and the precise semantics depend on the set of representations that might result from a retrieval action on the primary resource.
-
@jdt You're supposed to fetch the keyId first, then fetch its owner (or controller).
But in practice its either /main-key (GoToSocial) or fragment ID, so it is indeed possible to save a HTTP request.
-
keyId is a problem.
Generally speaking, most Actors have a `keyId' that looks something like:
https://enigmatick.social/user/jdt#main-keyWhen an inbox POST arrives from an unknown user, we can chop off the bit including #main-key and we can pull the remaining URL as the Actor's ID.
But some implementations decided they should use /main-key instead. That indicates that the keyId format is unreliable and not well-specified. So I switched to deferring this header check for unknown Actors deeper into my ingestion pipeline so that I could retrieve the actor string from the object being sent. That works pretty well.
But GET requests. Like followers_synchronization. Dammit. There's no object to refer to. So we're back to parsing the keyId and hoping for meaning.
Out of 124,007 Actors in my database, 587 do not comply with the #main-key convention.
enigmatick=> select count(*) from actors where as_public_key->>'id' NOT LIKE '%#main-key'; count ------- 587 (1 row)For full coverage, I need to accommodate /main-key and #key as well
#ActivityPub
-
@reiver I'd consider interoperating social networks to be "federated", but I know it's not a precise term. There are similar ambiguities with other commonly used terms: decentralization, server, node, instance, and so on. We have our personal definitions but find that others have a different mental model than ours. It might be interesting to have a collaborative social web glossary that captures the variations of how these terms are used.
-
@rimu@mastodon.nzoss.nz Definitely. Offloading the static assets to nginx is a big win. Varnish adds a layer of serving from memory that takes it up a notch. Like having your own Fastly pop.
It does require some configuration nuance to be sure you aren't serving cached assets to the wrong connections (e.g., authenticated GET requests that shouldn't be shared beyond a specific session).
