Embed Notice

@evan Thank you for your comments!

>End-to-end encryption. It's time to get on this; I don't think building on top of an incompatible stack is the way to go, though

I'm interested in MLS because it promises private group messaging. Your proposal is much simpler, and doesn't require any fancy cryptography, but since we have a blank slate (no legacy implementations), I think MLS is worth considering. That being said, I don't understand how it works yet, and it is possible that MLS will be too complicated for our purposes.

>Quote Announce. This comes down to recommending `content` in the `Announce` activity.

Yes, this representation is possible too, but non-supporting servers will process it as a boost, and I think it can't be used in replies. Today almost all projects that support "quote" feature use quoteUrl (and some adopted FEP-e232) because links doesn't have these downsides.

By the way, here is an excellent comparison of various approaches: https://socialhub.activitypub.rocks/t/disambiguating-various-interpretations-of-a-quote-feature-pre-fep/3426

>In general, I think you've got a lot of good ideas here. The ActivityPub fork idea is terrible, though.

No, I'm not advocating for a fork. If you are talking about https://github.com/steve-bate/activitypub-mincore - I see it as a profile, and I think it could be useful for new implementers who may not know where to start, or frustrated when their implementation doesn't federate with Mastodon.