capsulesocial / capsule-vue Goto Github PK

Posted comments are being displayed in reverse order as they should be. Show most recent comments at top.

Start date: 21.09.21
Estimated end date: 21.09.21

When logging out, I'm getting this error:

Error: Key 'blogchain-auth-admin' does not exist. Key not found in database [/info/blogchain-auth-admin]
    at Keychain.findKeyByName (index.js?91cd:287)
    at async Keychain.removeKey (index.js?91cd:303)

Source: components/Header.vue logout method

const node = this.$getNode()
// Remove a user's key from keychain when they logout
await node.key.rm(`blogchain-auth-${this.$store.state.session.id}`)
this.endSession()

This may be caused by using the admin bypass when logging in. This issue may become irrelevant with the NEAR branch merge

When you remove a bookmark, that bookmark is still appearing on the bookmarks list on your profile but with bookmarked: false.

In the posts feed, these are the calls being made to the backend:

[1] GET: /content/tags
[1] GET: /content?sort=NEW&offset=0&limit=10&bookmarker=tom
[1] GET: /repost?authorID=tom&sort=NEW
[1] GET: /bookmark/tom/bafyreidb7agoj5f4cii32sbuoyddkc7cpqrt2iyjg6i5po5wam5keoiesy
[1] GET: /bookmark/tom/bafyreiamg4zuxujullh42bptlnfl2ksqohcxls4ozfcu3rntdnnrft3bvq
[1] GET: /bookmark/tom/bafyreibz335w2owf55in5y5ne67q4mhmxdodvf2q6yki5s4mlejfpl2rrq
[1] GET: /bookmark/tom/bafyreia2tgkkk4lg5bfabodgza2zxwi3mggzlbzb2pauyusbeq3dpsfmne
[1] GET: /bookmark/tom/bafyreidhabogixo7e7z4tupc7ikiwnevabwmwyuppo3txxvazlnt6dbx5a
[1] GET: /bookmark/tom/bafyreif6bcollvovwxkjqz2l2ikcs4hyyj3toz7f2e67htetldvkhw5cm4
[1] GET: /bookmark/tom/bafyreieun42zrm332kjo7s5ldz5eu6iuwokyxi64wri4dfizmlzhjhdtzy
[1] GET: /bookmark/tom/bafyreicos6mnd7kl5dxy3phmpzxf7hhr77dc6nti4bh6iypxlubr6a3z2y
[1] GET: /bookmark/tom/bafyreig7zhcdr2p5tceulzzi4da3rdt6z23d7bdyyvu2exadsrwridfkre
[1] GET: /bookmark/tom/bafyreig676dzyksqmssk4moj2hc5syg4uac6zbhcm4jdt2svjc2rjtbypy

Calls to /bookmark/tom/<CID> in the posts feed are not required. When you fetch posts (/content?sort=NEW&offset=0&limit=10&bookmarker=tom), it contains a bookmarked flag (See example response: https://github.com/capsulesocial/capsule-orbit/blob/main/docs/content.md#response-1) which indicates whether or not a the post has been bookmarked by the logged-in user (aka bookmarker in the query parameter).

Well it's self describable :)

1. We should decide on an upper tag character limit
2. We should also amend the UI so that it doesn't break up to that upper character limit.

The buttons below should be removed if the user who wrote the post is the logged in user.

I tried entering a random long word and it seems it is going out of the containing element as you can see in the screenshot above.

When a new post is created, the tags persist in the editor for the next post too.

Currently lists aren't properly formatted with indentation and bulleting format.

https://yabwe.github.io/medium-editor/

estimated start date: 24.09.2021

On a profile page, display a list of profiles who are following or follow a user.

Followers mock-up: https://app.zeplin.io/project/603e81e66a60d1a5df091ddb/screen/614432c86d0ba321d93b5a7d

Following mock-up: https://app.zeplin.io/project/603e81e66a60d1a5df091ddb/screen/61443340fcb613264addec3a

There was some spacing between Posts title bar and first Post card earlier, which is now gone.

Steps to reproduce this behavior:

1. Select an image for a new post
2. Click on Replace Image
3. Close the image selector window instead of selecting a new image.

There is an issue with the the new default avatar pictures, they are not in the img folder, (where for example the category pictures are) and as a result they are broken on the test-node.

Move repost button from share dropdown to main card

Expected start date: 21.09.2021
Expected Completion date: 22.09.2021

It would be great to give the ability to the user to choose his own capsule-orbit node. We can do that by adding an "advanced" settings tab, where there will be a text field that can be filled with your preferred node URL. That URL will be stored in the $store, where it will be picked up by the "backend" on load.

• Changing the preferred node URL should trigger a refresh of the page
• We should make sure that the node URL is a valid URL.
• If the $store variable is empty, the backend will automatically use the test-node url

Pagination for getCommentsOfUser is already implemented on capsule-orbit. The implementation is exactly the same to the feed pagination.

Given this is ready: https://github.com/capsulesocial/capsule-orbit/pull/44 I can start implementing that in the frontend.

@jackdishman I will provide a getCommentsOfUser(authorID: string) method for you.

• Implement getCommentsOfUser (Today)
• Comments of User UI/UX

We store profile data in the app's store. In some places we retrieve the profile from the store and in others we retrieve the profile through IPFS.

So when the profile is updated from another instance of the app, there are some places that have the profile kept the same as before and others that the profile is updated.

Possible Solution:

Whenever a profile is needed, retrieve it from the store but also, make an async call to ipfs and update it if there is a change.

I can access this post by navigating to it from the news feed, but not when I click the direct link:
https://test-node.capsule.social/post/Qmd4DTjpsf3iyMuQQzMZw7ffCt1tRriwmf1XJHqVJB6Zfj

Implement the bookmarks feature on the frontend. The action on a Post must be implemented and also fetching bookmarks of a user to display on a profile page

Estimated start date: Oct 18
Estimated completion date: Oct 22

Steps to reproduce:

1. Create a new post (as an example copy paste this blog)
2. Select Heading and insert a link. Here, It selects whole post content for the link

Duplicate posts are shown when you visit someone's profile. This goes away on page-refresh.

To replicate, you can simply try to visit someone's profile from your feed.
Note: This same issue was also found in Categories.

@jackdishman Do you mind taking a look?

Something's wrong with pagination in frontend.

I tried to scroll on home page when I got these errors. Happens only on local deployment (commit 053829c), and not on test-node, so I am guessing some latest un-deployed commits have this issue. I can't seem to figure out what's wrong.

What's happening

Expected (with shorter name)

Remove old Text editor and replace with Quill

Start date: Oct 12
Estimated completion date: Oct 18

Check out the video. If you exit a bullet list, then for some time, you can't make another one. Also, how do you exit a bullet list without deleting the whole list? xD

In the profile page, the settings dropdown is sent to the background, unlike other pages, where the settings dropdown is above all screens. I am guessing the z-index needs to be updated?

For pagination on feeds to get posts including

• homepage
• tag subpages
• category subpages
• profile pages (posts, reposts, bookmarks, comments)
• Lists: followers, following

1. #133
2. Creative for displaying repost on a post preview card

mock-ups here: https://app.zeplin.io/project/603e81e66a60d1a5df091ddb/screen/6144330c2be2f728e1aaca08

The X button tries to pop the last entry from the history stack to navigate to. When the article is accessed through the app, the X button behaves as expected.

When an article is loaded directly from the link (either through opening it on a new tab or by opening a new tab and pasting the link), things can get unexpected. Either the X button won't lead anywhere (because there is no history to pop) or it will open the new tab page (because that was the last history entry).

Expected behaviour:

Only navigate to a history entry if it is a capsule.social entry. In any other case, if the previous history entry is not capsule.social, navigate to home.

Implement functions that can be called to add / remove / retrieve bookmarks.

Deadline: 14th October

Create a config file so that connection to smart contract on NEAR network is easily switch-able, similar to: https://github.com/near/create-near-app/blob/master/templates/vanilla/src/config.js

Prioritised due to recent incidents on testnet due to which it was down on 16th Sept, 2021: https://status.nearprotocol.com/

Dependencies: deploy capsule-near smart contract on desired networks of NEAR

Estimated start date: 22nd September, 2021
Estimated completion date: 22nd September, 2021

Getting the following error while creating a post: Error: multihash too short. must be > 2 bytes.
Seems a validation issue.

Add the frontend functions to interface with the repost feature.

https://github.com/capsulesocial/capsule-orbit/pull/41

DL: 22/9

https://www.notion.so/capsulesocial/29a0f6319b564b4ba60980f5b46d9428?v=c3dd9d9c7d6d4023ae38ce912de4941f

• Comment must have a reaction
• Post must belong to a category
  start: 21.09.21
  exp end: 21.09.21

When I update my avatar in settings page, the avatar on that page and on the home page gets automatically updated once my NEAR profile is successfully set. However, if I go to my profile the avatar doesn't get updated until I hit the refresh button.

I suppose it has got something to do with caching, but I am not too sure.

Implement backend function that can be called to delete a post

Deadline: 21st October, 2021

Presently, we send encrypted content signing key and encrypted NEAR access key to capsule-server on registration. In order to eliminate capsule-server, we must stop sending these keys to capsule-server.

Store NEAR access key in localStorage instead. Do not remove it from localStorage after a user logs out.

Add the ability to delete a post to the frontend