home.social

#activitypubdev — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #activitypubdev, aggregated by home.social.

fetched live
  1. Slowly developing the in depth testing of the same functionality at different levels in the #GoActivityPub stack.

    I have just finished the collection pagination integration test as exposed in the reference server implementation for the library. So we now have the same pagination functionality covered in unit-tests in the different storage backends, also covered by the storage conformance suite, and now, through an integration test in the server application itself.

    #ActivityPub #ActivitypubDev #fedidev

  2. Slowly developing the in depth testing of the same functionality at different levels in the #GoActivityPub stack.

    I have just finished the collection pagination integration test as exposed in the reference server implementation for the library. So we now have the same pagination functionality covered in unit-tests in the different storage backends, also covered by the storage conformance suite, and now, through an integration test in the server application itself.

    #ActivityPub #ActivitypubDev #fedidev

  3. Slowly developing the in depth testing of the same functionality at different levels in the #GoActivityPub stack.

    I have just finished the collection pagination integration test as exposed in the reference server implementation for the library. So we now have the same pagination functionality covered in unit-tests in the different storage backends, also covered by the storage conformance suite, and now, through an integration test in the server application itself.

    #ActivityPub #ActivitypubDev #fedidev

  4. Slowly developing the in depth testing of the same functionality at different levels in the #GoActivityPub stack.

    I have just finished the collection pagination integration test as exposed in the reference server implementation for the library. So we now have the same pagination functionality covered in unit-tests in the different storage backends, also covered by the storage conformance suite, and now, through an integration test in the server application itself.

    #ActivityPub #ActivitypubDev #fedidev

  5. Slowly developing the in depth testing of the same functionality at different levels in the #GoActivityPub stack.

    I have just finished the collection pagination integration test as exposed in the reference server implementation for the library. So we now have the same pagination functionality covered in unit-tests in the different storage backends, also covered by the storage conformance suite, and now, through an integration test in the server application itself.

    #ActivityPub #ActivitypubDev #fedidev

  6. When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API.

    But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:

    #ActivityPubDev #fedidev

  7. When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API.

    But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:

    #ActivityPubDev #fedidev

  8. When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API.

    But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:

    #ActivityPubDev #fedidev

  9. When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API.

    But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:

    #ActivityPubDev #fedidev

  10. When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API.

    But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:

    #ActivityPubDev #fedidev

  11. I'm surprised at how many issues my new integration tests are finding.

    I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install.

    We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations.

    #fedidev #activityPubDev #activitypub

  12. I'm surprised at how many issues my new integration tests are finding.

    I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install.

    We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations.

    #fedidev #activityPubDev #activitypub

  13. I'm surprised at how many issues my new integration tests are finding.

    I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install.

    We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations.

    #fedidev #activityPubDev #activitypub

  14. I'm surprised at how many issues my new integration tests are finding.

    I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install.

    We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations.

    #fedidev #activityPubDev #activitypub

  15. I'm surprised at how many issues my new integration tests are finding.

    I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install.

    We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations.

    #fedidev #activityPubDev #activitypub

  16. Oof, the painful long road of fixing concurrency bugs that lie deep into your stack...

    #ActivityPub #ActivityPubDev

  17. Oof, the painful long road of fixing concurrency bugs that lie deep into your stack...

    #ActivityPub #ActivityPubDev

  18. Oof, the painful long road of fixing concurrency bugs that lie deep into your stack...

    #ActivityPub #ActivityPubDev

  19. Oof, the painful long road of fixing concurrency bugs that lie deep into your stack...

    #ActivityPub #ActivityPubDev

  20. Oof, the painful long road of fixing concurrency bugs that lie deep into your stack...

    #ActivityPub #ActivityPubDev

  21. Does anyone know of a #WordPress hosting company with a free plan that includes the ActivityPub plugin?

    I just gave it a try with my FedIAM single sign-on project, and it seems very close to "just working", but it doesn't like my test network very much, so I'd like to give it a try on the live network.

    #WordPress #ActivityPubDev #FediDev #FedIAM
  22. Does anyone know of a #WordPress hosting company with a free plan that includes the ActivityPub plugin?

    I just gave it a try with my FedIAM single sign-on project, and it seems very close to "just working", but it doesn't like my test network very much, so I'd like to give it a try on the live network.

    #WordPress #ActivityPubDev #FediDev #FedIAM
  23. Does anyone know of a #WordPress hosting company with a free plan that includes the ActivityPub plugin?

    I just gave it a try with my FedIAM single sign-on project, and it seems very close to "just working", but it doesn't like my test network very much, so I'd like to give it a try on the live network.

    #WordPress #ActivityPubDev #FediDev #FedIAM
  24. Does anyone know of a #WordPress hosting company with a free plan that includes the ActivityPub plugin?

    I just gave it a try with my FedIAM single sign-on project, and it seems very close to "just working", but it doesn't like my test network very much, so I'd like to give it a try on the live network.

    #WordPress #ActivityPubDev #FediDev #FedIAM
  25. Question about HTTP Signatures in #ActivityPub, IIUC the header is a digest of the HTTP body. Given that JSON is not white-space sensitive, does that mean that storing the response must preserve the indentation used by the server?

    #ActivityPubDev

  26. Question about HTTP Signatures in #ActivityPub, IIUC the header is a digest of the HTTP body. Given that JSON is not white-space sensitive, does that mean that storing the response must preserve the indentation used by the server?

    #ActivityPubDev

  27. Question about HTTP Signatures in #ActivityPub, IIUC the header is a digest of the HTTP body. Given that JSON is not white-space sensitive, does that mean that storing the response must preserve the indentation used by the server?

    #ActivityPubDev

  28. Question about HTTP Signatures in #ActivityPub, IIUC the header is a digest of the HTTP body. Given that JSON is not white-space sensitive, does that mean that storing the response must preserve the indentation used by the server?

    #ActivityPubDev

  29. > Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
    > (Brian Kernighan)

    Bit hard by this today.

    The Rube Goldberg-esque machine of generating HTTP-Signatures and verifying them has become too much for my brain to handle.

    Too many elements to keep track of and I'm currently having steam coming out of my ears.

    I'll sleep on it...

    #activitypub #activitypubdev

  30. > Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
    > (Brian Kernighan)

    Bit hard by this today.

    The Rube Goldberg-esque machine of generating HTTP-Signatures and verifying them has become too much for my brain to handle.

    Too many elements to keep track of and I'm currently having steam coming out of my ears.

    I'll sleep on it...

    #activitypub #activitypubdev

  31. > Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
    > (Brian Kernighan)

    Bit hard by this today.

    The Rube Goldberg-esque machine of generating HTTP-Signatures and verifying them has become too much for my brain to handle.

    Too many elements to keep track of and I'm currently having steam coming out of my ears.

    I'll sleep on it...

    #activitypub #activitypubdev

  32. > Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
    > (Brian Kernighan)

    Bit hard by this today.

    The Rube Goldberg-esque machine of generating HTTP-Signatures and verifying them has become too much for my brain to handle.

    Too many elements to keep track of and I'm currently having steam coming out of my ears.

    I'll sleep on it...

    #activitypub #activitypubdev

  33. > Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
    > (Brian Kernighan)

    Bit hard by this today.

    The Rube Goldberg-esque machine of generating HTTP-Signatures and verifying them has become too much for my brain to handle.

    Too many elements to keep track of and I'm currently having steam coming out of my ears.

    I'll sleep on it...

    #activitypub #activitypubdev

  34. I started a private thread between my account and a test actor. The root post was delivered to me (as an Add/Create/Note) and all the objects in the message have:

    {
      "context": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "contextHistory": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "to": [
        "https://zotum.net/lists/17bb4e2e-3149-4803-ad61-b8b8357af703"
      ],
      ...
    }

    But I can't dereference either of these URLs, or any of the object IDs, not even with a signed request. In particular, I can't dereference the to URL, which means my test actor can't reply to the thread. :(

    Should I expect to be able to fetch these? I would have thought a signed GET would work, but it seems not.

    Is it worth trying to set up a local Hubzilla instance to test against? I can do this, but I thought asking first might be a lot easier.

    #ActivityPubDev #FediDev
  35. I started a private thread between my account and a test actor. The root post was delivered to me (as an Add/Create/Note) and all the objects in the message have:

    {
      "context": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "contextHistory": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "to": [
        "https://zotum.net/lists/17bb4e2e-3149-4803-ad61-b8b8357af703"
      ],
      ...
    }

    But I can't dereference either of these URLs, or any of the object IDs, not even with a signed request. In particular, I can't dereference the to URL, which means my test actor can't reply to the thread. :(

    Should I expect to be able to fetch these? I would have thought a signed GET would work, but it seems not.

    Is it worth trying to set up a local Hubzilla instance to test against? I can do this, but I thought asking first might be a lot easier.

    #ActivityPubDev #FediDev
  36. I started a private thread between my account and a test actor. The root post was delivered to me (as an Add/Create/Note) and all the objects in the message have:

    {
      "context": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "contextHistory": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "to": [
        "https://zotum.net/lists/17bb4e2e-3149-4803-ad61-b8b8357af703"
      ],
      ...
    }

    But I can't dereference either of these URLs, or any of the object IDs, not even with a signed request. In particular, I can't dereference the to URL, which means my test actor can't reply to the thread. :(

    Should I expect to be able to fetch these? I would have thought a signed GET would work, but it seems not.

    Is it worth trying to set up a local Hubzilla instance to test against? I can do this, but I thought asking first might be a lot easier.

    #ActivityPubDev #FediDev
  37. I started a private thread between my account and a test actor. The root post was delivered to me (as an Add/Create/Note) and all the objects in the message have:

    {
      "context": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "contextHistory": "https://zotum.net/conversation/2ffbd4e4-6197-4922-98ec-bedd4108679d",
      "to": [
        "https://zotum.net/lists/17bb4e2e-3149-4803-ad61-b8b8357af703"
      ],
      ...
    }

    But I can't dereference either of these URLs, or any of the object IDs, not even with a signed request. In particular, I can't dereference the to URL, which means my test actor can't reply to the thread. :(

    Should I expect to be able to fetch these? I would have thought a signed GET would work, but it seems not.

    Is it worth trying to set up a local Hubzilla instance to test against? I can do this, but I thought asking first might be a lot easier.

    #ActivityPubDev #FediDev
  38. So on my ONI instance that I've been use as an alternative fediverse profile for myself for about two years, the full storage used is about 3.4G, but out of that there's 2.5G containing mostly the Delete activities of mastodon.social. Crazy.

    #mastodev #fediverse #ActivityPubDev #ActivityPub

  39. So on my ONI instance that I've been use as an alternative fediverse profile for myself for about two years, the full storage used is about 3.4G, but out of that there's 2.5G containing mostly the Delete activities of mastodon.social. Crazy.

    #mastodev #fediverse #ActivityPubDev #ActivityPub

  40. So on my ONI instance that I've been use as an alternative fediverse profile for myself for about two years, the full storage used is about 3.4G, but out of that there's 2.5G containing mostly the Delete activities of mastodon.social. Crazy.

    #mastodev #fediverse #ActivityPubDev #ActivityPub

  41. So on my ONI instance that I've been use as an alternative fediverse profile for myself for about two years, the full storage used is about 3.4G, but out of that there's 2.5G containing mostly the Delete activities of mastodon.social. Crazy.

    #mastodev #fediverse #ActivityPubDev #ActivityPub

  42. So on my ONI instance that I've been use as an alternative fediverse profile for myself for about two years, the full storage used is about 3.4G, but out of that there's 2.5G containing mostly the Delete activities of mastodon.social. Crazy.

    #mastodev #fediverse #ActivityPubDev #ActivityPub

  43. I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

    Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

    This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

    Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

    #ActivityPubDev #fedidev #httpsig

  44. I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

    Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

    This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

    Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

    #ActivityPubDev #fedidev #httpsig

  45. I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

    Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

    This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

    Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

    #ActivityPubDev #fedidev #httpsig

  46. I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

    Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

    This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

    Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

    #ActivityPubDev #fedidev #httpsig

  47. I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

    Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

    This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

    Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

    #ActivityPubDev #fedidev #httpsig

  48. Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

    According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

    #fediverse #activityPub #activityPubDev

  49. Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

    According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

    #fediverse #activityPub #activityPubDev

  50. Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

    According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

    #fediverse #activityPub #activityPubDev

  51. Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

    According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

    #fediverse #activityPub #activityPubDev

  52. Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

    According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

    #fediverse #activityPub #activityPubDev

  53. @julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

  54. @julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

  55. @julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

  56. @julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

  57. @julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

  58. If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

    Now downloading google.com...

    #ActivityPub #ActivityPubDev

  59. If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

    Now downloading google.com...

    #ActivityPub #ActivityPubDev

  60. If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

    Now downloading google.com...

    #ActivityPub #ActivityPubDev