{ "@context":[ "https://www.w3.org/ns/activitystreams", {"Hashtag":"as:Hashtag","sensitive":"as:sensitive"}, {"toot":"http://joinmastodon.org/ns#","focalPoint":"toot:focalPoint"} ], "published":"2025-10-26T00:52:16.508Z", "attributedTo":"https://epiktistes.com/actors/toddsundsted", "inReplyTo":"https://epiktistes.com/objects/O8GYi-K-2TM", "replies":"https://epiktistes.com/objects/pZDs8sjzByw/replies", "to":["https://www.w3.org/ns/activitystreams#Public","https://epiktistes.com/actors/toddsundsted"], "cc":["https://epiktistes.com/actors/toddsundsted/followers"], "content":"
Annoyingly, it seems like the ActivityPub Fuzzer wants to run over HTTPS, and there's no obvious way to persuade it to run on, for example, localhost, port 3000 with plain old HTTP. The supported use case seems to be fuzzer on public URL ↔︎ server on public URL, which is more trouble than it's worth, right now.
Annoyingly, it seems like the ActivityPub Fuzzer wants to run over HTTPS, and there's no obvious way to persuade it to run on, for example, localhost, port 3000 with plain old HTTP. The supported use case seems to be fuzzer on public URL ↔︎ server on public URL, which is more trouble than it's worth, right now.