Agenda
Future of the agent server
Integrated better into HM protocol
IPFS storage
Unified permission system
Schemas (Onyx Project)
asdf
Agent Server Redesign
Consistency with HM proto + IPFS
User goal: see the exact signed agent+context that led to agent comments+changes
Generic Storage + Permission System
IPFS - Agent server wants to save arbitrary data and specify the permission policy for this.
Generic Resource Concept with Permissions + Schema
Maybe requires a daemon plugin system so that it understands different resource behaviors.
Or, maybe we ship the daemon IPFS data+permission system as a go library?
Linking system- use regular https links to agent server. Suggested by Burdi
Another framing: moving agent memory here, does this behave like a new "git" impl
New Hierarchal Document Permissions system should incorporate these ideas!
Bug with Caps not Syncing
hm://z6Mkq9emq1yUBq4KSeiSH5yzgNBJSnidPVqFnTpzjCdLxB3R/:profile?v=bafy2bzaceauy3rmah2gf2yjkcdzlm2u5ua3w2a6k3qrjkfzywayzazls2arp2&l - bug has probably always been there.
Frontend does not push caps?
Onyx Schemas
To what extent does the daemon need to understand schemas?
Does it validate schemas?
Daemon can dynamically run code for interpreting/validating/indexing custom data types.
Schema permanent data: how should it work??
Plugin System
Is inevitable?
If we host arbitrary applications inside seed, we are an OS
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime