@thisismissemEmelia @cheeaunChee Aun ๐Ÿค”

Yes, I agree.

I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.

Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...

Who dares to ?

@smallcircles@social.coop I think something that is going to be really interesting to explore is that with ActivityPub C2S, it may make sense for there to be aggregator services, which fulfil a role much like "relays" in AT Protocol โ€” essentially a big fat pipe for applications to aggregate data from all their accounts from many individual data servers.

There may even be a need to have a way to have an application when writing an activity to the data server, to be able to say "also deliver this to the relay as a bcc/bto" (a relay could just be an inbox/outbox setup).

0

If you have a fediverse account, you can quote this note from your own instance. Search https://activitypub.space/post/1256 on your instance and quote it. (Note that quoting is not supported in Mastodon.)