privateblue / paragraph-api Goto Github PK

FOLLOW arrows can point from users to blocks too. Notifications are sent about followed blocks too.

also add validation to the whole thing

If a user wants to link two blocks that are already linked, it should still be recorded. This data might be used for personalization later.

new node label: Page

Pages have:

• id
• timestamp
• url
• author
• title
• site

new arrow type: SOURCE

SOURCE always points from Page to Block

SOURCEs have:

• timestamp
• index (a zero-based index to reconstruct the original order of the Page's Blocks)

LINK arrows may point to Page nodes too, not only Blocks

The API should be able to somehow link, append, and possibly prepend Pages to Blocks, by providing an external url. This action should parse the provided url, create a Page node with all metadata, create Block nodes by scraping content, and connect the created Page to these Blocks with SOURCE arrows.

Also it should be possible to provide the specific target Block of the Page to be linked or appended (or prepended). Although this could also be a frontend feature, realized by two API calls. In this case the new API call would only create the Page node, link to it, parse the page, create the Blocks, and connect these to the Page with SOURCEs. See https://github.com/privateblue/paragraph-frontend/issues/10

depends on #6

depends on #3

Remaining work is related to the follow functionality. Notifications could be received when:

• someone followed / unfollowed me
• someone I follow created a new Block
• someone I follow logged in

After adding the block star functionality (see #20), additional notification types are possible:

• a block I stared got shared, replied, linked
• someone stared / unstared a Block of mine