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.

This project is very simple: We want to update the design for our embed cards to this: New Cards design As you can see, this one are simpler. Nothing too complex. but this will make sure we have more Visual consistency across Hypermedia Elements in the app.

We believe the best tools stay out of your way. Creating a new document should feel like adding a thought, not launching a process.

Problem Solution Scope

Problem Solution Scope Rabbit holes No Gos

Import content into seed ecosystem

Problem Solution Scope

Power feature I wanted to test how it would look and feel. so I decided to prototype it!

Idea to show the Directory in a full page. Imo if we have this we don't need the left hierarchical document navigator. However, we can have both. They are not incompatible! Inspirations Sketches Demo Mockup

Shouldn't Ethosfera Homepage show all members in the Site? 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 activity 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.

Lunaticoin.blog site disable activity panel on its homepage, hence, we can't see the document panels on the homepage: However, in gabo.es I have also disabled the panel, but I still see it:

I hover over Solution, and it has a green background. There is also a grey background for the entire group. My apologies, , but I still don't understand the meaning. I have asked this question before, but I can't find the explanation you gave me then.

Summary The Core Problem: Hotlinking is Mandatory Download Tracking Requirement Exception: Derivative/Remixed Images Enterprise Workaround Options for Local-First / P2P Apps Sources