gnolang / dsocial Goto Github PK

This is a tracking issue to revert #25 when gnolang/gno#1509 is resolved.

Users will be able to set themselves a profile picture.

The fields of the "Import with Seed Phrase" screen should be cleared after use, so that they are clear when returning to the screen. See the short video demo:
https://www.loom.com/share/d97cefb88aac407cac521577361328ad

The Sign up screen creates an account on the phone and then calls onboarding to register with r/demo/users on the blockchain. But the account names in the keystore on the phone and the blockchain are linked. If the account name already exists in r/demo/users, then oboarding fails to register with r/demo/users. And the keystore on the phone may have an account with the same name but different addresses.

We need to keep the keystore in sync with r/demo/users when the user enters name N on the signup screen. The following table covers all cases and the action to take.

Request name N.

fixed #90

Currently, dSocial has one function where user A can repost the post of another user B, with a comment. In the other social apps, this behavior with a comment is called "quote", and there are separate buttons for "repost" and "quote". In the other apps, when you click "repost", it just does a repost without a comment. This difference is important for what happens when a third user C clicks the "react", "repost" and "quote" buttons while looking at the post in the feed of user A.

• If it came from "repost", then the "react", "repost" and "quote" buttons work as if user C was looking at the original post in the feed of user B.
• If it came from "quote" (with comment), then the "react", "repost" and "quote" buttons apply to the comment post of user A. (For example, a "gnod" reaction is added to the comment from user A, not the original post of user B.)

fixed in #86

When creating a new account, gnoboard checks if the account name already exists on the phone. We need to do something similar in the dSocial "Sign up" screen. But there is a difference. gnoboard allows to overwrite the existing account. We can't do this in dSocial because we are linked to r/demo/users on the blockchain and we can't overwrite a user on the blockchain. So I think the "Sign up" screen should not allow to re-use an existing account name.

Replace "tweet" and other terms with standard words dsocial/mobile/components/feed

As explained in gnolang/gnonative#133 , there will be a breaking change which affects how gnodev checks signatures. After merging that PR, we need to update gnonative in go.mod

We need to choose an approach for the general smart contract scalability testing that we plan to do as part of the Gno Social v1 project. This issue is created to reflect the work of identifying the right approach for the different types of testing to follow.

If I forget to type any text, and click Post, then dSocial posts a blank message. This is probably not what the user wants and there should be a confirmation message (or a message to require adding text). Should check for a blank text for Post and for Reply.

(Low priority but easy to implement.)

In the screenshot, test_qemu6 has reposted a post from jeff_galaxy20, adding the repost comment "I like this kind of cat". A UX question: should clicking the "gnod" add the gnod to the original post from jeff_galaxy20 or to the repost comment?

Current behavior: The gnod is added to the repost comment from test_qemu6. But the feed only displays the number of gnod on the original post from jeff_galaxy20. My suggestion: the gnod should be added to the original post. (I'm not sure exactly where in the code to check if clicking "gnod" is a repost. Maybe here?)

This is a benchmark tool that devs will be able to use for fixing performance issues related to various contracts stress tests around total number of messages, speed, users, memory usage.

ListJsonUsersByPrefix also matches the current username. It should be removed from the search results.

We have an issue in gnodev where reload doesn't replay initial "send coins" and "register user" correctly.

@gfanton created a fix which works: https://github.com/gfanton/gno/tree/fix/gnodev-block-commit . This is a tracking issue to wait for a PR to merge this into gnolang/gno.

Specify the versions for yarn, etc.