* feat: add NIP-85 Trusted Assertions feed & detail renderers
Add support for NIP-85 Trusted Assertion events (kinds 30382-30385) and
the Trusted Provider Declaration (kind 10040) with kind constants,
helper library, and feed + detail renderers.
- Add kind entries for 10040, 30382, 30383, 30384, 30385 to EVENT_KINDS
- Create src/lib/nip85-helpers.ts with cached helpers for parsing
assertion data (user, event, address, external) and provider lists
- Create shared TrustedAssertionRenderer for all 4 assertion kinds with
rank bar, subject display, and compact metrics preview
- Create TrustedAssertionDetailRenderer with full metrics table,
rank visualization, topics, and raw tag fallback
- Create TrustedProviderListRenderer/DetailRenderer for kind 10040
with provider table and encrypted entries indicator
- Register all renderers in kinds/index.tsx
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* refactor: extract NIP-73 helpers and shared ExternalIdentifierDisplay
Move getExternalIdentifierIcon() and getExternalIdentifierLabel() from
nip22-helpers.ts into a new nip73-helpers.ts since they are NIP-73
utilities, not NIP-22 specific. Add inferExternalIdentifierType() and
getExternalIdentifierHref() helpers.
Create shared ExternalIdentifierDisplay components (inline + block
variants) that use proper NIP-73 type-specific icons (Globe for web,
BookOpen for ISBN, Podcast for podcasts, Film for ISAN, etc.) instead
of a generic ExternalLink icon.
- Kind 1111 renderer now uses ExternalIdentifierInline for root scope
- Kind 30385 assertion renderer uses ExternalIdentifierInline (feed)
and ExternalIdentifierBlock (detail) for NIP-73 subjects
- nip22-helpers.ts re-exports from nip73-helpers for compatibility
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* fix: UI polish for NIP-85 renderers
Address review feedback across all NIP-85 components:
Icon: Replace BarChart3 with ShieldCheck for assertion kind constants
(30382-30385) — communicates "verified trust data" vs generic analytics.
Feed renderer: Subject is now the visual anchor (ClickableEventTitle)
with kind label as a small outline Badge above it. Rank bar widened to
w-32, color-coded green/yellow/red by score threshold. Fix "Zaps Recd"
abbreviation to "Zaps In".
Detail renderer: Metrics grouped into Activity, Zaps, Moderation
sections with uppercase section headers. Kind 30384 addresses now
show "Kind X by <UserName> / d-tag" instead of raw hex. ExternalMetrics
type badges now show NIP-73 icons + friendly labels (getExternalTypeLabel)
instead of raw k-tag values like "podcast:item:guid".
Provider list: Feed uses compact Badge for kind:tag + count summary.
Detail uses stacked cards instead of 3-column table for narrow panels.
ExternalIdentifierBlock: Linked blocks now show dotted underline on
label + ExternalLink icon for clear click affordance.
Add getExternalTypeLabel() to nip73-helpers for k-value display names.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* fix: use Progress component for rank bars, consistent sats formatting
Replace custom rank bar divs with the existing Progress UI component
(with new indicatorClassName prop for color-coded fills).
Make sat amount displays consistent with zap receipt renderer pattern:
value and "sats" unit are rendered as separate elements — numeric value
in font-medium, unit in smaller muted text — matching how Kind9735
displays amounts across the app.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* fix: use RelayLink for relay URLs, remove redundant kindTag, add relay hints
Provider list renderers now use RelayLink instead of raw relay URL
strings — shows favicon, insecure ws:// warning, opens relay detail
on click.
Remove kindTag display from provider cards — it's an internal
protocol detail redundant in the UI context.
Pass relay hints from provider entries to UserName so profiles can
be fetched from the relay the provider actually publishes to.
Add UserName relayHints prop (forwarded to useProfile).
Add RelayLink and UserName to Shared Components section in CLAUDE.md
so they're consistently used across the codebase.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* docs: expand shared components section in CLAUDE.md
Add BaseEventContainer, ClickableEventTitle, RichText, QuotedEvent,
and CustomEmoji to the shared components reference. These are the
core building blocks used across all kind renderers — documenting
them prevents re-implementation and ensures consistent patterns.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* docs: trim shared components list in CLAUDE.md
Remove BaseEventContainer and QuotedEvent — these are internal
patterns that kind renderer authors already know from context,
not general-purpose components that get misused or forgotten.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* feat: show metric type labels in trusted assertion feed view
Add Label components to the assertion feed renderer so you can see at a
glance which metrics an assertion carries (Followers, Posts, Zaps, etc.)
instead of just numeric values. Also swap Badge → Label for the kind
indicator for visual consistency.
Replace hardcoded green/yellow/red rank colors with theme variables
(success/warning/destructive) in both feed and detail renderers so the
rank bar works correctly across all themes.
Add Label to CLAUDE.md shared components list (22 imports across the
codebase).
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* feat: show provider kind tag in trusted provider list renderers
Add Label with formatKindTag() to both feed and detail views so each
provider row shows what it provides (e.g. "User Assertion: Rank").
Also swap Badge → Label for consistency with the assertion renderers.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
* fix: stabilize relayHints in useProfile to prevent fetch abort loop
relayHints was used directly in the useEffect dependency array, so
callers passing a new array literal (e.g. [p.relay]) on every render
caused the effect to re-run each cycle — aborting the previous network
fetch before it could complete. The IndexedDB fast-path masked this in
the feed view (profiles already cached), but the detail view showed
raw pubkeys because profiles were never fetched from the network.
Wrap relayHints in a JSON.stringify-based useMemo (same pattern as
useStableArray) so the effect only re-runs when the actual relay
values change.
https://claude.ai/code/session_01XjwLaShFSVPR5gNA7iUjuB
---------
Co-authored-by: Claude <noreply@anthropic.com>
* refactor: extract relay auth manager into standalone package
Decouple NIP-42 relay authentication from Grimoire internals into a
generic, framework-agnostic package at packages/relay-auth-manager/.
The new package uses dependency injection for pool, signer, and storage
(localStorage-like interface), making it reusable in any applesauce-based
app. Fixes the bug where auth prompts appeared even when the signer
couldn't sign events - now only emits pending challenges when a signer
is available.
Key changes:
- New package with RelayAuthManager class, pure auth state machine,
and comprehensive test suite (103 tests)
- Grimoire's relay-state-manager now delegates all auth logic to the
package, retaining only connection/notice tracking
- Auth preferences moved from Dexie to localStorage via pluggable storage
- Reactive signer lifecycle: auto-auth re-evaluates when signer appears
- Pool relay lifecycle via add$/remove$ observables (no polling)
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* fix: prevent auth prompts when signer is unavailable
Three bugs fixed:
1. Race condition in emitState(): states$ was emitted before
pendingChallenges$, so relay-state-manager's states$ subscriber
would read stale pendingChallenges$.value. Now pendingChallenges$
is emitted first for consistent reads.
2. relay-state-manager only subscribed to states$, missing
pendingChallenges$ changes. Now subscribes to both.
3. canAccountSign used constructor.name which is fragile under
minification. Now uses account.type !== "readonly" (stable
property from applesauce-accounts).
Added 3 regression tests verifying pendingChallenges$.value
consistency when observed from states$ subscribers.
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* fix: migrate auth preferences from Dexie to localStorage
One-time migration preserves existing user preferences: reads from
Dexie relayAuthPreferences table, writes to localStorage, injects
into the running manager, then clears the Dexie table. Skips if
localStorage already has data (idempotent).
Removes the DexieAuthStorage adapter — sync/async impedance mismatch
made it fragile. localStorage is the right fit for the sync
getItem/setItem interface.
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* docs: add README for relay-auth-manager package
Covers constructor options, observables, methods, auth lifecycle,
preferences, storage interface, state machine, and dependency
interfaces.
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* fix: address 3 bugs in relay-auth-manager
1. State machine: authenticated + CHALLENGE_RECEIVED with "never"
preference now correctly auto-rejects instead of entering a dead
challenge_received state that nobody acts on.
2. Auto-auth error handlers now guard with `status === "authenticating"`
before overwriting state, preventing a late-resolving promise from
clobbering a valid state transition (e.g. disconnect → "none").
3. API no longer leaks mutable internal references. getRelayState(),
getAllStates(), getAllPreferences(), and states$ emissions all return
shallow copies. Previously, consumers holding a reference to a
previous emission would see it silently mutate.
All three fixes include regression tests (110 tests, up from 103).
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* feat: make relay-auth-manager production-ready
- authenticate() now waits for authenticated$ confirmation via
firstValueFrom(race(...)) — resolves only when relay confirms,
rejects on disconnect. Uses Promise.all to avoid unhandled rejections.
- Add retry() for relays stuck in "failed" state.
- Add removePreference() to prevent unbounded preference growth.
- Add normalizeUrl option for custom URL normalization — preferences and
session rejections now consistently normalized via normalizeForKey().
- Wire Grimoire's normalizeRelayURL as the normalizer in relay-auth.ts.
- Update README with new methods, normalizeUrl option, retry lifecycle.
- 123 package tests passing.
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
* chore: prepare relay-auth-manager for npm publishing
- Point exports/main/types to dist/ for correct npm resolution
- Add tsconfig.build.json for emitting ESM JS + declarations
- Add build/clean/prepublishOnly scripts
- Add LICENSE, description, keywords, author, files field
- Add Vite resolve alias + tsconfig paths for workspace dev
(resolves source directly, no pre-build needed for dev)
- Fix TypeScript strict errors in test file
- Clean npm pack output: dist/, README.md, LICENSE only
https://claude.ai/code/session_01XqrjeQVtJKw9uC1XAw6rqd
---------
Co-authored-by: Claude <noreply@anthropic.com>
Kind 11 events are thread roots (NIP-7D) with an optional title tag.
Previously they reused the Kind1Renderer (short text note). Now they
get a dedicated ThreadRenderer that shows the title as a clickable
heading (via ClickableEventTitle) when present, followed by the
content rendered with RichText.
https://claude.ai/code/session_01SQLhrJfeQHceRAS1MjYHrN
Co-authored-by: Claude <noreply@anthropic.com>
* feat(kind-1111): show root scope and parent context per NIP-22
The Kind 1111 renderer previously only showed the immediate parent reply,
missing the root scope that defines what a comment thread is about. Now
shows both the root item (blog post, file, URL, podcast, etc.) and the
parent reply (when replying to another comment), giving full threading
context.
- Add NIP-22 helper library using applesauce pointer helpers
(getEventPointerFromETag, getAddressPointerFromATag,
getProfilePointerFromPTag) for tag parsing
- Support external identifiers (I-tags) with NIP-73 type-specific icons
- Unified ScopeRow component for consistent inline display
- Only show parent reply line for nested comments (not top-level)
https://claude.ai/code/session_01Dxedi6VWdZG8nFpba211oR
* fix(kind-1111): unify scope row styling, fix redundant icons and link style
- Replace separate NostrEventCard/ExternalScopeCard with children-based
ScopeRow so root and reply rows look identical
- Remove redundant icons: root events show only KindBadge, replies show
only Reply arrow — no double icons
- External URLs now use the standard link style (text-accent + dotted
underline on hover) matching UrlList, with ExternalLink icon
- Children are direct flex items for proper gap spacing
https://claude.ai/code/session_01Dxedi6VWdZG8nFpba211oR
* fix(kind-1111): match icon sizes and make external URLs clickable
- Set KindBadge iconClassname to size-3 so it matches Reply and
ExternalLink icons (was size-4 by default)
- Use the I-tag value itself as href when it's a URL and no hint is
provided — most web I-tags only have the URL in value, not in hint
https://claude.ai/code/session_01Dxedi6VWdZG8nFpba211oR
* fix(kind-1111): use muted style for external link rows
Match the muted-foreground + dotted underline style used by other
scope rows instead of accent color.
https://claude.ai/code/session_01Dxedi6VWdZG8nFpba211oR
---------
Co-authored-by: Claude <noreply@anthropic.com>
StatusIndicator was stuck showing a loading spinner indefinitely when no
status events existed, because the useTimeline observable never completes
for live Nostr subscriptions. Default to showing "Open" immediately and
update reactively when status events arrive.
https://claude.ai/code/session_01UAjKegpi8uWyLdjgRpNeEJ
Co-authored-by: Claude <noreply@anthropic.com>
* fix: disable smooth scroll on initial chat load
The chat viewer was using smooth scrolling for all followOutput events,
including when first loading the message list. This caused a slow,
animated scroll towards the latest messages on initial load.
Fix by tracking whether initial render is complete and only enabling
smooth scrolling for subsequent followOutput events (new incoming
messages). The ref is reset when switching between conversations.
https://claude.ai/code/session_0174r1Ddh5e2RuhHf2ZrFiNc
* fix: use instant scroll instead of disabling scroll on initial load
The previous fix returned `false` which disabled scrolling entirely,
causing incorrect scroll position. Changed to return "auto" which
scrolls instantly (no animation) while still positioning correctly.
https://claude.ai/code/session_0174r1Ddh5e2RuhHf2ZrFiNc
* fix: buffer NIP-29 messages until EOSE to prevent partial renders
The loadMessages observable was emitting on every event as they streamed
in before EOSE, causing multiple re-renders with partial message lists.
This resulted in incorrect scroll positions during initial chat load.
Now uses combineLatest with a BehaviorSubject to track EOSE state and
only emits the message list after the initial batch is fully loaded.
New messages after EOSE continue to trigger immediate updates.
https://claude.ai/code/session_0174r1Ddh5e2RuhHf2ZrFiNc
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix(zap): only send comment to LNURL callback if server accepts it
The comment in the zap request event (kind 9734 content) is always
included as that's part of the Nostr protocol. However, the LNURL
callback `comment` parameter should only be sent if the server's
`commentAllowed` field is > 0.
Previously, the comment was always sent to the LNURL callback
regardless of the server's comment support, which could cause issues
with servers that don't accept comments.
https://claude.ai/code/session_01KTcAyKHVaqg4QKKXQxUzum
* fix(zap): silently skip comment in LNURL callback if too long
Instead of throwing an error when the comment exceeds the server's
commentAllowed limit, simply don't include it in the LNURL callback.
The comment is still preserved in the zap request event (kind 9734).
https://claude.ai/code/session_01KTcAyKHVaqg4QKKXQxUzum
---------
Co-authored-by: Claude <noreply@anthropic.com>
The --type flag for blossom blob command was being parsed correctly but
the mediaType and blobUrl props were not forwarded from WindowRenderer
to BlossomViewer, causing the preview to always show "preview not available".
https://claude.ai/code/session_018edX9kUcEudJzwuFCGh1xf
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add custom media renderer support to RichText
Add renderMedia prop to RichText component that allows overriding
how images, videos, and audio are rendered across the entire
RichText subtree (including Link and Gallery components).
The custom renderer receives:
- url: the media URL
- type: "image" | "video" | "audio"
- imeta: optional NIP-92 metadata (dimensions, blurhash, alt, etc.)
This enables chat-specific media rendering with compact thumbnails,
lightboxes, or any custom presentation.
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: add ChatMediaRenderer for compact inline media display
Custom media renderer for chat that shows:
- Media type icon (image/video/audio)
- Filename (extracted from URL or imeta alt)
- File size (from imeta if available)
- Blossom link button (opens blob viewer for blossom URLs)
Usage:
<RichText event={message} renderMedia={ChatMediaRenderer} />
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: use ChatMediaRenderer in chat messages
- Updated ChatMediaRenderer to use getHashFromURL from blossom-client-sdk
- Integrated ChatMediaRenderer into ChatViewer for message content
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* style: make ChatMediaRenderer inline with subtle dotted border
Use a subtle dotted bottom border instead of background/padding
to better integrate with surrounding text flow.
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: improve ChatMediaRenderer UX
- Full dotted border with rounded corners (was bottom-only)
- Increased gap between elements
- Images/videos open in MediaDialog zoom viewer on click
- Audio still opens in new tab
- Better extension extraction for display
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: improve blossom integration in ChatMediaRenderer
- Use HardDrive icon instead of Flower2 (consistent with rest of app)
- Add commandString for Edit functionality in window toolbar
- Pass blobUrl with extension to BlossomViewer for correct media preview
- Extended BlossomViewer.BlobDetailView to accept blobUrl prop
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* refactor: simplify ChatMediaRenderer styling
- All icons now size-3
- Use dotted underline only (cleaner inline appearance)
- All media types open in new tab on click
- Removed MediaDialog dependency
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* fix: inherit custom media renderer in nested RichText components
Previously, nested RichText components (like those in QuotedEvent/KindRenderer)
would always reset the media renderer context to null because the provider
used `renderMedia ?? null`. This caused embedded events in chat to use
the default media renderer instead of ChatMediaRenderer.
Now RichText inherits the parent media renderer when no explicit renderMedia
prop is passed, allowing custom renderers to work throughout the entire
rich text subtree including quoted events.
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: improve ChatMediaRenderer with expandable inline media
- More compact representation: "icon truncated-hash blossom"
- Click filename to expand and show actual media inline (image/video/audio)
- Tooltip shows full filename and file size on hover
- Audio support with inline audio player when expanded
- Fixed BlossomViewer to detect media type from URL extension when
mimeType is not available from blob descriptor
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* feat: improve ChatMediaRenderer with better UX
- Click to expand shows MediaEmbed (not collapsible once expanded)
- Tooltip only shows when imeta is present, displays: alt, mime type,
dimensions, size, duration
- More compact representation: [icon] truncated-hash [blossom]
- Pass mediaType to BlossomViewer for correct preview rendering
- BlossomViewer now accepts mediaType hint for preview type detection
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* fix: blossom blob command now parses --type flag
- Added mediaType and blobUrl fields to BlossomCommandResult
- Blob subcommand now parses --type image|video|audio flag
- Fixed server URL overflow in blob detail view with truncation
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
* refactor: add global loadMedia setting with CompactMediaRenderer
- Add `loadMedia` setting to Appearance section (enabled by default)
- Create CompactMediaRenderer in src/components/nostr/ (renamed from ChatMediaRenderer)
- Link.tsx and Gallery.tsx now check the setting and use CompactMediaRenderer when disabled
- Tooltip format improved: "Field <value>" with field name and value side by side
- Shows: Hash, Size, Dimensions, Type, Duration, Alt
- Remove renderMedia prop from ChatViewer (now automatic based on setting)
- Delete old ChatMediaRenderer.tsx
This makes media rendering a site-wide setting rather than chat-specific.
https://claude.ai/code/session_01AeeN5d5EcVLGjZbGueZxaD
---------
Co-authored-by: Claude <noreply@anthropic.com>
* refactor: remove unused compactModeKinds from app state
The compactModeKinds feature was partially implemented but never used:
- Settings dialog allowed configuration but the value was never consumed
- REQ viewer uses --view flag for compact mode, not this state value
Removed:
- compactModeKinds from GrimoireState type and initial state
- setCompactModeKinds logic function and state hook callback
- Compact Events section from SettingsDialog (now shows placeholder)
- compactModeKinds from AppearanceSettings in settings service
- Migration now strips compactModeKinds if present instead of adding it
https://claude.ai/code/session_01DiWUxiS5BAzU9mrKvCUuMW
* chore: delete unused SettingsDialog component
The SettingsDialog was imported but never used - the Settings menu
item opens a window via addWindow("settings", ...) instead.
https://claude.ai/code/session_01DiWUxiS5BAzU9mrKvCUuMW
* refactor: simplify settings service to only used settings
Removed unused settings that were defined but never consumed:
- RelaySettings (fallbackRelays, discoveryRelays, outbox*, etc.)
- PrivacySettings (shareReadReceipts, blurWalletBalances, etc.)
- DatabaseSettings (maxEventsCached, autoCleanupDays, etc.)
- NotificationSettings (enabled, notifyOnMention, etc.)
- DeveloperSettings (debugMode, showEventIds, logLevel, etc.)
- Most of AppearanceSettings (theme, fontSizeMultiplier, etc.)
- Most of PostSettings (defaultRelayMode, customPostRelays)
Only kept settings that are actually used:
- post.includeClientTag
- appearance.showClientTags
Also simplified useSettings hook to match.
https://claude.ai/code/session_01DiWUxiS5BAzU9mrKvCUuMW
---------
Co-authored-by: Claude <noreply@anthropic.com>
* docs: add plan for repository tree visualization feature
Comprehensive plan covering:
- git-natural-api library analysis and API documentation
- useGitTree/useGitBlob hooks for fetching git data
- FileTreeView component using Radix Collapsible
- Shiki migration with on-demand language loading
- Multi-server fallback for redundant clone URLs
- Dexie caching for offline access
* docs: add comprehensive Shiki migration plan
Detailed plan for migrating from Prism.js to Shiki with lazy loading:
- Analysis of all 8 components using SyntaxHighlight
- Shiki service with singleton highlighter and on-demand language loading
- Custom Grimoire dark theme matching current Prism styles
- Language alias mapping for 50+ extensions
- React hook for async highlighting with loading states
- CSS theme preserving minimalistic dark aesthetics
- Migration steps with rollback plan
* feat: migrate syntax highlighting from Prism.js to Shiki
Replace Prism.js with Shiki for syntax highlighting with several key improvements:
- Lazy loading: Languages loaded on-demand via dynamic imports instead of bundling all upfront
- Broader language support: 200+ TextMate grammars vs 11 statically imported
- Singleton highlighter: Core languages (JS, TS, JSON, diff, bash) preloaded, others loaded on first use
New files:
- src/lib/shiki.ts: Shiki service with highlightCode(), normalizeLanguage(), language aliases
- src/hooks/useHighlightedCode.ts: React hook for async highlighting with loading states
- src/styles/shiki-theme.css: Grimoire dark theme matching previous minimalistic style
Updated components:
- SyntaxHighlight: Now uses Shiki with graceful loading/error states
- CodeSnippetRenderer/DetailRenderer: Simplified, removed manual language mapping
- MarkdownContent: Removed type casts, any language now supported
Removed:
- prismjs and @types/prismjs dependencies
- src/styles/prism-theme.css
* feat: add repository file tree visualization
Add file tree explorer to the Repository detail renderer (kind 30617)
using @fiatjaf/git-natural-api for fetching git trees via HTTP.
New files:
- src/lib/git-types.ts: TypeScript types for DirectoryTree, SelectedFile, etc.
- src/hooks/useGitTree.ts: Hook to fetch git repository tree from clone URLs
- Tries multiple clone URLs in sequence
- Uses getDirectoryTreeAt with filter capability when available
- Falls back to shallowCloneRepositoryAt otherwise
- src/hooks/useGitBlob.ts: Hook to fetch individual file content by hash
- Detects binary files
- Returns both raw Uint8Array and decoded text
- src/components/ui/FileTreeView.tsx: Recursive tree view component
- Collapsible directories with chevron icons
- File icons based on extension (code, json, text, image, etc.)
- Alphabetical sorting with directories first
- src/components/nostr/kinds/RepositoryFilesSection.tsx: Main integration
- Side-by-side tree and file preview layout
- Syntax-highlighted file content using existing SyntaxHighlight
- Binary file detection with appropriate UI
- Loading/error states
Modified:
- RepositoryDetailRenderer.tsx: Added RepositoryFilesSection below relays
Dependencies:
- Added @fiatjaf/git-natural-api from JSR
* fix: improve repository tree visualization UX
- Collapse directories by default in file tree
- Hide files section on tree loading error
- Add code-like skeleton loader with file header
- Fix syntax highlight size jump between loading/loaded states
- Replace purple accent with grayscale theme
- Preload Rust and Markdown languages for reliable highlighting
* refactor: improve git tree and syntax highlighting
- Remove shallow clone fallback from useGitTree, only use no-blobs fetch
Servers without filter capability are skipped instead of downloading blobs
- Add light theme support for Shiki syntax highlighting
Theme is automatically selected based on current color scheme
* fix: improve dark theme contrast for syntax highlighting
* fix: address code review issues
- useGitTree: use useStableArray for cloneUrls to fix dependency tracking
- useGitTree/useGitBlob: add isMounted checks to prevent state updates after unmount
- RepositoryFilesSection: remove unnecessary useMemo for language
- FileTreeView: use path instead of hash for React keys
- shiki: track failed languages to avoid repeated console warnings
* fix: improve dark theme contrast for syntax highlighting
- Add CSS variables for syntax highlighting instead of hardcoded colors
- Add --syntax-constant and --syntax-tag variables to light and dark themes
- Use high contrast colors for dark mode (bright green strings, purple keywords)
- Simplify Shiki transformer to output CSS classes instead of inline styles
- Remove unused parameters from transformer callback
* fix: restore syntax highlighting colors
Revert the CSS class-based approach which was failing to classify tokens.
Instead, keep Shiki's inline styles from the theme and only remove
backgrounds to let CSS handle those. The theme colors now provide
syntax highlighting directly.
* feat: add copy button and CSS variable-based syntax highlighting
- Add copy button next to file name in file viewer header (icon-only)
- Use Shiki's createCssVariablesTheme for proper theme integration
- Map Shiki CSS variables to our theme system variables
- Syntax highlighting now works correctly across all themes (light/dark)
* refactor: create IconCopyButton component and use CopyCheck consistently
- Add IconCopyButton component for reusable icon-only copy buttons
- Refactor RepositoryFilesSection to use IconCopyButton
- Replace Check with CopyCheck in ChatMessageContextMenu
- Replace Check with CopyCheck in BaseEventRenderer
- Use text-success instead of text-green-500 for consistency
* fix: add HTML, CSS, TOML to core languages and expand token mappings
- Add html, css, toml to CORE_LANGUAGES for eager loading
- Add variableDefaults to cssVarsTheme for proper initialization
- Expand shiki-theme.css with more token type mappings:
- HTML/XML: tag, attribute, attr-value
- CSS: selector, property
- Additional: variable, operator, number, boolean, regex, etc.
* fix: improve diff line spacing with flex layout
- Use flex-col with gap-0 on code element for tight line packing
- Reduce line-height from 1.5 to 1.4 for tighter spacing
- Add .line display:block with min-height for consistent sizing
- Simplify diff background styling (remove negative margin hack)
* fix: improve code block line spacing and wrap long lines
- Increase line-height from 1.4 to 1.5 for better readability
- Use pre-wrap instead of pre to allow long line wrapping
- Add overflow-wrap: break-word to break long URLs/strings
* chore: remove planning docs
* chore: update @fiatjaf/git-natural-api to 0.2.3
* fix: make code blocks horizontally scrollable with full-width diff backgrounds
- Use white-space: pre for horizontal scrolling instead of wrapping
- Add width: fit-content and min-width: 100% to code element
- Ensure diff line backgrounds extend full width when scrolling
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add "+ new tab" option to move window menu
Adds a "+ New tab" option at the top of the "Move to tab" submenu in the
window toolbar. This allows users to create a new tab and move the current
window to it in a single action, streamlining the workflow.
Changes:
- Add moveWindowToNewWorkspace function in logic.ts
- Expose moveWindowToNewWorkspace through useGrimoire hook
- Always show "Move to tab" menu (not just when multiple tabs exist)
- Add "+ New tab" option with Plus icon at top of submenu
https://claude.ai/code/session_01Hy2vYBooPyrF7ZJCodcCav
* refactor: simplify new tab menu item copy
- Change menu text from "+ New tab" to "New" (icon already shows +)
- Simplify toast to just "Moved to new tab"
https://claude.ai/code/session_01Hy2vYBooPyrF7ZJCodcCav
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix(nwc): improve connection reliability and add health tracking
- Add connection status observable (disconnected/connecting/connected/error)
- Validate wallet connection on restore using support$ observable with 10s timeout
- Add notification subscription error recovery with exponential backoff (5 retries)
- Add retry logic for balance refresh (3 retries with backoff)
- Use library's support$ observable for wallet capabilities (cached by applesauce)
- Replace manual getInfo() calls with reactive support$ subscription
- Add visual connection status indicator in WalletViewer header
- Add reconnect button when connection is in error state
- Store network info in cached connection for display
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* feat(wallet): add copy NWC connection string button to header
Adds a copy button (Copy/Check icons) in the wallet header before the
refresh button that copies the NWC connection string to clipboard for
easy sharing or backup.
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* fix(wallet): use CopyCheck icon and fix transaction loading
- Change Check to CopyCheck icon for copy NWC string button
- Add walletMethods computed value that combines support$ observable
with cached info fallback from initial connection
- Fix transaction history not loading because support$ waits for
kind 13194 events which many NWC wallets don't publish
- The cached info from getInfo() RPC call is now used as fallback
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* refactor(nwc): simplify with derived state from observables
Production-ready refactor of NWC implementation:
nwc.ts:
- Add wallet$ observable for reactive wallet instance access
- Remove redundant subscribeToSupport() - only needed for validation
- Cleaner code organization with clear sections
useWallet.ts:
- All state derived from observables (no useState for wallet)
- Move walletMethods computation to hook (reusable)
- isConnected derived from connectionStatus
- Simplified from 240 to 170 lines
WalletViewer.tsx:
- Use walletMethods from hook instead of local useMemo
- Simpler connection state tracking via connectionStatus
- Remove redundant wallet variable from destructuring
- No color change on copy NWC string (per feedback)
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* refactor(wallet): use useCopy hook for clipboard operations
Replace manual clipboard state management with useCopy hook:
- copyInvoice/invoiceCopied for generated invoice
- copyRawTx/rawTxCopied for transaction JSON
- copyNwc/nwcCopied for NWC connection string
Benefits:
- Cleaner code (removed manual setTimeout calls)
- Automatic timeout cleanup on unmount
- Consistent copy behavior across all clipboard operations
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* feat(wallet): implement lazy-loaded transactions observable
- Add shared wallet types (Transaction, TransactionsState) in src/types/wallet.ts
- Add transactionsState$ observable to NWC service for shared tx state
- Implement loadTransactions, loadMoreTransactions, and retryLoadTransactions
- Auto-refresh transactions on payment notifications
- Simplify WalletViewer to use observable state instead of local state
- Remove manual transaction loading logic from component
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* fix(wallet): update balance observable on initial connect
- Call refreshBalance() in createWalletFromURI to fetch initial balance
- Update balance$ directly when ConnectWalletDialog gets balance
- Fixes issue where WalletViewer showed "-" after connecting while
user menu showed correct balance (different data sources)
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* refactor(wallet): use single data source for balance across UI
Remove fallback to nwcConnection.balance in user-menu - now both
WalletViewer and user-menu use balance$ observable as the single
source of truth for wallet balance.
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* fix(wallet): address code review issues and simplify user menu
- Fix memory leak: track retry timeout and clear on disconnect
- Add explicit WalletSupport type for support observable
- Add comments explaining balance refresh error handling behavior
- Add comment about restoreWallet not being awaited intentionally
- User menu now uses connectionStatus observable (shows connecting/error states)
- Remove wallet name display from user menu (simplifies UI)
- Remove unused walletServiceProfile hook and getWalletName function
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
* refactor(wallet): extract WalletConnectionStatus component
- Create reusable WalletConnectionStatus component for connection indicator
- Remove rounded borders from indicator (now square)
- Export getConnectionStatusColor helper for custom usage
- Use component in both user-menu and WalletViewer
- Supports size (sm/md), showLabel, and className props
https://claude.ai/code/session_01CnJgjFMvZHZWs2ujAiWAiQ
---------
Co-authored-by: Claude <noreply@anthropic.com>
When images are turned off in the RichText options, galleries now show
a single [gallery] placeholder instead of multiple [image] placeholders.
This provides a cleaner UI for users who have disabled image loading.
https://claude.ai/code/session_01LAhYP5iRQskJC4XWi6MHvf
Co-authored-by: Claude <noreply@anthropic.com>
* fix: hide tabbar scrollbar by setting width/height to 0
The no-scrollbar utility's display:none wasn't fully overriding the
global scrollbar styles that set width/height to 8px. Adding explicit
width:0 and height:0 ensures the scrollbar is completely hidden in
WebKit browsers.
https://claude.ai/code/session_018RiPf74GNf2oWcoYNRoZyx
* fix: use !important to override global scrollbar styles
The global * selector's scrollbar-width: thin was overriding the
no-scrollbar utility due to CSS cascade order. Adding !important
ensures the utility always wins.
https://claude.ai/code/session_018RiPf74GNf2oWcoYNRoZyx
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: build proper q-tag with relay hint and author pubkey for replies
When sending replies in NIP-29 and NIP-C7 adapters, now build the full
q-tag format per NIP-C7 spec: ["q", eventId, relayUrl, pubkey]
Previously only the event ID was included, making it harder for clients
to fetch the referenced event. Now:
- NIP-29: includes group relay URL and author pubkey
- NIP-C7: includes seen relay hint and author pubkey
https://claude.ai/code/session_01Jy51Ayk57fzaFuuFFm1j1K
* chore: remove unused NIP-C7 adapter
The NIP-C7 adapter was already disabled/commented out everywhere.
Removing the file to reduce dead code.
https://claude.ai/code/session_01Jy51Ayk57fzaFuuFFm1j1K
* chore: remove NIP-C7 references from docs and code
- Remove nip-c7 from ChatProtocol type
- Remove commented NIP-C7 adapter imports and switch cases
- Update comments to reference NIP-29 instead of NIP-C7
- Update kind 9 renderer docs to reference NIP-29
- Clean up chat-parser docs and error messages
https://claude.ai/code/session_01Jy51Ayk57fzaFuuFFm1j1K
---------
Co-authored-by: Claude <noreply@anthropic.com>
- Add useIsMobile hook for viewport detection
- TabBar: larger height (48px), disable reorder on mobile, hide workspace numbers
- Header buttons: larger touch targets for SpellbookDropdown, UserMenu, LayoutControls
- Window toolbar: larger buttons (40px) on mobile
- Mosaic dividers: wider (12px) on mobile for easier dragging
- CommandLauncher: larger items, footer text, hide kbd hints on mobile
- Editor suggestions: responsive widths, min-height 44px touch targets
- EventFooter: larger kind/relay buttons on mobile
- CodeCopyButton: larger padding and icon on mobile
- MembersDropdown: larger trigger and list items on mobile
All changes use mobile-first Tailwind (base styles for mobile, md: for desktop)
to meet Apple HIG 44px minimum touch target recommendation.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* feat: add -f (follow) option to req command
Add tail -f style auto-refresh behavior to the req command. When enabled,
new events are automatically displayed instead of being buffered behind
a "X new events" button.
The SVG path extended slightly beyond the viewBox (bezier control points
reached x=121.464 while viewBox ended at x=121), while the left edge was
flush at x=0. This caused uneven spacing.
Changed viewBox from "0 0 121 160" to "-0.5 0 122 160" to add equal
0.5px margins on both sides, properly centering the logo content.
https://claude.ai/code/session_019PGCQHRovoNE81udohhU3R
Co-authored-by: Claude <noreply@anthropic.com>
* fix: filter invalid relay URLs from event tags
Add validation to prevent invalid URLs from being used as relay hints.
The issue occurred when "r" tags containing non-relay URLs (like
https://(strangelove@basspistol.org/) were being extracted and used
as relay connection targets.
Changes:
- Add isValidRelayURL() helper to validate relay URLs (must have ws://
or wss:// protocol and valid URL structure)
- Update extractRelayContext() in loaders.ts to filter r-tags, e-tag
relay hints, and a-tag relay hints using the new validator
- Add comprehensive tests for isValidRelayURL()
https://claude.ai/code/session_01Ca2fKD2r4wHKRD8rcRohj9
* refactor: use applesauce isSafeRelayURL for relay URL validation
Refactor relay URL validation to use applesauce's isSafeRelayURL helper
which provides a fast regex-based check for valid websocket URLs.
Changes:
- Update isValidRelayURL in relay-url.ts to use isSafeRelayURL as fast
path, with URL constructor fallback for IP addresses
- Re-export isSafeRelayURL from relay-url.ts for convenience
- Update loaders.ts to use isSafeRelayURL directly from applesauce
- Add relay URL validation to:
- nostr-utils.ts: getEventPointerFromQTag (q-tag relay hints)
- zapstore-helpers.ts: getAppReferences (a-tag relay hints)
- nip89-helpers.ts: getHandlerReferences (a-tag relay hints)
- PublicChatsRenderer.tsx: extractGroups (group relay URLs)
This ensures consistent validation across all relay URL extraction points
using applesauce's battle-tested validation.
https://claude.ai/code/session_01Ca2fKD2r4wHKRD8rcRohj9
* chore: remove unused isSafeRelayURL re-export
The re-export was added but all consumers import directly from
applesauce-core/helpers/relays instead.
https://claude.ai/code/session_01Ca2fKD2r4wHKRD8rcRohj9
---------
Co-authored-by: Claude <noreply@anthropic.com>
The client tag was being added twice to spells:
1. Unconditionally in encodeSpell() in spell-conversion.ts
2. Conditionally in publish-spell.ts based on user settings
Removed the unconditional addition in encodeSpell() so the client tag
is only added once by publish-spell.ts when the user setting is enabled.
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add Grimoire logo SVG and generate PWA assets
- Add logo.svg with the official Grimoire logo and gradient
- Create GrimoireLogo React component for use in the app
- Add scripts/generate-pwa-icons.mjs to generate all PWA icons from SVG
- Regenerate all favicon and PWA icons from the new logo
- Update mobile welcome screen to show the logo instead of text
* feat: use transparent backgrounds for PWA icons and add theme gradient option
- Update generate-pwa-icons.mjs to output PNGs with transparent backgrounds
- Add gradient prop to GrimoireLogo component ("original" or "theme")
- Theme gradient matches text-grimoire-gradient CSS (yellow -> orange -> purple -> cyan)
- Mobile welcome screen now uses theme gradient to match ASCII art
* feat: use original gradient for mobile welcome logo
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: pass source event to RichText in highlight feed preview
The source event preview in HighlightRenderer was only passing the
content string to RichText, which meant custom emoji tags from the
source event weren't processed. Now passes the source event with
the preview content to enable proper emoji and tag-based rendering.
* refactor: use CSS truncation for highlight source preview
- Pass sourceEvent directly for notes instead of extracting content
- Only create synthetic event with title for articles
- CSS line-clamp-1 and overflow-hidden handle truncation
- Media and event embeds remain disabled
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat(nip34): Add NIP-34 issue status renderers and locale-aware formatting
- Add IssueStatusRenderer for feed view (kinds 1630-1633: Open/Resolved/Closed/Draft)
- Add IssueStatusDetailRenderer for detail view with status badge and embedded issue
- Update IssueRenderer/IssueDetailRenderer to fetch and display current issue status
- Status validation respects issue author, repo owner, and maintainers
- Add status helper functions to nip34-helpers.ts (getStatusType, findCurrentStatus, etc.)
- Use parseReplaceableAddress from applesauce-core for coordinate parsing
- Expand formatTimestamp utility with 'long' and 'datetime' styles
- Fix locale-aware date formatting across all detail renderers
- Update CLAUDE.md with useLocale hook and formatTimestamp documentation
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* refactor(nip34): Use theme semantic colors for issue status
Replace hardcoded colors with theme semantic colors:
- Resolved/merged: accent (positive)
- Closed: destructive (negative)
- Draft: muted
- Open: neutral foreground
Also fixes import placement in nip34-helpers.ts.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Use repository relays instead of AGGREGATOR_RELAYS
Status events for issues are now fetched from the relays configured
in the repository definition, not from hardcoded aggregator relays.
This respects the relay hints provided by repository maintainers for
better decentralization and reliability.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* perf(nip34): Add memoization caching to helper functions
Use getOrComputeCachedValue from applesauce-core to cache computed
values on event objects. This prevents redundant computation when
helpers are called multiple times for the same event.
Also added documentation in CLAUDE.md about best practices for
writing helper libraries that compute data from Nostr events.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Add relay fallback chain for status event fetching
Status events now use a fallback chain for relay selection:
1. Repository configured relays (from "relays" tag)
2. Repo author's outbox relays (from kind:10002)
3. AGGREGATOR_RELAYS as final fallback
This ensures status events can be fetched even when repository
doesn't have relays configured.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* feat(nip34): Add status rendering to Patch and PR renderers
- PatchRenderer and PatchDetailRenderer now show merge/closed/draft status
- PullRequestRenderer and PullRequestDetailRenderer now show merge/closed/draft status
- Status events fetched from repository relays with author outbox fallback
- For patches and PRs, kind 1631 displays as "merged" instead of "resolved"
- Fixed destructive color contrast in dark theme (30.6% -> 50% lightness)
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* refactor(nip34): Extract StatusIndicator component, improve UI layout
- Create reusable StatusIndicator component for issues/patches/PRs
- Move status icon next to status text in feed renderers (not title)
- Place status badge below title in detail renderers
- Fix dark theme destructive color contrast (0 90% 65%)
- Remove duplicate getStatusIcon/getStatusColorClass functions
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Make status badge width fit content
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(theme): Improve destructive color contrast on dark theme
Increase lightness from 65% to 70% for better readability.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(theme): Use lighter coral red for destructive on dark theme
Changed to 0 75% 75% (~#E89090) for better contrast against #020817 background.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* docs: Fix applesauce helper documentation in CLAUDE.md
- Fix parseCoordinate -> parseReplaceableAddress (correct function name)
- Clarify getTagValue (applesauce) vs getTagValues (custom Grimoire)
- Add getOrComputeCachedValue to helpers list
- Improve code example with proper imports and patterns
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Render status event content as rich text
Use MarkdownContent component for status event content in
Issue, Patch, and PR detail renderers.
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Smaller status indicators, improve issue feed layout
- Use shared StatusIndicator in IssueStatusRenderer (smaller size)
- Render status event content as markdown
- Put status on its own line between title and repo in IssueRenderer
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
* fix(nip34): Use warning color for closed status instead of destructive
- Change closed status from red (destructive) to orange (warning)
- Improve dark theme status colors contrast (warning: 38 92% 60%)
- Less aggressive visual for closed issues/patches/PRs
https://claude.ai/code/session_01C6Lty4k9pKxdwnYUCcpzV2
---------
Co-authored-by: Claude <noreply@anthropic.com>
* Add NIP-56 Report renderer (kind 1984)
- Add nip56-helpers.ts with report parsing and type definitions
- Add ReportRenderer for displaying report events in feeds
- Support profile, event, and blob report targets
- Display report type with color-coded badges and icons
- Show embedded reported event when available
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
* refactor(nip56): apply applesauce caching and neutral styling
- Use getOrComputeCachedValue for report parsing (applesauce pattern)
- Rename parseReport to getReportInfo for consistency
- Use muted/neutral colors for all report type icons and badges
- Use QuotedEvent component for embedding reported events
- Remove unnecessary useMemo (helper caches internally)
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
* refactor(nip56): use collapsed quote and cleaner copy
- Use "Reported <username> for <reason>" format
- Remove redundant "Event by:" line for event reports
- Use depth=2 for QuotedEvent to show collapsed by default
- Content may be disturbing, user can expand on demand
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
* feat(nip56): hide preview and clickable header
- Add hidePreview prop to QuotedEvent for sensitive content
- Hide text preview when collapsed, show "Click to reveal content"
- Make report header clickable to open report detail
- UserName stops propagation so clicking username opens profile
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
* style(nip56): use dotted underline hover, reduce spacing
- Remove background highlight on hover
- Use underline dotted with cursor crosshair (consistent with app)
- Reduce gap between header and quoted event
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
* refactor(nip56): use RichText for comment and applesauce helpers
- Render report comments using RichText like kind 1 notes
- Use getTagValue/getTagValues helpers instead of direct tag access
- Add explanatory comments where direct tag access is still required
https://claude.ai/code/session_012ux81GyM8iZ1GLnKHC7esJ
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat(nip88): add poll event renderers
Implement NIP-88 poll events support with:
- PollRenderer: Feed view for kind 1068 polls showing question, options, type
- PollDetailRenderer: Detail view with live vote counts and percentages
- PollResponseRenderer: Feed view for kind 1018 showing voted options
- nip88-helpers: Utilities for parsing poll data and counting votes
* fix(nip88): use RelayLink component and differentiate poll type icons
- Use ListCheck icon for single choice, ListChecks for multi choice
- Replace relay text spans with clickable RelayLink components
- Shorten "Vote on these relays" to "Relays"
* refactor(nip88): production readiness improvements
- Add symbol-based caching to all helper functions using getOrComputeCachedValue
- Use QuotedEvent component for embedded polls in PollResponseRenderer
- Simplify PollResponseRenderer by leveraging QuotedEvent's loading states
- Add clear documentation about what can/cannot be cached
* fix(nip88): restore option label resolution in PollResponseRenderer
---------
Co-authored-by: Claude <noreply@anthropic.com>
Add a search input to KindsViewer matching the style from NipsViewer.
Users can now filter kinds by number, name, or description. Supports
autofocus on mount, clear button, and Escape to clear.
Co-authored-by: Claude <noreply@anthropic.com>
The chat input now grows as you type, from 1 line up to approximately
3 lines before showing a scrollbar. This improves UX when composing
longer messages by providing better visibility of the content.
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add profile metadata fallback for NIP-29 groups
When a NIP-29 group ID is a valid pubkey and the relay doesn't support
NIP-29 (no kind 39000 metadata), fall back to using the pubkey's profile
metadata (kind 0) for group name, description, and icon.
This allows users to create simple group chats using their pubkey as the
group identifier on relays that don't have full NIP-29 support.
Changes:
- Add isValidPubkey() helper to validate 64-char hex strings
- Modify resolveConversation() to fetch profile when metadata is missing
- Add comprehensive tests for pubkey validation and parsing
- Prefer NIP-29 metadata over profile fallback when available
Tests: 20 NIP-29 adapter tests passing, 1037 total tests passing
Build: Successful
* refactor: extract group metadata resolution into shared helper
Refactored profile fallback logic into a reusable helper that both
NIP-29 adapter and GroupListViewer can use. This fixes the issue where
GroupListViewer wasn't benefiting from the profile metadata fallback.
Changes:
- Created shared `group-metadata-helpers.ts` with:
- `isValidPubkey()` - validates 64-character hex strings
- `resolveGroupMetadata()` - unified metadata resolution with fallback
- `ResolvedGroupMetadata` type with source tracking
- Updated NIP-29 adapter to use shared helper (DRY)
- Updated GroupListViewer to resolve metadata with profile fallback
- Added resolvedMetadata to GroupInfo interface
- Added useEffect to resolve metadata for all groups
- Updated GroupListItem to use resolved metadata
Priority:
1. NIP-29 metadata (kind 39000) if available
2. Profile metadata (kind 0) if groupId is a valid pubkey
3. Fallback to groupId as name
Tests: All 1037 tests passing
Build: Successful
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat(nip-66): add relay discovery and monitor announcement renderers
Implements NIP-66 support to display relay health metrics and monitoring
information. Users can now view relay performance data (RTT, network type,
supported NIPs) and monitor announcements to make informed decisions about
relay selection and reliability.
Includes 58 comprehensive tests for all helper functions and event parsing.
* refactor(nip-66): improve UI with Label, NIPBadge, and clickable titles
Enhance NIP-66 renderers with better UI components:
- Use NIPBadge component for clickable NIP numbers
- Replace section headers with Label component for consistency
- Add ClickableEventTitle to monitor announcements
- Improve requirement icons with CheckCircle/XCircle for clarity
- Add proper icons throughout for better visual hierarchy
* refactor(nip-66): use Hammer icon for PoW requirements
Replace Zap (lightning bolt) icon with Hammer icon for proof-of-work
indicators to better represent the mining/work metaphor. Updates both
feed and detail renderers for relay discovery events.
* refactor(nip-66): improve feed UI with clickable titles and simplified layout
- Add ClickableEventTitle to relay discovery feed items for opening detail view
- Remove "Monitoring" label from relay monitor feed items for cleaner layout
- Remove unused imports (RelayLink, Label, Activity) from feed renderers
- Maintain existing Label and NIPBadge usage in detail renderers
* refactor(nip-66): add Label component for check types in monitor feed
Add "Check Types" label to relay monitor feed renderer for better
visual hierarchy and consistency with detail renderer.
* refactor(nip-66): remove Check Types label from monitor feed
Remove label title to simplify monitor feed layout - check type badges
are displayed directly without a header for cleaner appearance.
* refactor(nip-66): use Label component for individual check types in monitor feed
Replace Badge components with Label components for check types to match
the design system and provide better visual consistency.
* refactor(nip-66): rename components to human-readable names
Rename NIP-66 component exports to match established naming convention:
- Kind10166Renderer → MonitorAnnouncementRenderer
- Kind10166DetailRenderer → MonitorAnnouncementDetailRenderer
- Kind30166Renderer → RelayDiscoveryRenderer
- Kind30166DetailRenderer → RelayDiscoveryDetailRenderer
This follows the pattern used elsewhere (e.g., LiveActivityRenderer vs Kind30311Renderer) to make code more readable without memorizing kind numbers.
* refactor(nip-66): extract relay kinds display into reusable component
Create RelayKindsDisplay component to show accepted/rejected kinds in a
consistent format across detail views. Used in RelayDiscoveryDetailRenderer
to reduce code duplication and improve maintainability.
* refactor(nip-66): extract supported NIPs display into reusable component
Create RelaySupportedNips component to show relay-supported NIPs in a
consistent format. Used in RelayDiscoveryDetailRenderer to reduce code
duplication and improve maintainability.
* refactor(nip-66): add icon to supported NIPs component for consistent styling
Add FileText icon to RelaySupportedNips Label to match the visual
hierarchy pattern used in other relay detail sections (Performance
Metrics, Characteristics, Requirements, etc.).
* refactor(nip-66): use nicer NIP rendering from RelayViewer in shared component
Update RelaySupportedNips component to match RelayViewer's nicer styling:
- Show NIP names alongside numbers (showName=true) for better readability
- Use gap-2 for better spacing
- Use h3 title styling instead of Label with icon
- Make component reusable with optional title customization
- Use in both RelayViewer and RelayDiscoveryDetailRenderer
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: parse NIP-29 q-tags with relay hints for embedded event resolution
The issue was that q-tag relay hints were being discarded when parsing
chat messages. When a message quoted another event, only the event ID
was extracted from the q-tag, ignoring the relay URL hint at tag[2].
Changes:
- Add getEventPointerFromQTag and getQuotePointer helpers to nostr-utils
- Update Message.replyTo type from string to EventPointer | AddressPointer
- Update all chat adapters (NIP-29, NIP-10, NIP-53, NIP-C7) to parse
full pointers with relay hints
- Update loadReplyMessage signature to accept EventPointer with relays
- Update ReplyPreview to pass full pointers to event loading
- Update ChatView and ChatViewer to use new pointer-based q-tag parsing
This ensures embedded events (quotes/replies) are fetched using the
relay hint from the q-tag when the event is not found in the local store.
* fix: pass full EventPointer with relay hints through embed chain
The previous commit fixed q-tag parsing in chat adapters, but the
RichText/Mention chain was also discarding relay hints from nevent.
EventEmbed was only extracting `pointer.id` and passing it as a string
to QuotedEvent, losing the relay hints. Same issue in EmbeddedEvent.
Changes:
- Update QuotedEvent props: eventPointer instead of eventId string
- Update EmbeddedEvent props: eventPointer instead of eventId string
- Update EventEmbed to pass full pointer to QuotedEvent
- Update MarkdownContent to pass full pointers for note/nevent
- Update EventRefList to pass full pointer instead of just ID
- Update HighlightDetailRenderer to pass full eventPointer
- Update RepostRenderer to extract e-tag as EventPointer with hints
Now nevent mentions in content like nostr:nevent1... correctly use
the relay hints from the bech32 encoding when fetching the event.
* fix: use EventPointer for repost replyTo in NIP-10 adapter
Apply the same relay hints fix to the repostToMessage function that was
added in a recent main commit.
* refactor: use applesauce helpers for relay operations in chat adapters
- Use mergeRelaySets for relay deduplication and normalization
- Use getOutboxes helper instead of manual relay list parsing
- Simplify getThreadRelays in NIP-10 adapter
- Simplify loadReplyMessage in NIP-10, NIP-29, and NIP-53 adapters
* refactor: use mergeRelaySets in relay-selection service
- Simplify selectRelaysForInteraction using mergeRelaySets for priority-based relay combination
- Use mergeRelaySets for unique relay extraction in selectRelaysForFilter
- Reduces manual Set operations and gains automatic normalization
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add -i/--id flag for direct event ID filtering in REQ command
Add a new -i/--id flag for direct event lookup via filter.ids, and clarify
-e flag behavior for tag-based filtering (#e/#a tags).
Changes:
- Add -i/--id flag: accepts note1, nevent, or hex event IDs for direct lookup
- Clarify -e flag: now always routes to #e/#a tags (including nevent)
- Update man page with new flag documentation and examples
- Add comprehensive tests for the new -i/--id flag
This aligns with nak's behavior where -i is for direct ID filtering and
-e is for tag-based event references.
* feat: support raw coordinate format (kind:pubkey:d) in -e flag
The -e flag now accepts raw a-tag coordinates like `30023:pubkey:article`
in addition to naddr bech32 encoding. Both route to #a tag filtering.
Examples:
- req -e 30023:abc123...:my-article # Raw coordinate
- req -e naddr1... # Bech32 encoded (same effect)
* feat: add event ID previews in REQ viewer query dropdown
When using -i/--id flag for direct event lookup, the query dropdown now
shows clickable event ID previews (truncated hex).
Click any ID to open the event detail view.
Works in both accordion (complex queries) and simple card views.
---------
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add repost system messages with grouping in chat
- Add kind 6 and 16 (reposts) to NIP-10 adapter filters
- Convert simple reposts (no content) to system messages
- Implement consecutive system message grouping
- Groups consecutive system messages with same action
- Format: "alice, bob and 3 others reposted"
- Works for all system messages (reposts, join, leave, etc.)
- Update scroll-to-message to handle grouped messages
- Ignore reposts with content (quotes) to keep it simple
System message grouping UX:
- 1 person: "alice reposted"
- 2 people: "alice and bob reposted"
- 3 people: "alice, bob and charlie reposted"
- 4+ people: "alice, bob and 3 others reposted"
* feat: show all reposts regardless of content
Remove content filtering for reposts - now all kind 6 and 16 events
are shown as system messages. Quote reposts (with content) will just
display as 'reposted' without showing the quote text, keeping the
chat interface clean and consistent.
* refactor: extract and test system message grouping logic
Extract grouping logic to separate module:
- Created src/lib/chat/group-system-messages.ts with:
- groupSystemMessages(): Groups consecutive system messages
- isGroupedSystemMessage(): Type guard with validation
- GroupedSystemMessage interface
- Updated ChatViewer to import from new module
- Improved type guard with additional validation:
- Check array lengths match (authors.length === messageIds.length)
- Ensure arrays are not empty
- Validate all field types
Added comprehensive test coverage (26 tests):
- Basic grouping behavior
- Edge cases (empty arrays, single messages)
- Mixed message types (user, zap, system)
- Timestamp preservation
- Large group handling (100+ items)
- Type guard validation
All tests pass (1006 total), build succeeds.
Production ready.
---------
Co-authored-by: Claude <noreply@anthropic.com>
When displaying a zap that targets another zap (kind 9735), the compact
preview was passing the inner zap receipt directly to RichText. Since a
zap receipt's content is empty (the user's message with emoji tags is in
the embedded zap request), custom emojis weren't rendering.
Now when the zapped event is a zap receipt, we extract its zap request
using getZapRequest() and use that for the preview, matching how the
full renderer handles this via recursive KindRenderer.
Co-authored-by: Claude <noreply@anthropic.com>
* fix: only match nostr entities at word boundaries in paste handler
Updates the paste handler regex to only match nostr bech32 entities
(npub, note, nevent, naddr, nprofile) when surrounded by whitespace or
at string boundaries. This prevents URLs containing nostr entities
(e.g., https://njump.me/npub1...) from being incorrectly converted
to mentions.
Uses a capture group (^|\s) instead of lookbehind assertion for
Safari compatibility (lookbehind only supported in Safari 16.4+).
* fix: disable pointer events on links in editor
Adds pointer-events: none to anchor tags within the ProseMirror editor
to prevent clicking on pasted URLs from navigating away. This allows
users to edit the text containing links rather than accidentally
triggering navigation.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Add isEditorReady() helper to check if editor.view.dom is mounted
before accessing editor commands. This prevents the TipTap error
"The editor view is not available" that occurred when PostViewer's
draft loading called editor methods before the view was fully mounted.
Co-authored-by: Claude <noreply@anthropic.com>
Removed the "Publishing..." text from the Publish button during posting,
keeping only the loading spinner icon for a cleaner UI.
Co-authored-by: Claude <noreply@anthropic.com>
* feat: add client tag support to all event creation
Implements a global settings system to control whether the Grimoire client tag
should be included in all published events. This allows users to opt-in or
opt-out of identifying their client in published events.
Changes:
- Created global settings service (src/services/settings.ts) with reactive
BehaviorSubject for app-wide configuration
- Created useSettings hook (src/hooks/useSettings.ts) for React components
- Migrated PostViewer from local settings to global settings system
- Added client tag support to:
- Post publishing (PostViewer.tsx)
- Spell publishing (publish-spell.ts)
- Event deletion (delete-event.ts)
- NIP-29 chat messages, reactions, join/leave, and group bookmarks
(nip-29-adapter.ts)
- Zap requests (create-zap-request.ts)
The client tag setting defaults to enabled (true) for backward compatibility.
Users can toggle this in the post composer settings dropdown.
All event creation locations now check settingsManager.getSetting("includeClientTag")
before adding the GRIMOIRE_CLIENT_TAG to event tags.
* refactor: exclude client tags from NIP-29 and zap requests
Remove client tag support from NIP-29 adapter events and zap requests
as these events may be rejected by servers with large tags or have
specific size constraints.
Changes:
- Removed client tag from NIP-29 chat messages (kind 9)
- Removed client tag from NIP-29 reactions (kind 7)
- Removed client tag from NIP-29 join/leave requests (kind 9021, 9022)
- Removed client tag from NIP-29 group bookmarks (kind 10009)
- Removed client tag from zap requests (kind 9734)
Client tags remain enabled for:
- Regular posts (kind 1)
- Spell publishing (kind 777)
- Event deletion (kind 5)
This ensures maximum compatibility with relay servers and LNURL endpoints
while still providing client identification for standard events.
* feat: implement comprehensive namespaced settings system
Redesigned the settings system with proper namespacing, type safety, validation,
and migration support. This provides a solid foundation for all app configuration.
Settings Structure:
- post: Post composition settings (client tag, relay selection)
- appearance: UI/theme settings (theme, compact mode, font size, animations)
- relay: Relay configuration (fallback, discovery, outbox, timeouts)
- privacy: Privacy settings (read receipts, content warnings, link warnings)
- database: Caching settings (max events, cleanup, IndexedDB options)
- notifications: Browser notifications preferences
- developer: Debug and experimental features
Key Features:
- Fully typed with TypeScript interfaces for each namespace
- Automatic validation with fallback to defaults for invalid data
- Migration system from old flat structure to namespaced structure
- Backwards compatible with old "grimoire-settings" localStorage key
- Import/export functionality for settings backup/restore
- Reactive updates via RxJS BehaviorSubject
- Section-level and individual setting updates
- Reset individual sections or all settings
Changes:
- Created comprehensive AppSettings interface with 7 namespaced sections
- Implemented SettingsManager class with reactive updates and persistence
- Updated useSettings hook to support namespaced API
- Updated PostViewer, publish-spell, and delete-event to use new API
(settingsManager.getSetting("post", "includeClientTag"))
- Added extensive inline documentation for all settings
Migration:
- Automatically migrates old includeClientTag setting to post.includeClientTag
- Moves data from "grimoire-settings" to "grimoire-settings-v2" key
- Validates all loaded settings and fills in defaults for missing values
This foundation will support future settings UI with tabbed interface.
* feat: add comprehensive settings UI with Post and Appearance sections
Created a minimal MVP settings system accessible via command palette and user menu.
Settings are organized in a clean tabbed interface with two initial sections.
UI Features:
- SettingsViewer component with sidebar navigation
- Post section: Toggle to include Grimoire client tag in published events
- Appearance section:
- Theme selector (light/dark/system)
- Toggle to show/hide client tags in event UI ("via Grimoire" etc)
Integration:
- Added "settings" command to command palette
- Added "Settings" option to user menu (before Support Grimoire)
- Registered "settings" as new AppId in window system
Display Logic:
- BaseEventRenderer now honors settings.appearance.showClientTags
- When disabled, "via Grimoire" and other client tags are hidden from events
- Setting applies instantly across all event renderers
Technical Details:
- SettingsViewer uses existing UI components (Checkbox, Button, Label)
- Leverages useSettings hook for reactive updates
- Settings persist to localStorage via settingsManager
- Simple button group for theme selection instead of dropdown
- Clean two-column layout with icons for each section
This provides a solid foundation for adding more settings sections later
(relay config, privacy, database, notifications, developer options).
* refactor: redesign settings UI with shadcn Tabs and cleaner layout
Simplified the settings UI to be more minimal and follow Grimoire patterns:
Changes:
- Use shadcn Tabs component instead of custom sidebar navigation
- Remove non-working theme selector (no theme system implemented yet)
- Use regular <label> elements with htmlFor instead of custom Label component
- Shorter, cleaner copy throughout
- Properly remove unused theme-related imports from user menu
- Follow Grimoire UI patterns (similar to SettingsDialog)
Settings sections:
- Post: Include client tag setting
- Appearance: Show client tags setting
The UI is now cleaner, uses proper form semantics, and matches the rest
of Grimoire's design system.
* feat: add working theme selector and improve settings UI
Added fully functional theme selector and improved the settings UI with
better components and cleaner copy.
Changes:
- Created Switch component (shadcn/radix-ui) for boolean settings
- Added working theme selector that integrates with existing theme system
- Uses useTheme hook to display available themes (Dark, Light, Plan9)
- Reordered sections: Appearance first, Post second
- Reordered settings: Theme first in Appearance section
- Replaced Checkbox with Switch for better UX on boolean toggles
- Simplified copy: "Add Grimoire tag to published events" instead of listing kinds
- Simplified copy: "Display client identifiers in events" instead of "via Grimoire" mention
- Better layout: Label/description on left, Switch on right
Settings now use proper form components:
- Switch for boolean toggles (include client tag, show client tags)
- Button group for theme selection
- Clean justify-between layout for settings rows
The theme selector works immediately - clicking Dark/Light/Plan9 applies
the theme instantly via the existing ThemeProvider context.
* refactor: improve settings UI with Select, icons, and better spacing
Enhanced the settings UI with shadcn Select component, tab icons, and
improved typography and spacing.
Changes:
- Created Select component (shadcn/radix-ui) for dropdowns
- Added icons to tabs: Palette for Appearance, FileEdit for Post
- Replaced button group theme selector with Select dropdown (w-48)
- Added gap-4 between labels and switches for better spacing
- Increased setting names from text-sm to text-base (bigger)
- Reduced help text from text-sm to text-xs (smaller)
- Added gap-3 between "Theme" label and Select
- Added font-medium to "Theme" label for consistency
Layout improvements:
- Theme selector now uses Select with 192px width
- All setting rows have gap-4 between content and controls
- Consistent text hierarchy: font-medium for labels, text-xs for descriptions
- Tab triggers have gap-2 between icon and text
The Select component is properly integrated with the theme system and
displays Dark, Light, and Plan9 options with checkmark indicators.
* refactor: use horizontal layout for theme selector
Aligned theme selector with other settings by using horizontal layout:
- Label and description on left, Select on right
- Added gap-4 for consistent spacing
- Changed label from text-sm to text-base font-medium
- Added helpful description: 'Choose your color scheme'
- Added id='theme' for accessibility
Now all settings follow the same visual pattern.
* refactor: reduce theme selector width for compact display
Changed theme selector from w-48 (192px) to w-32 (128px) since
theme names are short (Dark, Light, Plan9). More compact and
better proportioned for the content.
* fix: pass 'settings' command string when opening from menu
Changed the command string from 'Settings' to 'settings' when opening
the settings window from the user menu. This ensures clicking edit on
the settings window shows the correct command: 'settings'
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: improve tooltip contrast across all themes
CRITICAL FIX: Plan 9 theme had a catastrophic contrast failure where
tooltip text (HSL 60, 100%, 96%) was nearly identical to the background
(HSL 60, 100%, 94%), creating a ~1:1 contrast ratio that made tooltips
completely unreadable.
Changes:
- Added dedicated `tooltip` and `tooltipForeground` colors to theme system
- Updated all three built-in themes (dark, light, plan9) with proper colors
- Modified tooltip component to use new colors instead of primary/primary-foreground
- Added rounded corners and shadow to tooltips for better visual separation
Theme-specific tooltip colors:
- Dark theme: Dark blue-gray background (#217.2 32.6% 17.5%) with light text
- Light theme: Very dark background (#222.2 47.4% 11.2%) with light text
- Plan 9 theme: Dark blue (#220 50% 25%) with pale yellow text
All tooltip colors now meet WCAG AA standards (4.5:1+ contrast ratio) and
are clearly visible against their respective theme backgrounds.
Files modified:
- src/lib/themes/types.ts: Added tooltip color types
- src/lib/themes/builtin/*.ts: Added tooltip colors to all themes
- src/lib/themes/apply.ts: Apply tooltip CSS variables on theme change
- src/index.css: Added tooltip CSS variables for light/dark themes
- tailwind.config.js: Exposed tooltip colors as Tailwind utilities
- src/components/ui/tooltip.tsx: Use new tooltip colors with improved styling
* fix: increase dark mode tooltip lightness for better visibility
Dark mode tooltips were too dark (17.5% lightness) against the very dark
background (4.9% lightness), making the tooltip box hard to distinguish.
Changes:
- Increased dark mode tooltip lightness from 17.5% to 30%
- This provides ~6:1 contrast ratio between tooltip and background
- Tooltip box now clearly visible against dark background
- Text contrast remains excellent (light text on medium-dark background)
The tooltip now stands out properly while maintaining high text readability.
* fix: improve ChatViewer group tooltip contrast in dark mode
The group description tooltip in ChatViewer had poor contrast due to
using `text-primary-foreground` color classes that conflicted with
the new tooltip background colors.
Issues fixed:
1. Description text using `text-primary-foreground/90` - replaced with `opacity-90`
2. Protocol button using `bg-primary-foreground/20` with `text-primary-foreground`
(light-on-light, ~1.5:1 contrast) - now uses `bg-tooltip-foreground/20`
3. All other text using `text-primary-foreground` variants - replaced with `opacity-*`
This allows the text to inherit the correct `text-tooltip-foreground` color
from the TooltipContent component, ensuring proper contrast against the
`bg-tooltip` background in all themes.
Files modified:
- src/components/ChatViewer.tsx: Updated tooltip text color classes
---------
Co-authored-by: Claude <noreply@anthropic.com>
- Update viewport meta tag to include viewport-fit=cover
- Add apple-mobile-web-app-capable and status-bar-style meta tags
- Add CSS safe area insets to body element for proper notch handling
- Ensures content extends into safe areas on iOS devices while
respecting notches and rounded corners
Co-authored-by: Claude <noreply@anthropic.com>
