Content pfp
Content
@
https://warpcast.com/~/channel/jump
0 reply
0 recast
0 reaction

Kairon pfp
Kairon
@k41r0n
I remember having JUMP community calls explaining what Mirror is Some of my best appearances have centered around onchain publishing Today, I'm so glad to finally see onchain publishing coming together as a united front https://dev.mirror.xyz/_JH3B2prRmU23wmzFMncy9UOmYT7mHj5wdiQVUolT3o
3 replies
0 recast
8 reactions

Kauffman 🪂 pfp
Kauffman 🪂
@kauffman
Tipping my full daily allowance 😂 8 $degen Curious about your thoughts on how these two protocols work and/or interact with each other. Trying to think about what their swim lanes will be and how they compliment each other.
1 reply
0 recast
1 reaction

Kairon pfp
Kairon
@k41r0n
So far, my thinking was: Paragraph focuses on emulating the current writing UX and distribution Mirror focuses on net-new onchain publishing experiences Both are needed for different reasons I hope this continues down the line, but not sure about what it'll mean in the future
1 reply
0 recast
0 reaction

Kauffman 🪂 pfp
Kauffman 🪂
@kauffman
That makes perfect sense. Would you say/agree they can have a sort of front end / back end type of relationship? Where Paragraph is more of the app and Mirror is a publishing protocol?
1 reply
0 recast
1 reaction

Kairon pfp
Kairon
@k41r0n
I would 100% agree with this, especially cause paragraph is already strongly inspired by the protocol mirror created That'd be the ideal scenario, I was actually thinking about this situation specifically when I wrote graveyard of protocols, and I'm glad to see it's playing out in a way that preserves onchain content
0 reply
0 recast
1 reaction