@fredy testyy

@mro the https signature issue is getting on my nerves. i'm currently working on the logic for receiving the inbox. Then I can somehow verify my own signature. I just have to think of an external fake recipient so that I can send to myself.
But that doesn't make that much sense in the end, if I misunderstand the signature stuff, then I'll verify wrong too!
And as key id I will then transfer the actor URL extended by ‘#throwMeAway’

@mro ah, I forgot that it says above ‘If it has a fragment, discard it.’
It is assumed that the keyId has a fragment to be ignored. If the keyId is used without a fragment, it is assumed that it points to an actor object. Or as in 5. to a raw key.
So to get the rdf PublicKey object, the fragment of the keyId must be discarded, then the Actor object must be loaded to get the PublicKey object.
Sorry, but I would never interpret keyId like that

@mro aha, that is not how i understand: https://swicg.github.io/activitypub-http-signature/#how-to-obtain-a-signature-s-public-key

@mro hAhAhA.....

Maybe i understand now ?!

While reading https://swicg.github.io/activitypub-http-signature/#how-to-obtain-a-signature-s-public-key

5. If it's a raw Key object, use its controller or owner property as the new key id, jump back to step 2, and repeat. (This is necessary to confirm that the owner actually owns and uses this key.)

So the keyId of the signature is not a key id, it's the key?!

this is more than confusing, the ‘keyId’ can be an InstanceActor, an Actor or the Key but not the Id of the Key ????

#activitypub #activitypubdev

@crepels
- clear cookies
- restart firefox
- wait 10 Seconds
- load https://activitypub.academy/
- wait more than 10 second (while writing that)
- sign in -> YYEEEAAAAHhhhhh it works

So it was some caching problem of firefox, whatever?!

Thanks.

Hallo deutschsprachige #activitypub Entwicklungsfreunde. Wer hätte interesse an einem Online-Stammtisch?

@sl007
what you remember
Unbelievable how long I've been motivated to work on #rdfpub. I never had motivation for more than 1 - 2 weeks for my own projects before and certainly not open source.
so #activitypub and #rdfpub must be/become something very special.
It's about time for a German-language online event.
@FabianPfeffer and others are interested. I have time, I just don't know how it is with the connection from Spain. The remote desktop of my dev server is extremely slow.

Ok, now with nodeinfo:
curl https://dev.rdf-pub.org/.well-known/nodeinfo
curl https://dev.rdf-pub.org/nodeinfo/2.1
#rdfpub #activitypub #activitypubdev

I am flooded with
/api/v1/instance requests.
Do you expect a nodeinfo response?

Ok, I did some research: https://github.com/jhass/nodeinfo/blob/main/PROTOCOL.md
So the
Nodeinfo path would be: /.well-known/nodeinfo
why does ‘presumably’ mastodon get the idea that I offer this endpoint?

#activitypub #activitypubdev

@crepels No, it's not working with my standard firefox. I have now found out that it works in a private window. I have deleted the cookies in the non-private window. But it still doesn't work.

Can I see these 2 errors somewhere? I can't find them

ggggrrrrrrrrrr
Because i changed the propertyName yesterday.
See:
https://mastodon.social/@naturzukunft/113419656230832832

#activitypub #activitypubdev

Security - Mastodon documentation

Public key cryptography and supported signature schemes over HTTP and JSON-LD.

(docs.joinmastodon.org)

->

"The keyId should correspond to the actor"

What? What does that mean?

#activitypub #activitypubdev

another step forward (or just somewhere else)

"error":"publicKey id for https://dev.rdf-pub.org/resource/acto40aaf20a-d9d8-41ef-bdf5-13112c7c38af does not correspond to https://dev.rdf-pub.org/resource/acto40aaf20a-d9d8-41ef-bdf5-13112c7c38af/resc522a91b-e7fd-44b6-879f-ded2edf1bbbb"}

what does mastodon want? does the url for the publicKey have to have a fragment?

#activitypub #activitypubdev

I tidied up a bit after I realised that browserPub didn't like reading my Actor either.
So the problem seems to have been an unsupported Accept header. I now map to json-ld by default, so if I can't map the Accept header to an RDF format, I get json-ld

another step forward (or just somewhere else)

"error":"publicKey id for https://dev.rdf-pub.org/resource/acto40aaf20a-d9d8-41ef-bdf5-13112c7c38af does not correspond to https://dev.rdf-pub.org/resource/acto40aaf20a-d9d8-41ef-bdf5-13112c7c38af/resc522a91b-e7fd-44b6-879f-ded2edf1bbbb"}

what does mastodon want? does the url for the publicKey have to have a fragment?

#activitypub #activitypubdev

does anyone have any idea how i can find out what exactly mastodon doesn't like ?

#activitypub #activitypubdev

{
"id" : "https://dev.rdf-pub.org/resource/acto4/resc5",
"type" : [ "Object", "prov:Entity" ],
"owl:sameAs" : {
"id" : "..."
},
"prov:wasAttributedTo" : {
"id" : "..."
},
"prov:wasGeneratedBy" : {
"id" : "..."
},
"owner" : "https://dev.rdf-pub.org/resource/acto4",
"publicKeyPem" : "***",
"name" : "public key of https://dev.rdf-pub.org/resource/acto4",
"@context" : [ "https://schema.org/...", "https://rdf-pub.org/...", "https://w3id...1", "https..." ]
}

#activitypub #activitypubdev

Mastodon probably doesn't like my key

"error":"Unable to fetch key JSON at https://dev.rdf-pub.org/resource/acto40aaf20a-d9d8-41ef-bdf5-13112c7c38af/resc522a91b-e7fd-44b6-879f-ded2edf1bbbb"

before the error the key is requested and i answer as follows

#activitypub #activitypubdev

uuupppss,
currently debugging "try&error" sending a note to #mastodon

Now i got the message:

"Fetching attempt skipped because of recent connection failure"

I assume that mastodon no longer requests the publicKey. Because errors have occurred several times.
Does anyone know this? Is this something temporary? How long does Mastodon want peace and quiet?

#activitypub #activitypubdev