# Wiki: Vision for a Fedi Specification

**URL:** <https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563>\
**Category:** Prosocial foundations\
**Tags:** wiki, social-web, vision\
**Created:** [November 14, 2024, 10:09am UTC](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563 "2024-11-14T10:09:40Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![benpate](https://discuss.coding.social/user_avatar/discuss.coding.social/benpate/32/894_2.png) [@benpate](https://discuss.coding.social/u/benpate)\
**Post date:** [November 18, 2024, 4:04pm UTC](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563/13 "2024-11-18T16:04:34Z")

</div>

I think the “recipe app” is a great example, specifically because it’s not “yet another microblogging Twitter clone” that seems to permeate the Fediverse.

If we are serious about interoperability, it means that people on my music sharing site should be able to collaborate at some level with people on your recipe app. Each app should participate in the global ecosystem, instead of making siloed, incompatible networks surrounding each applications (with FunkWhale’s as an example of this)

Obviously, every app can’t be everything to everyone (which is kinda how AP currently operates) so what are the commonalities? What is the “Lowest Common Denominator” of the Fediverse?

I’ll propose that it’s: 1) identity, and 2) notifications. My username should be the master key that opens every door on the Fediverse, and allows me to subscribe to events in a myriad of other services. In this model, my Mastodon account doesn’t need to know how music (or recipes) are handled on remote servers, but I can get access to them, and seamlessly connect to those other specialized services when I want to.

---

_[View the full topic](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563)._