You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the era of current social networks, more and more applications are allowing users to add more than simple likes to posts. As an example, we've seen Facebook reactions:
Another one is the ability on Slack to react with emojis:
I think we should support this feature too as it make Desmos even more attractive to applications developers.
Post reaction implementation proposal
Currently we represent the like object using the following data structure:
typeLikestruct {
Created sdk.Int`json:"created"`// Block height at which the like was createdOwner sdk.AccAddress`json:"owner"`
}
I propose to expand and rename this structure to support other reaction types as follows:
typeReactionstruct {
Created sdk.Int`json:"created"`Owner sdk.AccAddress`json:"owner"`Valuestring`json:"value"`
}
The only change is the new Value field which allows application to insert any kind of text inside the reaction. This might be a simple like string, or even emojis.
Storage changes
No storage changes should be required.
The text was updated successfully, but these errors were encountered:
Context
In the era of current social networks, more and more applications are allowing users to add more than simple likes to posts. As an example, we've seen Facebook reactions:
Another one is the ability on Slack to react with emojis:
I think we should support this feature too as it make Desmos even more attractive to applications developers.
Post reaction implementation proposal
Currently we represent the like object using the following data structure:
I propose to expand and rename this structure to support other reaction types as follows:
The only change is the new
Value
field which allows application to insert any kind of text inside the reaction. This might be a simplelike
string, or even emojis.Storage changes
No storage changes should be required.
The text was updated successfully, but these errors were encountered: