Push Details

Proposal: send feedback from nodosdeconocimiento.es to seedteamtalks.hyper.media

We want users visiting: https://nodosdeconocimiento.es/feedback to submit feedback about nodosdeconocimiento.es, while the resulting private Seed documents are created under: seedteamtalks.hyper.media Users should not need write permission on seedteamtalks.hyper.media. Current issue Proposed approach Why this is better Server permissions Configuration Created document content Frontend behavior Authentication decision Summary

Table Block Design

Is this a backend or frontend concern? Frontend

Transformation happens between editor state to frontend block state.

Block Tree State

TableBlock

TableColumnBlock (all of them)

TableRowBlock (all of them)

Cell Blocks (normal blocks)

Editor state

probably resembles HTML

has <td> cell wrappers

Performance questions around this "heavy" data structure

Decision: We will not use Cell blocks in the block state

Use case questions about query blocks (database) vs table blocks

Table blocks inside documents and comments should be used for smaller datasets

Tables Project Proposal

This is a proposal for implementing tables in HM editor

Optimize Expensive Operations at publish time

For large documents and tables we have possibly slow code at publish time, because we iterate over the entire content in order to determine the operations that will be sent to the backend.

Is it currently slow to publish large documents? hm://z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou/:profile?v=bafy2bzacecoevvu2ebpntbrhm552uqp3ag5vrxvukpk7a4vvfmhazkk7smu5y&l will investigate.

hm://z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/:profile?v=bafy2bzacebrehvt6ciku2flf23pbf4qm5o7ylje5iihoqir2ho3urr7vmbntg&l will write a doc about event driven editor plugin

Sync Immediacy

hm://z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4/:profile?v=bafy2bzacebcdqgkczlb6f6y4pfhegwdd27tomlrxwxmyai6kyr4mk2i5rxbks&l would like to understand what is the exact RPC between peers?

How to handle private documents? Unlisted documents? Deletes?

We currently sync from 25 random peers max, plus bootstrap peers! (Very naïve sync strategy)

We need peer reputation system (and the already-existing domain store) to decide which peers to sync from and who to frequently poll from

What is the P2P Syncing protocol

Peer A requests a Resource string from Peer B while syncing

Resource string definition.

Does it include :comments ? :profile

Peer B responds with a set of Timestamps and CIDs, using RBSR. Peer A passes the CIDs into IPFS "blockstore" for syncing

How do we sync citations? This is broken right now between self-hosted peers

Fast Blob Propagation

Get a published blob to a connected peer in about a second by caching the server's reconciliation set in a monoid tree keyed by inbound demand, plus codec canonicalization on a new /0.9.3 protocol.

Domain Store

Can be used for network dialog to show domains.