- Bump @usememos/editor to 26.10.27: Markdown mode now highlights syntax
inside table cells, so a URL anchor in a table-cell link, such as
[Kappa](/memos/abc#ikebukuro), reads as part of the URL instead of a
tag.
Refs usememos/memos#6480 (item 13).
- Focus mode: a narrower sheet (max-w-3xl) with larger text through
MEMO_FOCUS_EDITOR_THEME; its header shows only the memo's time ("Now"
before it has one) and the exit button; toggling it runs a view
transition that grows the frame out of its place on the page and back,
instant under reduced motion or without view transitions.
- Markdown mode's + menu item uses Lucide's CodeXml instead of the
pilcrow.
The frontend handler served index.html for any extensionless path, so
OAuth Protected Resource Metadata probes under /.well-known/ received
HTML with status 200. MCP clients that run RFC 9728 discovery before
trusting the endpoint failed to parse it, while a 404 would have told
them the server does not advertise OAuth.
Paths with a hidden segment are never app routes: usernames, memo UIDs,
and fixed routes all begin with an alphanumeric character. Return 404
for them, following RFC 8615 for /.well-known/ and the dotfile
convention of common static servers for paths like /.git/.
Fixes#6495
The renderer discarded the SQL of an operand that folded to a constant,
such as the left side of `x || true`, but kept the arguments it had already
added. Callers append their own predicates after the filter fragment and
bind positionally, so each leftover argument bound to a later placeholder.
Fold boolean constants out of the condition tree before rendering, so a
subtree either renders with its arguments or not at all, and reject any
rendered fragment whose placeholders and arguments disagree.
Tables are styled like claude.ai's: the table fills the editor's width
with a round frame, a tinted header row, lines between rows and no
vertical lines, and cells wrap at words instead of mid-word. HTML tables
rendered through the html view look the same.
Footnote definitions render their text as Markdown. In read-only memos
the referenced definitions are collected in a section at the end of the
note, above the attachments, in order of first reference, each with a
backlink per reference; unreferenced definitions are left out and
labels show as written. While editing, definitions stay where they are
written.
Both fix items reported in #6480. Wire the editor's two new labels,
`footnotes` and `backToReference`, to new `editor` keys in every locale.
Use neutral, theme-aware surfaces and consistent density for hints,
menus, dialogs, and form controls. Restore visible field focus and use
Base UI tabs for keyboard navigation and RTL support.
Link preview was a Timeline view option, so it reset to on everywhere else.
Double-click to edit was an instance setting an admin chose for everyone.
Both are presentation choices for one browser, so they now live in a single
localStorage-backed store shared by every memo view and are toggled from
Settings > Preferences under "This device".
MemoRelatedSetting.enable_double_click_edit is removed from the API and
storage protos and reactions becomes field 1; stored rows that still carry
the old key load unchanged. The admin Memo page keeps only reactions.
Pass the editor palette once as `tokens.colors` instead of the same object
as `light` and `dark`. Drop the heading sizes, leading and weight from the
app's heading classes: the editor sets them in its own unlayered stylesheet,
scaled from its `fontSize` and `lineHeight` tokens, so the Tailwind sizes
never applied and would not follow a changed token. Only the muted h6 color
remains. No `highlight` token: memos' HTML sanitizer drops `<mark>`.
Correct the color guide's theme-switching section, which described a
`.dark` class memos does not use and which the editor would now follow.
Inline raw HTML inside a link, such as ruby annotations in a table cell,
now renders through the HTML view in both the composer and the memo view.
The editing session became a lazy chunk in #6481, so a signed-in user's
Home showed a blank card until the chunk arrived, then the feed jumped up
18px when the real composer replaced it.
The Home and Explore routes of a signed-in user now load the session's
code together with the page, so the composer renders with the page as it
did before the split; visitors keep the lighter page. Where a draft can
still suspend, the fallback is a still of the empty composer with the
same frame, placeholder line and toolbar height, so nothing moves when
the session takes its place.
Replace mermaid with pele for ```mermaid code blocks. Diagram types load
on first use through pele/lazy, the SVG takes its colors from --pele-*
variables mapped to the theme tokens in index.css, so a color scheme
change needs no redraw, and the layout shrinks to the memo's width while
keeping the author's direction.
Bump @usememos/editor to 26.10.22.
Take the tagline, one-liner, and short description from the rewritten
BRAND.md in usememos/.github and use the serif lockup and the light and
dark timeline previews published there. The README now leads with what a
visitor gets, keeps the quick start to one command plus the URL to open,
drops badges that repeat the sidebar, and carries the star-history
badges
instead of the chart. The local Georgia wordmark is removed.
In the app, the about page, manifest, and English locales carry the same
copy. The identity label uses the theme's serif stack at the wordmark's
weight and spacing rather than a vendored face. The about tagline sizes
to its column so neither sentence breaks mid-line, and the version chip
is the single place for build identity: a release links to its tag and a
development build links to its commit, so the Build commit row and its
locale label are gone.
The composer can show the whole memo as Markdown text and edit it as
plain
text, using the editor's new source mode.
- Turn it on from the + menu ("Source Mode"); a small "Source" tag in
the
editor's corner names the mode and switches back to rich text. The
first
line leaves room for the tag.
- The choice is remembered per device and applies to every composer.
- Tags and tasks are read from the Markdown text in source mode, so tag
suggestions still skip tags the memo already has; the checklist chip
is
hidden because it cannot apply.
- A saved caret remembers its mode and is not restored in the other one.
- DropdownMenuCheckboxItem gains `indicator="end"` for a trailing check,
replacing a className override in the sidebar Tags menu.
- Tag autocomplete follows the backend tag grammar: `hello#work` and `C#`
now match while typing, so the test expectations move with it.
- A titled link (`[url](url "title")`) is no longer treated as a bare URL
for link-preview cards, since the card would drop its title.
Share logo and identity typography across navigation, auth, and About
while preserving custom branding.
Use a transparent blue favicon and Celadon installation icons with
refreshed cache versions.
Quotes and callouts can hold lists, so a quote with a bullet list
renders
instead of showing its Markdown source, and callouts take the Linear and
Notion style: a tinted box with the type's icon.
Move memo content size into usage limits, with 8 KiB content and 32 MiB
upload defaults when settings are absent. Represent stored rule targets
with all_users or a positive user_id, and use that same schema for
deployment configuration.
Rename the memo count metric, remove reserved proto declarations, and
renumber fields and enums for the unreleased schema. Synchronize
enforcement, settings UI, generated clients, and tests.
The instance-wide maximum upload size in the storage setting and the
per-user UPLOAD_BYTES usage limit were two caps on the same thing, with
a
rule that the per-user value could only lower the instance value. The
storage setting field is removed, and the all-users UPLOAD_BYTES usage
limit is the only per-file cap. A user's own limit replaces the default
in either direction, and no limit means any file size.
- Remove upload_size_limit_mb from the API and store storage settings,
the 32 MiB store default, and the deployment config check.
- Drop the FILE_TOO_LARGE error; every refusal is QUOTA_EXCEEDED with
metric UPLOAD_BYTES.
- Split usagelimit.CheckFileSize out of CheckUpload and call it from
memo import, so import is no longer a bypass.
- Remove the Maximum upload size field from the Storage section and the
instance-limit warning from the usage limits dialog.
The old value is not carried over. Instances that relied on the default
accept any file size until an admin sets a limit.
ListAttachments was the only list RPC whose page token was a bare decimal
offset. Switch it to the shared PageToken format used by every other
paginated handler so the token also carries the page size and stays
consistent across the API.