in-band caching policies and routing table information
overlay vs core routing protocol
formalization of log-based communication and nested tangles
fancy networking functions (e.g. subscriptions plus relational algebra, or mapping, filtering, reducing, or just arbitrary (pure?) computations)
format(s) for in-band data
(log) name resolution
hierarchical (log) names rather than ssb's flat ones
how does this affect cypherlinks and causal order?
efficient causal order computation (i.e. directed reachability along cypherlinks)
blob retrieval strategies
defense against attacks mostly depends on trust along the social graph - can ssb without a social graph be feasible?
requiring storage of everything leads to scaling problems
global coordination of "conventions" (in-band foaf information, pub announcements, type, crypto)
application framework API between server and clients/plugins
data independence, concurrency
indexing
in general: what should be part of the core protocol (log structure), and what should be convention-based interpretation of payloads?
supporting arbitrary payload (as opposed to a specific self-describing data format)
can already do this via "content": "asdf.boxwhatever" anyways
disentangling the multiple purposes of pubs
figure out which of the parts that are explicitly modeled after (or rely on) human interaction patterns are strictly necessary and which are not (and whether those are desirable anyways)
this boils down to the question "Does ssb still work well when logs don't correspond (roughly) to humans?"
problems arising from building social (networking) applications in particular upon ssb
Don't mind me, just moving some thoughts from brain-RAM into persistent storage. Feel free to add more things here.
distinguish between ssb application layer challenges/future work and replication layer
figure out how to split this between the section on ssb problems and future work
underlying feeds as trees or dags (pure recursive tangle model) rather than paths (dags as solution to same-as?)
cyclic feeds? (cypherlinks expressed as author-id + seqnum can form cycles)
what exactly is a cypherlink? (see above)
generic app-layer same-as solution
(soft) deletion
educating users about the pecularities
hard local deletion
privacy of social graph (TODO find ssb thread on confidential set membership tests)
privacy of subscription-based networking in general
push?
dealing with broken crypto primitives
offchain content and it's risks/drawbacks
log lifecycle (termination, key rotation)
log compaction (lossy)
partially replicable, order-preserving append-only logs (leyline-core)
partially replicable, non-order-guaranteeing append-only logs (hypercore)
in-band caching policies and routing table information
overlay vs core routing protocol
formalization of log-based communication and nested tangles
fancy networking functions (e.g. subscriptions plus relational algebra, or mapping, filtering, reducing, or just arbitrary (pure?) computations)
format(s) for in-band data
(log) name resolution
hierarchical (log) names rather than ssb's flat ones
efficient causal order computation (i.e. directed reachability along cypherlinks)
blob retrieval strategies
defense against attacks mostly depends on trust along the social graph - can ssb without a social graph be feasible?
requiring storage of everything leads to scaling problems
global coordination of "conventions" (in-band foaf information, pub announcements, type, crypto)
application framework API between server and clients/plugins
indexing
in general: what should be part of the core protocol (log structure), and what should be convention-based interpretation of payloads?
supporting arbitrary payload (as opposed to a specific self-describing data format)
"content": "asdf.boxwhatever"anywaysdisentangling the multiple purposes of pubs
figure out which of the parts that are explicitly modeled after (or rely on) human interaction patterns are strictly necessary and which are not (and whether those are desirable anyways)
problems arising from building social (networking) applications in particular upon ssb