-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for post subspaces and topics #46
Comments
I think having I'm thinking a use case that So the message itself should not be storing
|
@kwunyeung I think that due to your request being very application specific, it might suite better the new proposal I've just added: #52 |
I'm thinking about revisiting the structure of this implementation, deleting the type Post struct {
PostID PostID `json:"id"`
ParentID PostID `json:"parent_id"`
Message string `json:"message"`
Created int64 `json:"created"`
LastEdited int64 `json:"last_edited"`
Owner sdk.AccAddress `json:"owner"`
Subspace string `json:"subspace"`
// Arbitrary data as specified by #52
} I'm also thinking about making the |
Context
Ideally, what we want to achieve with Desmos is to enable any developer to create a messaging-based application that is completely decentralized and censorship resistant.
To do this, we need to find a way to distinguish the messages of an application from the ones of other applications built on Desmos.
Subspace implementation proposal
To solve this problem, we can implement the concept of subspace and topic.
A subspace will identify all the messages coming from the same application. For example, all messages coming from BigDipper will have
subspace = "bigdipper"
.A topic, on the other hand, allows applications to arbitrarily decide the topic of a specific post. For example, inside the
bigdipper
namespace we might want to haveproposal-discussion
,private-message
and other topics that let the clients easily fetch the messages related to a specific discussion subject.Storage implementation
The post object should be changed adding two new fields:
The following data should also be stored:
subspace
.topic
s associated to a specificsubspace
topic
.In this way we will be able to fetch in constant time the following data:
The text was updated successfully, but these errors were encountered: