Fixes around the Activity panel

Activity + Discussion panel fixes documentToText Activity Filtering Feed sorting Video

Feed and Memory leaks

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

Private Documents and Memory Leaks

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 refactor overview

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) );      

Web Key Linking with Desktop App

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

Iskak's update September 9th

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

Project: Introducing list node type

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

Navigation Infrastructure

https://linear.app/seedhypermedia/issue/SHM-2020/project-navigation-infrastructure

Editor test coverage

https://linear.app/seedhypermedia/issue/SHM-2016/editor-test-coverage

Design Project: Identity System

We are still shaping the design methodology. Please be flexible and constructive. Currently, we have two Active Design Projects. The other one is . It is hard to have two active projects at the same time, but we want to unblock  with this one so he can start working on the cryptography and backend. A Design Project is different from a Development Project, which we have been using all these years. A Design Project involves deep design work, every team member is expected to participate, and it is usually composed of more than one Development Project. Our Design Process follows Google's Design Sprint Methodology. The goal is to provide a mix of methods for meetings and async work. We can use different techniques depending on the Design Project. However, we should always be aware of the 6 phases. It is very probable that every time we skip a phase, we will end up having to come back and redo it, because the outcome won't work. Below are the 6 phases applied to the current Identity System Design Project. Each document should be a method output. Let's see how we operate async! Everybody is expected to: Phase 1: Understanding Phase 2: Define Phase 3: Sketch Phase 4: Decide Phase 5: Prototype Phase 6: Validation Project Tasks

Design Project: New Users quickly understand the Basics of Seed Hypermedia

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

Zero-Knowledge Multi-Device Identity System

Problem Scope Solution Rabbit Holes

Blob Visibility & Access Control for Private Documents

This is a status update for the current state of  implementation, and also the technical and architectural documentation for it. The names of files and other code-related things are valid at the time of the writing. Things might change as we continue developing these features. The Core Idea Visibility Tracking Access Control P2P APIs Frontend APIs Final Notes

Web Builder

Many new users think that Seed Hypermedia is a Web Builder. When this happens, users get frustrated because we don't meet their expectations. How can we escape from this notion? My first thoughts are:

Enhancement Note: Add commentary metadata to Card Embeds and Query Block results

https://linear.app/seedhypermedia/issue/SHM-994/add-commentary-metadata-to-card-embeds-and-query-block-results

Enhancement Note: Email improvements

https://linear.app/seedhypermedia/issue/SHM-1834/major-email-issues

Enhancement Note: Comments on moved documents

https://linear.app/seedhypermedia/issue/SHM-1754/comments-on-moved-documents

Notions: Documents and Pages

Documents and Pages are different notions. In Seed, documents are automatically turned into webpages, which can look confusing to people. Bea is proposing to change the wording to use 'Page' instead of 'Document'. I believe we first need to research the meaning of each notion before taking a drastic decision. Maybe we need both terms! What if a Webpage is a document with a web URL and a layout that you configure in the Preview Screen? Dynamic Webpages, Static Documents Most products get this wrong. Definitions in the Web Context Opportunity to clarify the Notions in the Publish User Task Site Owners want Layouts for their Sites