Abstract ctzn protocol + networking from actual implementation of twitter-style app

[xing-e-recruiting-code-challenges]

Hi Paul,

I've been silently watching your progress with ctzn with great interest. I think the basic ideas as a core schema for social networks is very sound but I'm wondering whether at this point it makes sense to separate the "protocol" layer from the actual particular social network implementation layer? i.e. separating the"data-mesh" from the "application" layer?

I'm asking this because I can see how the basic underlying protocol and network design could be used to implement more than just as in this case a twitter style social network.

e.g. I'm interested in creating a p2p network of indexed content/links ( a sort of p2p pocket/wikipedia thingy) and reusing the ctzn data mesh protocol for that would definitely make sense to me but as is I'm seeing tight coupling between the data-mesh layer and the app layer?

[pfrazee]

This is one of our goals! We're currently focusing on getting the core schemas and behaviors into a good state, but there's very little reason why new schemas shouldn't be addable. Worst case, you just need to fork the ctzn server to add new behaviors. Best case, we get a system in-place where the indexing logic of custom schemas can be set by users/new-schemas.

[xing-e-recruiting-code-challenges]

Awesome news Paul. I'd like to help out! I'll take a look at the rest of the issues and see where I can pitch in.

[saimonmoore]

Oops 😅 I forgot to logout and used a company account :(