Drop #1644351
ci6529
Daily release notes · 2026-11-08 Posting a drop no longer creates duplicates when the connection times out Today: 6 new or changed features, 6 fixes, 2 security fixes and 35 behind-the-scenes changes. Everything below is live on 6529.io. New and changed Performance: Drop lists, leaderboards and boosted drops load faster on large competition waves, with the same results. Notifications: The unread badge now loads only the count, and the sidebar's highly rated waves refresh every 5 minutes instead of every minute. Chat: Returning to a tab or login refresh keeps your live connection; unread badges can appear up to 3 seconds later on a cold load. Chat: When encrypted messages fail to send, you can keep writing, and a banner says retries continue; after about 20 seconds the conversation shows as delayed. Profiles: Device Permissions in Preferences now says when this browser cannot read its own keys and warns before you revoke a possibly local permission. Accessibility: Pressing Escape closes the emoji picker and returns focus to its trigger, even from the search field. Fixed Waves: Fixed failed saves leaving drops half-deleted or partly edited, and rolled-back bot posts leaving unread and metric updates behind. Waves: Fixed duplicate drops after a timeout or lost connection; each post is now retried once and confirmed with "Your drop was posted." Waves: Fixed drop posts, reactions, votes and deletes hanging until a timeout; they now return a retryable busy message, and posts finish sooner. Chat: Fixed the direct message list taking 15 seconds or more to load for some users who have blocked profiles. Chat: Fixed a false "Encrypted DMs could not finish setup" message after enabling signed posts and encrypted DMs together. Waves: Fixed shared post links on mobile sometimes opening at the top of older history instead of the linked post. Security API: Strengthened sign-in token checks; no action needed. API: Strengthened ownership checks for media uploads; no action needed. Known issues Chat: Typing indicators now share one connection per tab, so typing may not show for the first 2 seconds after a page loads, and only the most recently opened wave shows typing when two chats are open. Behind the scenes: Most of today's work was backend performance and reliability: smaller database queries for viewers in many groups, faster eligibility checks, shorter competition lock times, extra timing and connection metrics, and clearer error handling for uploads and activity logs. Other work covered live-update delivery tuning, server support for a second encryption suite, keepalive checks and audience limits built but switched off for now, and staging and automated-check configuration cleanup. Thanks @[punk6529]. For builders: Backend: viewer-group CTEs and stored group sets, off-lock competition leaderboards, afterCommit in loops, budgeted write transactions, WS fan-out and PING/PONG, follower audience flag, MLS suite-set grants and security hardening; frontend: clientdropid idempotent creates, unread-count route, shared typing socket, E2EE enrollment and stall fixes; desktop: no changes. Each change with its pull request is in Deploys · Production (https://6529.io/waves/2041bb9f-b5ba-489b-b426-d9c5d62b2ce7).
