Main feed view

[nichoth]

The view on the home page

• [x] should get posts from your friends (1 hop)
• [x] need to get the path in wnfs for friends & their shared files

Any friend can view your 'friends' collection of posts. This is difficult because it means things work the way they did previously, meaning we need to share our wnfs files at the same time that we add a friend to the DB — need to synchronize state across two systems.

---

get post path

• [x] should take a post object only

[nichoth]

• [ ] need to get posts with respect to permissions

shared files

• [x] first create the shared files in wnfs
• [x] then post to the DB what you shared & who the recipient is
• [ ] The other person needs to ack your new share. Then we can delete the share record in the DB. ack means that they have seen your share and accepted it in wnfs

---

• [ ] need to write permissions to DB, so we can use them in queries

We need to get any posts that a given username has permission to read

Object shape for permissions

{
  username: 'alice',
  permissions: {
    'collection2': {
      users: ['desmond', 'carol'],
      files: [hash2, hash3]
    },
    'my-collection-name': {
      users: ['bob', 'carol'],
      files: [hash1, hash2, ... ]
    }
  }
}

// `permissions.collectionName` here refers to a directory path

So the DB query means

First get your friends, then get the files you are allowed to read for each friend

Must be able to get a file by its collection.

---

[nichoth]

Query is like

• Get any accepted shares by username
• then get any posts related to that accepted share

Need to relate a post to a given shareId.

Could keep a shareId next to the post object.

{
  post: {...},
  shareId: 3
}

This means the post author needs to know the shareId for each post.

---

Users need to track shared folders of their own, so you can add a shareId to every new post.

We have been using post.type to track visibility. Value of either 'friends' or 'private'

Need to start using shareId. Need to keep track of our shareIds, and which folder they correspond to.

Keep a document like

// save at `private/shares.json`
// This is a map of { shareId: pathname }
{
  "1": "/private/friends",
  "2": "/private/coffee-crew"
  "3": "/private/baloney-world"
}

This way when we write a new file to '/private/baloney-world', we can include the shareId in the post message.

[nichoth]

Get any shares that are visible to you

We want any shares that we have accepted

get acceptedShareMessage where username === myUsername

then get any posts by acceptedShareMessage.shareDetails.sharedBy.username, where shareId === acceptedShareMessage.shareDetails.shareId

---

get the usernames of the acceptedShareMessages use those username to get posts filter the posts, so that post.shareIds includes the shareId in share-msg

[nichoth]

When you make a new post

• [ ] each folder should correspond to a shareId
• [x] need to select visiblity/folder when you create a new post
• [x] create a private file map of folder name to shareId. Use the map when you create a post. Add shareId to the post object based on its folder/visibility.

[nichoth]

• [ ] when you create a new account, the shareId for 'friends' folder should exist, because you would share it with the person who invited you