Implement reply, like, and repost buttons for chat messages:
Features:
- Action buttons appear on hover for each message bubble
- Reply button - opens thread view or reply composer
- Like button - sends reaction (+) with filled state tracking
- Repost button - opens repost decision sheet
The buttons integrate with the existing NoteAction system:
- Uses existing app_images for icons
- Integrates with reaction tracking via reaction_sent_id
- Properly routes to reply, react, and repost handlers
- Follows Slack-like UX pattern with hover-based interactions
This completes the chat message interaction layer, making
messages fully interactive while maintaining a clean interface.
Implement a Slack-style quick switcher for navigating between channels:
Features:
- Press Cmd+K (or Ctrl+K) to open the channel switcher modal
- Search/filter channels by name
- Navigate with arrow keys (↑/↓)
- Select with Enter or click
- Shows unread count badges
- Highlights currently selected channel
- Dark overlay background for focus
- Keyboard shortcuts shown at bottom
The switcher provides fast keyboard-driven navigation between channels,
matching the Slack UX pattern that users expect.
Implement basic keyboard shortcuts:
- Escape: Close the channel creation dialog
- Cmd+N / Ctrl+N: Open the channel creation dialog
These shortcuts provide quick access to channel management without
requiring mouse interaction, improving the Slack-like UX.
Implement a channel creation dialog that allows users to:
- Enter a channel name
- Specify comma-separated hashtags to track
- Create and subscribe to new channels
When a channel is created:
1. It's added to the active channels list
2. Saved to disk for persistence
3. Automatically subscribed to start fetching messages
The dialog uses egui::Window for a modal-like experience and
includes validation to ensure both name and hashtags are provided.
When a channel is selected, adjust the StripBuilder to expect only 1
content cell (for ChatView) instead of num_cols cells. This prevents
layout issues when switching between channel chat view and normal
column view.
When a channel is selected in the sidebar, the main content area now
displays ChatView with Slack-like message bubbles instead of the
traditional column timeline view. When no channel is selected, the
app falls back to the normal column view.
This completes the core integration of the Slack-like chat interface.
- Create ChatView component for chat-style message display
- Implement message grouping (same author + 5min window)
- Add message bubbles with rounded corners
- Include avatar, author name, and timestamp
- Support click-to-thread functionality
- Relative timestamp formatting (5m ago, 2h ago, etc.)
Note: Needs API fixes to compile - several API mismatches with current
nostrdb/notedeck APIs that need adjustment.
- Create ChannelSidebar component with channel list display
- Implement channel selection with visual highlighting
- Add unread badge support for channels
- Include "Add Channel" button at bottom
- Support both light and dark modes
- Use # icon prefix for channels (Slack-like style)
This commit lays the foundation for the Slack-like interface redesign:
- Add Channel data structure: represents a channel that filters notes by hashtags
- Add ChannelList: manages multiple channels per user
- Add ChannelsCache: maps users to their channel lists (stored per-account)
- Add RelayConfig: global relay configuration (not tied to user profiles)
- Add persistence: save/load channels and relay config to disk
- Update Damus app state to include channels_cache and relay_config
Next steps:
- Create sidebar UI with channel list
- Build main chat view with message bubbles
- Add thread side panel
- Update main layout to use new components
Since users can delete the corrupted decks_cache.json file, the
migration logic is no longer necessary. The URL encoding/decoding
ensures all new cache files will be saved correctly going forward.
When decks_cache.json was saved with the old format, relay URLs like
"wss://wot.nostr.net" were split by the ":" delimiter into separate
tokens: ["wss", "//wot.nostr.net"]. This commit adds migration logic
to detect and reconstruct these corrupted URLs during parsing.
Detection heuristic:
- If the relay_url token is just "wss" or "ws" (without "://")
- AND the next token (hashtags_str) starts with "//"
- Then reconstruct the full URL as "wss://..." or "ws://..."
- And pull the next token as the actual hashtags
This allows existing users with corrupted decks_cache.json files to
automatically have their relay URLs fixed on next app restart, without
needing to manually delete the cache file.
The relay URL "wss://wot.nostr.net" was being incorrectly parsed as
Relay("wss", Some(["//wot.nostr.net"])) when the app restarted and
loaded from the decks cache.
Root cause:
The TokenWriter uses ":" as the default delimiter. When relay URLs
containing ":" (like "wss://wot.nostr.net") were serialized, the
colons were not escaped, causing the URL to be split into multiple
tokens during parsing:
- Token 1: "relay" (type)
- Token 2: "wss" (mistakenly read as relay_url)
- Token 3: "//wot.nostr.net" (mistakenly read as hashtags)
Solution:
- URL-encode relay URLs when serializing (using urlencoding crate)
- URL-decode relay URLs when parsing
- Added backward compatibility: if decoding fails (old format),
fall back to using the token as-is
This ensures relay URLs with colons are correctly preserved across
app restarts.
This fix addresses the "got unknown eose subid" warnings that were appearing
in the logs when EOSE (End Of Stored Events) messages arrived from relays.
The issue was that when `TimelineSub::try_add_remote()` and
`TimelineSub::try_add_remote_with_relay()` created new subscription IDs,
they were not being tracked in the `Subscriptions.subs` HashMap. When EOSE
messages arrived for these subscription IDs, the `handle_eose()` function
couldn't find them in the HashMap, causing the "unknown eose subid" warnings.
Changes:
- Modified `try_add_remote()` and `try_add_remote_with_relay()` to accept
`&mut Subscriptions` and `&TimelineKind` parameters
- Added subscription tracking by inserting subscription IDs with
`SubKind::Timeline(timeline_kind)` into the Subscriptions HashMap
- Updated all call sites throughout the codebase to pass the required
parameters, including:
- TimelineCache::open()
- DecksCache::add_deck_default()
- DecksCache::new_with_demo_config()
- is_timeline_ready()
- execute_note_action()
- execute_and_process_note_action()
- add_demo_columns()
- demo_decks()
This ensures all subscription IDs are properly tracked, eliminating the
unknown EOSE warnings and allowing proper handling of EOSE messages.
This commit adds the ability to create columns that display content from
a specific relay, with optional hashtag filtering.
Features:
- New TimelineKind::Relay variant storing relay URL and optional hashtags
- Relay-specific subscription support in RelayPool (subscribe_to method)
- UI for configuring relay URL and hashtag filters
- Filter generation for relay-specific queries
- Column header with relay icon
- Serialization/deserialization support for deck persistence
Implementation details:
- Extended RelayPool with subscribe_to() for relay-specific subscriptions
- Added TimelineSub::try_add_remote_with_relay() to handle targeted subscriptions
- Timeline cache automatically routes relay columns to specific relays
- UI validates relay URLs before creating columns
- Hashtag filtering is optional and space-separated
Usage:
Users can now add a "Relay" column from the column picker, enter a relay
URL (e.g., wss://relay.example.com), and optionally filter by hashtags.
from remote-tracking branches:
* kernel/fix-soft-keyboard
* kernel/composite-profiles-perf
* kernel/fix-nav-flicker
kernelkind (8):
Revert "fix: nav drawer shadow extends all the way vertically"
chore(profiling): markup composite render path
chore(tracy): repaint every frame
feat(composite-cluster): do culling for pfps
feat(mime-cache): upgrade UrlMimes
feat(reactions): use ProfileKey when possible for performance
fix(nav-drawer): shadow extends all the way vertically
fix(thread): remove flicker on opening thread
1. more performant. No more deserialization every frame
2. employs TTL (so cache doesn't grow unbounded)
3. exponential backoff to retry on error
Signed-off-by: kernelkind <kernelkind@gmail.com>
since we stop rendering when there is no user input, tracy sees
big hangs, and it's annoying to parse through which frames are
actual performance issues and which are due to no user input.
So just repaint every frame while using tracy.
Signed-off-by: kernelkind <kernelkind@gmail.com>
df5cf8a1fc caused a regression
making the soft keyboard auto close. This patch extends the shadow
all the way vertically without triggering the regression
Signed-off-by: kernelkind <kernelkind@gmail.com>
the previous unseen notification indicator only ran once a few
seconds, but when it did it often took > 5ms because of ndb::query,
which is unacceptable.
This commit removes the ndb::query entirely and relies on the
ndb::poll_for_notes which is already being used every time there is
a new event from a relay
Signed-off-by: kernelkind <kernelkind@gmail.com>
will be used in the UI for whether to show the filled/unfilled
react icon in the actionbar. Temporary until ndb metadata lands
Signed-off-by: kernelkind <kernelkind@gmail.com>
