Outbound Communication Channel Overload

We have a bit of a problem. Right now, we have a one-to-one relationship between project identities and our outbound communication channels.

Our existing top level project identities are:

* IPFS
* libp2p
* IPLD
* multiformats
* Filecoin

We also have new projects that may soon graduate to a top level identity like PeerPad and ProtoSchool.

There are good reasons that we keep these identities separate and I'm not suggesting that we stop keeping them separate. However, as we develop our outbound communication channels (Blogs, Twitter, YouTube, etc) it's prohibitively expensive to always be splitting our audience and subscriber base.

My recommended fix is to create "The Publication" (real name TBD) which is a new identity that we can use to encompass all of this ecosystem. We can use this for a Blog or Medium Publication, twitter account, YouTube channel, etc. This would allow us to build a unified subscriber base without sacrificing any project identities.

We could even consider using this to brand events that are broader in scope that our project specific events.

We'd continue to manage independent twitter accounts that would tweet about any new posts and other content relevant to that identity. Obviously, other project identity assets like websites would remain unchanged.

Thoughts?

What do people think this publication should be called?