I started to work on some cross protocol message payload restructuring for version 11.
What we currently do is sending a signed activitystreams message with two attachments (if both protocol addons are enabled). One is the signed activitypub payload (which is meanwhile basically a duplicate of the activitystreams payload without the two attachments) the other is the signed diaspora payload.
This made sense when we started to transition to zot6 some years ago. Now it just produces a lot of duplicated data on the wire.
What i plan to do, is to inline the diaspora protocol stuff into the actvitystreams/activitypub message so that no attachments are required anymore. This will reduce the payload size via zot6 transport and reduce some signing overhead but will slightly increase the payload via activitypub transport since they will then also receive the diaspora bits...
The next step will be to simplify caching of the received signed data payload to just store it once instead of once for every receiver on the hub. Possibly storing it to the filesystem instead of the DB to reduce DB size even more (similar to what streams did).
