Skip to content

Latest commit

 

History

History
59 lines (40 loc) · 2.35 KB

CHANGELOG.md

File metadata and controls

59 lines (40 loc) · 2.35 KB
Raw

Changelog

M3

SEO optimizations

It’s essential for any spaceging platform or a social network to be indexed by the search engines so other people could find your spaces or posts through a web search.

  • Integration with Next.js for server-side rendering of read-only parts: view space, post, comment, and public user’s profile.
  • Server-side rendering of a space.
  • Server-side rendering of a post.
  • Server-side rendering of every comment.
  • Server-side rendering of a user profile. (Profiles should be optional)

Full-text search

Currently, it’s hard to build a full-text search service in a decentralized way because we don’t have a proper incentivization model for technology that is not built on blockchain (as a full-text search is). That's why we will implement it as a centralized service built on the open-source technology: ElasticSearch.

  • Full-text search for spaces.
  • Full-text search for posts.

M2

Rating and reputation

  • Update a comment rating after the comment upvoted/downvoted.
  • Update a post rating after it has been upvoted/downvoted.
  • Update a space rating after its post has been upvoted/downvoted.
  • Update an account/member reputation after their post/comment upvoted/downvoted.

Activity stream

  • Follow an account.
  • List spaces you follow.
  • List accounts you follow.
  • List account followers.
  • Render an activity stream based on the spaces you follow.
  • Render an activity stream based on the accounts you follow.
  • Share a post with your followers (the post will be included in their activity stream).

M1

IPFS integration

Currently we store all text content onchain. And in this milestone we want to refactor Subsocial module to store text content of spaces, posts and comments on IPFS.

  • Store spaces on IPFS (name, description, cover image, etc.).
  • Store posts on IPFS (title, body, summary, tags, cover image, publishing date, etc.)
  • Store comments on IPFS.
  • Store public member profiles on IPFS (username, avatar, about, links to other social networks).

Edit history

Store an edit history on IPFS + list of CIDs in Substrate storage in a corresponding struct: space, post, comment or profile.

  • Save and view an edit history of a post.
  • Save and view an edit history of a space.
  • Save and view an edit history of a comment.
  • Save and view an edit history of a member profile.