Donate | Contact | Search

requirements / ideas

• do ssl,dnssec,hpkp,hsts, whatever,4 the web site *and* internally w/ sharing so you know who youre talking to? or resolver does? om onemodel https ssl main
• supports cooperation even with differing worldviews
• design it so one doesnt have to spend excessive time "keeping up to date" on things, but it provides info just-in-time (pursue topics only when interested etc)
• 813_ trust networks/security [MAIN ENTRY]
• should it include a protocol? or something just the db code (java) interface? or alw connecting via a jdbc string so that+code is enough? or rest? dift DB typs?
• prevents wrong person from deleting data (like the system entity in a public site, things it connects to, ETC?) in an OM instance.
• suggestion from SN thread: packages of data that can be depended on transitively
• includes equivalent of "talk pages" (to discuss changes to the data)?
• might require handling time zone dif'cs between instances of DBs and clients: make all DBs UTC and all clients specify a zone or get it from the OS?
• needs undo feature?
• ?: need2version control entities & their attrs, like wikis do? when will be needed?
• does licensing matter in sharing, like systematic ways to indicate CC lics &c & allow the features that fit/allowed by the lic? (or have default lic 4 now)?
• omit dates from public info? always or when? (like, a person might be public, but their bdate might not?)
• full-client browser support: how make the use cases work for those who would not ever use the textui (or any non-browser UI), to share & work well w/ them?