Agenda
Email validation technique
Vault bug when clicking validation link on another device
Switch to verification code - is this a better UX?
Performance Issues
Demand-Driven Sync
Update from hm://z6Mkq9emq1yUBq4KSeiSH5yzgNBJSnidPVqFnTpzjCdLxB3R/:profile
Sync statistics measurement and reporting
SQLite busy errors on peer sync
use build to see INFO logging, and you may see SQLite busy errors
Debugging sync+DB bottlenecks
Trying to fix/use the daemon http /debug endpoint
Frontend "just trust me bro" sync API
hm://z6Mkq9emq1yUBq4KSeiSH5yzgNBJSnidPVqFnTpzjCdLxB3R/:profile says the FE should not hammer the daemon
hm://z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4/:profile?v=bafy2bzaceciguevcgg7lacbo7fgix52zw3ewydimhmvbgyfzepmliapuaepam&l says that FE has no API for fine-grained syncing. We have no api to request only profile, or only document, or only comments, or document+comments, or only direct children
Authenticated nodes
Two goals:
No security for local daemon- vulnerable from other devices on LAN
Read private docs on web
Cross-Site vulnerability: malicious web JS app may access local daemon
For web server, Node.js must be involved. Daemon will own responsibility
Web approach must be different
We will introduce a session system for the daemon.
Web node.js will proxy back to daemon's session system.
Desktop to use sessions directly
Todo: review HTPP server inside electron app
One day: We can use this to prevent arbitrary pushes to the server
hm://z6MkgYR76i3w2Xc2fcvgFJWfYjsop6YwUonDhQx3AdLmQ4BQ/:profile to write a note/project about this
SHM Development Principles
Single Responsibility Principle – Don't duplicate code
Tradeoff of stability and opportunity cost of delivering features
User-Centric Pragmatic – focus on performance and features, even at the cost of clean code
These principles should directly connect to our "Team Values"
Broken Publish Button - https://github.com/seed-hypermedia/seed/issues/484 cc hm://z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/:profile?v=bafy2bzaceaf5y2554kmdly7yz55fowqum4546bpa2gmi5gntflhlf4gaomdg6&l
for now just copy link to push
Commit message should be on a Change, not a Ref
hm://z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/:profile?v=bafy2bzaceaf5y2554kmdly7yz55fowqum4546bpa2gmi5gntflhlf4gaomdg6&l implemented a cool feature with commit message, but we should put that data on the Change DAG so that the data structure is preserved
Quantum Fears??
Design auth sessions with this future in mind
AI Meetup today
Showing WIP to the AI community is encouraged
App still has embarrassing performance+UX issues
Formal presentation for next meetup
Tomorrow meet to discuss how Agents will write data in SHM
Onyx Schema
Unified Resource type
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime