Technical Discussion

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

Hey @bjoern @Karlitschek @nextcloud #activitypub #fedidev

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.

Moving contexts (aka topics/threads) between audiences (aka categories/communities) should be something that can be communicated outward.

Been thinking about [fediverse wiki] after @2chanhaeng@hackers.pub mentioned it today. Some ideas:

This is an extension of the discussion from Topic removal from a category/community.

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.

#activitypub #fediverse #fedidev

TIL: #Mastodon specifically treats actor URIs with the pattern https://<domain>/actor as instance actors.

If we were to do a regular online Fediverse meeting —

evan@cosocial.ca question for you — is there any guidance in the spec about whether id and url for a given AP object needs to be same-origin?