I want to share a fediverse test resource I've started putting together over the last few days. It's a minimal config sandbox with automatically provisioned SSL and DNS for fedi services. A lot of apps refuse to federate with instances that don't have ssl or proper domain names, as a security measure. This makes that easy to run locally for testing.
@jenniferplusplus I need it for onepage.pub, the reference AP implementation for my book, so I'll let you know how it goes. I also just did a page in the ActivityPub primer about testing,
@jenniferplusplus@activitypubtestsuite thanks! I'll try to keep this in mind when/if I get to the federation part of my current project. Should prove to be very useful.
In a nutshell, we just return an array of delivery reports in addition to an http status. For sites that don't support delivery reports, we manufacture a report holding the http status, and if there are queue retrys, we collect the associated curl logs into a linked queue summary.
@activitypubtestsuite - question for the group: even if we were not to use it’s codebase, is there value in getting the old ActivityPub.rocks test suite live again? Just to see the old test in action?
> With any standard or specification, eventually the discussion turns to “how will we know if an implementation or application conforms to our standard or specification?”
Latest release candidate of @gotosocial finally adds federated #hashtags! This brings the number of missing "must-have" items on my wish list down to just one:
There are a few other things I'd like to have working before switching my primary Fediverse account from @KelsonV to a properly-set-up #GoToSocial#singleUserInstance, but that's the only big one left.
Follow moving accounts to their new location. (This is another big one.)
Mark account as moved
Polls
Fix Federation with Takahē (not sure how much is on which side at this point). I need to check in on what @activitypubtestsuite has been doing!
Federation with Lemmy (but that's on Lemmy to implement signed fetches)
I'm hoping we can get a suite that runs locally. I'm bad at installing software, so can help with the barrier-to-entry.
I've thought about test suite design, but that's mostly just identifying problems I don't know how to solve (e.g. how to test S2S when servers are more than just relays).
I can help with docs and testing. I'm playing with making a pedantic-to-the-point-of-uselessness literal implementation of the spec in Python, which might help if it goes anywhere.