I've found a few perf issues in @pixelfed accounts with 1k+ followers
Fanout and audience delivery are two tricky aspects that require more work, I'm working on this, and exploring ways to make pixelfed <-> pixelfed federation even more efficient!
I've found a few perf issues in @pixelfed accounts with 1k+ followers
Fanout and audience delivery are two tricky aspects that require more work, I'm working on this, and exploring ways to make pixelfed <-> pixelfed federation even more efficient!
@dansup shared inboxes were in the activity pub spec drafts for almost a full year before mastodon implemented activity pub.
@jenniferplusplus No they weren't, even Gargron admits that. It was him/Mastodon that contributed them to the spec, I'm sure you can ask @cwebber to verify.
I just want to mention that Mastodon has set the gold standard for this.
We take a lot for granted, like the MastoAPI, Webfinger, and sharedInbox.
These are not defined in the ActivityPub spec, these were contributed by Mastodon/Gargron.
The sharedInbox extension enables instances these large, which is a good thing, most people don't want to install Mastodon to have to use it.
@dansup Shared inbox is actually defined by the activitypub spec.
@jenniferplusplus Now it is, because of Mastodon.
@bitflipped I never meant that Mastodon created webfinger, I meant that they added a common implementation that we (activitypub implementations) use for addressing. Did AP define webfinger addressing?
@dansup while I do like Mastodon and what it has done for social media, Webfinger was created by the IETF
bartle is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All bartle content and data are available under the Creative Commons Attribution 3.0 license.