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.

React Virtualization for Large Lists and Trees Problem Solution Flat Lists → @tanstack/react-virtual Hierarchical Data → react-arborist Integration Points Scope Rabbit Holes No Goes

Installation Deploy the automation system by running the following command on target production servers: curl https://raw.githubusercontent.com/seed-hypermedia/seed/main/ops/install.sh | sh This installer: Deployment Script Architecture Runtime: Bun (TypeScript/TSX) Source: https://github.com/seed-hypermedia/seed Execution Schedule: Nightly via cron Modes: Headless (default), Wizard Operational Modes 1. Headless Mode (Default) Automated deployment execution without user interaction. Workflow: Example: bun run deploy.tsx Configuration Management Location: /shm/config.json Purpose: Stores deployment parameters and tracks desired state Example structure: { "domain": "node1.seed.run", "email": "ops@seed.hypermedia", "compose_url": "https://raw.githubusercontent.com/seed-hypermedia/seed/main/ops/docker-compose.yml",p "compose_sha": "a3f2b1c", "last_updated": "2026-01-21T10:30:00Z" } Dependencies Cron Configuration The installer sets up a cron job that runs nightly in headless mode: 0 2 * * * cd /opt/seed-deploy && bun run deploy.ts >> /var/log/seed-deploy.log 2>&1

https://www.figma.com/design/5DnHLFGQ1BsT4ca37IxSQe/UX_Seeds?node-id=900-5791&t=HEny2QwNufWkzRw8-1 User Stories Problem Scope Solution Rabbit Holes

We currently have a "hosting" server which allows users to register subdomains, associated with emails. Each domain is associated with an account. There is also a "notify" server which allows users to register for email notifications for a given account. But the notify server does not know which account is registered for notifs. These are independent services, not part of the central hyper.media service. Solution Identity Server DB Schema Hosting Server DB Schema Create an Account with a Vault API Endpoints Open Decisions

Defined interactions Designs (WIP)

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

Lists are one of the most critical elements in Seed Hypermedia, but much of their potential is lost because oversized headings and excessive paragraph spacing take up too much space. Additionally, collapsing and expanding lists should persist. This problem becomes very clear in the  : Everything we do in seed involves manipulating concept and symbol structures in service of the mental structures. The new participant needs to understand complex concept structures before being able to participate. Once they participate, they have learnt new concepts and also improved those concepts by changing their symbol structures. Hierarchies and associations are two key concepts for humans. We need Lists and Links are the way that our This is exactly what we are building and what we refer with Amplifing human intellegience. Participants read and understant new concepts, the participant through different reasoning processes, and the improve the concept structures to solve. This is exactly what we are experiment as a team, as a community, when we are using seed. We are learning, we are building symbols structures, we are making the world a better place basically. where much of the structuring that goes on in the human's total problem solving activity is for the purpose of building a mental structure which in a way "puts the human up where he can see what is going on and can point the direction to move next.

A Comprehensive Design Document

What if we add a new format setting that sets the Discussion section as the default view for a document?

The Home page can have a special behavior compared to the rest of the documents. On the Home page, the document options could surface site-wide views, including: This may require designing a slightly different document options panel specifically for the Home page. Another element that distinguishes the Home page is the navigation menu, which already makes it behave differently from other documents. Because the Home page lacks strong semantic meaning, it is well-suited to act as an entry point for showcasing the site’s structure and improving overall understanding and discoverability. Additionally, placing site-wide views on the Home page avoids the need to introduce another location for icons representing site-wide activity, comments, people, and documents—an approach that could otherwise create conflicts or increase confusion. Users often struggle to understand recursiveness. Centralizing global views on the Home page—while keeping document-level views within individual documents—could simplify the mental model. For power users, this recursiveness can still be exposed when accessing pages from the Home document.

Users frequently report confusion between the Activity and Discussion panels. Having a comment box in the Activity panel contributes significantly to this confusion and does not provide clear value. For users to create content effectively, they need a clear and unambiguous destination for their input. The Activity panel does not serve this purpose. Instead, it overlaps conceptually with the Discussion panel, making it harder for users to understand where comments should live and where conversations should happen. Removing the comment box from the Activity panel would reduce cognitive load, clarify intent, and better differentiate the roles of Activity versus Discussion. Can we remove it?

See source: https://stellar.org/blog/developers/passkeys-a-light-introduction-to-improving-blockchain-s-ux Passkey generation: Using a passkey for transaction authorization: Although these steps seem complex, the user experience is actually quite simple. All JimBob does is sign up for the application with his fingerprint and then verify his identity with his fingerprint again to perform the desired action. The user experience is quick and seamless without sacrificing security. JimBob might not even know he’s interacting with a blockchain. Screens