Varun Srinivasan
@v
We're thinking a lot about this idea. The two paths are - storing data offchain using meta tags and embedding and expanding them in posts or building them natively as a message type. Both have important tradeoffs that need to be explored. If anyone is interested in this topic, we're open to draft FIPs.
22 replies
12 recasts
305 reactions
Frederik Bolding 🦊
@frederik
Feels like this should be supported natively, but it opens up for the question of where to draw the line. I could definitely imagine other types of message types being requested in the near future for novel functionality.
1 reply
0 recast
0 reaction
Frederik Bolding 🦊
@frederik
It's an interesting protocol question, because at a certain point you need to decide how generic the protocol should be and how much should be left for clients to implement themselves. Letting clients handle too much causes interop problems and doing everything in the protocol causes bloat.
1 reply
0 recast
1 reaction
Frederik Bolding 🦊
@frederik
The protocol could be flexible, allowing for novel functionality while optimizing for highly-requested functionality once it reaches a certain threshold 🤔
0 reply
0 recast
0 reaction
