Indexing issue
Window backgroundable and movable thanks to @Untitled Contact
one doc causes this exponential growth due to lots of block moves.
700 changes, 157k blocks, and 404k full-text index rows.
@Untitled Contact investigating
must re-release the app with this fix ASAP
re-index takes down production web
makes reindex happen very quickly
beating the drum for zero-downtime deployments
at least, allow reads (temporary downtime of writes)
today: make re-indexing fast
one day: keep old daemon+web running (writes disabled), copy over db and launch new daemon for reindex. once reindex completes, switch over to new daemon+web, re-enable writes
hm26 inode resource, permission system.
keyhive inspiration, keyline has less causal structure
in keyline, each document is a key. (we want fewer keys)
in keyline, "admins are forever" - this simplifies permission checking
admins can be "removed" by rotating the permanode
using permanodes instead of document keys
blob privacy
blobs upload must include context (breadcrumbs) that explain why and where this blob will be used, giving proof that writing is allowed in that context
blobs must be sent in authority-first order
bitswap doesn't support privacy.
bitswap accepts arbitrary data(?!)
we need a deeper fork of IPFS for private blobs
IPFS gateways changing. "trustless gateway?!" - client verifies and assembles all data
new bitswap policy for gateways:
no libp2p needed for getting blobs, use http transport
"we have disabled the provider system" –I guess thats because we have disabled the DHT broadcast
blobs only enter the system with our new policy/system
comments
are comments resources? (maybe you dont want a comment to have a location)
comments are really more like triples
high level q: how does data/content/location relate to authority?
not sure. somehow very related to the sidebar
authority graph is critical
placement graph is for naming/addressing
what are the relevant policies/workflows?
can I accept some data to save?
is the data valid according to permission graph?
am I interested in saving this
can I send some data to a peer?
is it public OR is that peer allowed to read
custom/other workflows??
can I execute something?
"breaking" change
maybe requires re-invite
sub-document caps are trashed
everything else can be migrated
@Untitled Contact breaking up project into roadmap, smaller tasks
feat: organize private docs into hierarchy
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime