Activity + Discussion panel fixes documentToText Activity Filtering Feed sorting Video

Week: @2025-10-21: Hypertuesday. During the past week I've been doing work with the feed and trying to find the memory leak. SQLite Memory leak Feed Next Week

Week: . During the past week I've been switching between debugging random issues, and continuing the work on . SQLite Memory Leak Private Documents Next Week

Email Notifications System Documentation Current User Stories Implementation Receive Email Notifications please read this document with user stories for email notifications. Current Limitations Future Development I think we can bring back the accounts table with a flag to determine if the (accountId, email) entry is a subscription or a linked account to email. -- Add back the accounts table with email linking CREATE TABLE accounts ( accountId TEXT NOT NULL, email TEXT NOT NULL, isAccountLinked BOOLEAN NOT NULL DEFAULT FALSE, createdAt DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (accountId, email) ); The only issue is that email preferences are different for own account and subscriptions. Because of that I would instead propose creating a separate table for linking an account to email. CREATE TABLE email_account_links ( email TEXT NOT NULL, accountId TEXT NOT NULL, createdAt DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (email, accountId) ); And we could add creation of linking tokens to allow verifying the email address in the welcome email. CREATE TABLE email_account_links ( email TEXT NOT NULL, accountId TEXT NOT NULL, linkingToken TEXT UNIQUE NOT NULL, expiresAt DATETIME NOT NULL, isVerified BOOLEAN NOT NULL DEFAULT FALSE, verifiedAt DATETIME, -- NULL until verified notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (email, accountId) );      

Some time ago we enabled the ability to create Web Crypto keys in the browser on all Seed sites, for users to be able to sign their comments right on the site they are visiting. Previously they were redirected to hyper.media because this was the only place where their identity key lived, as Web Crypto keys are tied to a single domain and can't be shared securely. Now, this creates fragmentation. Essentially you have a separate account on each web site you are commenting on. Our vision for solving has always been the idea of linking your keys. You account is essentially the set of all the keys you have on you different devices and web sites. So during the past few weeks I've been working on implementing key linking. We already used to have to link desktop keys to hyper.media, but it wasn't suitable as-is for multi-origin world we now live in. So, I'll explain some of the changes I did. It All Begins on the Web Linking Instructions Conclusions

Update: Next week I will continue working on notifications refactor and implementing new subscribe feature for readers without an account.

https://linear.app/seedhypermedia/issue/SHM-2056/project-funnel-analytics Our funnel identifies a user and measures the conversion rate from one step to the next step. We need to identify the pain points at each step to boost conversion rates. A Growth Funnel is a bit different from a UX Funnel. The Growth Funnel should be a single instance across the system. It is core to the strategy and to every member of the team. Once we discover our Growth Funnel, it seldom changes. UX Funnels are a design tool. They can change all the time with different experiments. Growth Funnel UX funnels

Outcome: New Users quickly understand the Basics of Seed Hypermedia Sketching Final Design Tasks

This is a small and focused project that is aimed to solve the double-subscribe button. If you want to see the roadmap for subscriptions, look at  We are ready to do this project now. It is a pretty simple frontend change. Unlike the grand plan for subscriptions, this project does not require a new identity system. Problem Solution Implementation Notes

Problem 01 Solution

This project explains the problems with our current list implementation and proposes additions to editor schema that should handle lists better.

https://linear.app/seedhypermedia/issue/SHM-1622/i-cant-paste-images-on-web-mobile-comment-box

A home page, why??? I like Activity I like their Profile Page Substack has List document types! I like where the edit button is Clean Editor

Smalltalk document from Alan Kay We have the intuition that we must treat emails privately. However, aren't they meant to be public? I see people treating them publicly all the time!

UCANS: User Control Authorization Networks Open Source Project from Brooklyn Zelenka, github.com/expede The JSON you provided is the payload of a UCAN JWT. It describes who is granting a capability, to whom, for what, and under what conditions. It is a new Auth System for the decentralized web. It solves the Confused Deputy problem that ACLs schemas have in distributed systems. Basically, once we break from the Client-Server model, servers with ACLs get confused about who has authority. Who is using UCANS: CRDTS, flat file storage, databases, decentralized compute, name systems, email, etc. Distributed RPC framework. Payload Resources

Some: