@chocobozzz@framapiaf.org I have a question for you… I’m seeing in Are we HS2019 yet? that Peertube and Misskey both use your package: @peertube/http-signature
In the HTTP Signature Report we suggest a double-knock strategy for deploying RFC 9421. Basically, try RFC 9421 first, and if you get an error, downshift to draft-cavage-12 and try again.
Hey @panos@catodon.rocks, now that I’m tracking errors encountered, I’ve got a bit more visibility into things that normally would’ve just been caught and ignored.
Hi @peertube@framapiaf.org I am looking to debug some potential federation issues between NodeBB and Peertube and I am wondering if there is a test server I can federate against.
NodeBB federates out Note or Article depending on the length of the content. While this by-and-large works, the article logic does not encourage as much discussion as expected because a summary is generated so as to provide something for microblog-style software to show (otherwise, it would only show the title (name) and a URL to the forum.)
Hey @fentiger@zotum.net, I was debugging something @thisismissem sent me a couple days back, and in the process of doing so discovered that Zotum.net serves context with activities!
Hi @pfefferle@mastodon.social, I was trying to figure out something else (which I’ll ask in a separate topic), and then went down a rabbit-hole when I discovered I could no longer find @notiz.blog (:point_left: see, no link!)
I’ve seen hints of backfill working really well, but hadn’t seen good examples until recently. As more and more instances upgrade to the newer versions of Mastodon that support context, backfill from Mastodon instances will improve across the board.
Threaded applications often have the need to move and remove content between groups/communities for curation purposes (i.e. resolving miscategorization, spam, etc.)
This topic came up yesterday during the SocialCG meeting. I think it’s really interesting as a way to interact naturally with remote servers; see Cross-server Interactions in ActivityPub for a description of how it can work.
NodeBB has a very simple allow/deny list capability at present. You paste in a bunch of newline-separated domains, and we block (or optionally, only allow) them all.
P4 is a system-independent programming language for network devices like switches and routers. It lets developers define device behaviour like forwarding packets, quality of service, and traffic shaping. It’s event-based; it defines what the device should do as it receives packets on a network interface.
In Activity Streams 2.0, we can represent the result of an activity using the result property. Here, when the actor accepts a Follow activity, the result is that the follower is added to the actor’s followers collection.
Currently I am grappling with the specifics behind how to federate out the deletion of a topic in a category (or in ForumWG terms, the deletion of a context from an audience.)
nutomic@lemmy.ml reported a federation issue with a NodeBB instance and we debugged it. It turns out Lemmy is unable to handle actors who have image or icon set to null.
JollyPieFed
c/week-in-fediverse
Week in Fediverse :fediverse_light:
c/technical-discussion
evan
julian
c/general
c/canada
c/fedimemes
Emelia
c/fediverse