Mini-Diarium Files

Mini Diarium v0.4.5

Lots of UI/UX fixes and improvements in this release. We also included a "general debug report" feature in the settings so user can generate debug reports to more easily troubleshoot issues.

Installation

Download the appropriate file for your platform:

• Windows: Mini-Diarium-0.4.5-windows.msi or .exe
• macOS: Mini-Diarium-0.4.5-macos.dmg
• Linux: Mini-Diarium-0.4.5-linux.AppImage or .deb

Security Notes

Windows: SmartScreen may show a warning on first launch. Click "More info" then "Run anyway". macOS: Gatekeeper may show "damaged and can't be opened." Run xattr -cr "/Applications/Mini Diarium.app" in Terminal, then launch normally. Linux: Verify SHA256 checksums against checksums-*.txt before installation.

What's Changed

Added

• Advanced tab in Preferences with a "Generate Debug Dump" button — exports a privacy-safe JSON diagnostic file (app version, OS/platform, schema version, entry counts, auth method types, backup count, plugin count, preferences); no entry content, passwords, or key material is ever included
• Month/year picker in calendar header: clicking the month/year label in the sidebar calendar now toggles an inline month picker. The calendar body switches to a 3×4 month grid with year-step arrows; selecting a month jumps directly to that month and closes the picker. The currently displayed month is highlighted in the grid. No new dependencies. (#43)
• Delete entry button for multi-entry days: a "−" button now appears next to the "+" button in the entry navigator when a day has more than one entry. Clicking "−" opens a confirmation dialog ("Delete Entry" — "Are you sure you want to delete this entry?") and, if confirmed, deletes the currently selected entry and navigates to the next available entry for the same day (staying at the same index, clamping to bounds if the last entry was deleted). The button is only visible when the day has multiple entries and is disabled while an entry is being created. (#43)

Changed

• Unified user-facing terminology to "Journal": all UI text, error messages, and documentation now consistently use "Journal" instead of the mixed "diary"/"journal" wording; internal Tauri command names and filesystem identifiers (diary.db) are preserved for compatibility (issue [#46])
• Auto-select last-used journal on startup: the app now skips the Journal Picker when a previously used journal is known (active_journal_id set in config). initializeAuth() calls refreshAuthState() directly and transitions to the password prompt (or unlocked state if already unlocked). The Journal Picker is shown only on a fresh install or when no active journal is configured. (#43)
• Reduced password minimum length to 1 character: the 8-character minimum has been removed. Passwords must be non-empty; a visual strength indicator now guides users with feedback on weak/medium/strong passwords. Very weak passwords show an additional warning banner with recommendations. This aligns with the cryptographic reality that Argon2id protects any password length, while giving users control over their security tradeoffs. (#43)
• Website SEO/GEO follow-up pass (2026-03-06): replaced the 4.5 MB hero GIF with compressed MP4/WebM demo media plus a poster image, switched the stylesheet to inline-critical + non-blocking loading, updated title/description metadata for search intent, replaced the social preview SVG with a PNG, changed the hero download CTAs to distinct Windows/macOS/Linux direct installer links with ARIA labels, added apex-canonical redirect/cache parity to the nginx reference config, and documented post-release Search Console/IndexNow/Cloudflare ops in the release guide.

Fixed

• Window position flash on startup: the main window no longer flashes at the default position before jumping to the saved position. The window is now created hidden ("visible": false in tauri.conf.json) and shown explicitly after tauri-plugin-window-state has restored the saved bounds. (#43)
• "+" add-entry button: the button to create an additional entry for the same day now correctly guards against concurrent calls using a reactive signal. The button is disabled while creation is in flight, preventing duplicate entries from rapid clicks. Errors are no longer silently swallowed. (#43)
• "Go to today" calendar button: clicking the calendar icon in the sidebar now correctly navigates the calendar month view. A createEffect in Calendar.tsx watches selectedDate and syncs currentMonth whenever the selected date falls outside the currently displayed month — fixing all month-navigation cases including "go to today", go-to-date overlay, and day/month menu navigation. (#43)
• Clicking adjacent-month days in calendar: days from the previous or next month shown in the calendar grid are now clickable. The isCurrentMonth guard has been removed from handleDayClick and the disabled attribute; only future dates (when the preference is off) remain disabled. (#43)
• Sidebar header border alignment: the sidebar title bar and the main header bar now share the same rendered height (64 px). Previously the sidebar's text-only header was 12 px shorter than the main header whose icon buttons set the height, causing the bottom borders to visually misalign. (#43)
• "Go to today" button alignment: the button in the sidebar was right-aligned (justify-end) while the calendar below it is left-aligned. Changed to justify-start so the button aligns with the calendar's left edge. (#43)
• Settings tab active state on light theme: the active tab in Preferences used hardcoded Tailwind classes (bg-blue-100 text-blue-700) that could render with low contrast. Replaced with CSS-variable classes (bg-active text-primary) that correctly follow the current theme in both light and dark mode. (#43)
• Editor placeholder showing "Loading…": TipTap's placeholder extension showed "Loading…" whenever the editor was empty during an async entry load, which could flicker on fast navigations. Placeholders are now always static ("Title (optional)" / "What's on your mind today?"). (#43)
• Calendar month navigation broken by reactive loop: clicking the previous/next month buttons had no effect because the createEffect that syncs currentMonth to selectedDate was also reading currentMonth() as a reactive dependency — causing it to immediately reset the month back. Fixed by using untrack(currentMonth) so the effect only re-runs when selectedDate changes.
• "+" button creates spurious entry on empty day: pressing "+" when no content existed would create and immediately delete an empty entry (visible briefly as a dot in the calendar). The button is now disabled unless the current entry has body content. Contextual tooltip text explains why the button is disabled ("Write something first to add another entry for this day") or what it does when enabled ("Add another entry for this day").
• New entry auto-deleted 500 ms after creation: after creating a new entry via "+", setContent('') caused TipTap to fire onUpdate synchronously with empty content, scheduling a debounced save that would delete the blank entry. An explicit debouncedSave.cancel() now runs immediately after state is reset to prevent this.
• Multi-entry day counter order: entries for a day are now displayed in chronological order (oldest = 1/N, newest = N/N). Previously the backend's newest-first ordering made the counter confusingly start at 1 for the most-recent entry. New entries created via "+" always land at position N/N. Opening a multi-entry day now navigates to the newest entry (N/N) instead of the oldest.
• Empty entries persist on lock/switch: empty entries created with the "+" button now correctly delete themselves when the diary is locked or when switching journals without adding content. Previously, the empty entry would remain in the database until the user navigated to a different entry. The fix implements a pre-lock event pattern that ensures saveCurrentById() (which deletes empty entries) is called before the database is locked, covering all lock paths (manual button, OS session lock, and journal switching).

Full changelog: https://github.com/fjrevoredo/mini-diarium/compare/...v0.4.5