| layout | keywords | comments | title | description | micro_nav | page_nav | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
default |
true |
Development Roadmap |
Our intention for the future development of this project |
true |
|
Seeking feedback.
API client Realtime model.
Further extensions.
Block Chain?
We have designed the API to have CRDT capable data types. For various reasons outside of a block chain we want our data to be immutable, non-revokable, timestamped, independently verifiable, trustless. These things combined suggest a surprisingly good case for a block chain in this case.
After the first round of feedback we have attempted to simplify our API to the bare essentials. There are, however, some features we would like to build back in when we can.
In the above, we only allow:
- Claims that can be represented in short text form.
In future iterations we'd like to extend this model to include:
- Mixed media posts, such as urban rumors
- Article length content
- Quotes from well known persons, in speeches or other venues (these can be handled, but could do with special handling)
We would also like to address the relationship between specific wordings of a claim and the existence (in some cases) of a storm of related tweets and representations of the 'same' rumor or idea.
As an agent.. I can submit a claim for review I can submit a claim with annotations in one post I can add annotations to an existing claim I can retrieve a claim in its simple form so i can annotate I can retrieve a claim with all its annotations and responses I can see a feed of most recent claims as submitted I can find claims where the claim text includes matching keywords I can find claims where the support includes matching keywords or URLs Claims are sorted by date submitted by default I can retrieve all claims I am notified when a new claim matching my query appears