@reiver I see - the statement "It separates the user's content front the front-end related functionality" is confusing to me but I understand the intent now
darius@friend.camp
@darius@friend.camp
Posts
-
Remote Inbox Architecture -
Remote Inbox Architecture@reiver interesting. shouldn't the outbox be on (2)? In theory that is a place to get content and feeds from
-
So happy to see that #Mastodon has become a member of the W3C and is now coming to the renewed #ActivityPub standardization activity.@j12t @julian open to hearing about it of course.
Threadiverse as it currently exists is great for general discussion but for WG work items ("how's project A coming along?" and I only want responses from WG members) I'm not sure the tech is there for "closed group" style activity.
Mailing list might ultimately be the right choice. On a personal level, email is the worst part of my working day, but I'm trying not to let my prejudices block me here!
-
@evan @darius what about switching to YAML for #ActivityPub 2.0 -
Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.@julian @hongminhee @jenniferplusplus @feditest I'd love for any of these projects to use the data I've collected at the Observation btw
