Quick roundup post for the most recent PeakD releases. All of them are included in today's release and live on peakd.com.
When writing a post, you now have access to more AI tools directly in the post editor. The goal is to keep the author fully in the loop while providing tools to review and improve content:
A lot of the practical work this week was on chat.
1) Native chat onboarding is now explicit
If you were still on the classic Sting widget and had no chat preference saved yet, PeakD now shows a small opt-in prompt for the native chat UI.
Important detail: this is still about choice, not forced migration. You can accept it, keep legacy, and switch anytime later in settings.
2) New chat-only color mode setting
I'll be honest, this one is for me. I'm so used to having Discord in dark mode that I created a dedicated Chat color mode setting (default, light, dark). This chat specific setting allows to use PeakD in light mode and the chat in dark mode (or the other way around).
3) Faster chat initialization + better reconnect behavior
The native chat workspace now does less heavy work during init, and reconnect/resume behavior was tuned quite a bit:
The practical outcome is simple: chat should feel less sluggish and less fragile when opening the first time or switching around the app.
The create/edit proposal flow now guards date ranges more strictly.
If end date is before start date, it gets reset and blocked instead of silently accepting an invalid setup. Also, opening create vs edit now resets date constraints correctly.
Thanks to for reporting the problem.
The Snaps Topics sidebar now filters out a set of automatic app tags that were polluting the tag list.
So the sidebar is now more about useful discovery and less about system-generated noise.
Thanks to for the suggestion (this and the next one actually).
If you enabled the KE/Krampus coefficient option in settings, the post author card now shows it directly next to author metadata.
That makes the metric easier to access while browsing, instead of having to jump around account views.
This is more of a tech, less visible, change. PeakD now routes profile/community cover rendering through the dedicated proxy .../u/{account}/cover endpoint in more places (sidebar, user layout, community view, badge view, top user menu).
Practical effect:
This may seems slow when you see a cover image for the first time but it's the correct way to do it. Supported on all image servers (images.hive.blog and proxy.peakd.com).
If anything in these flows feels better or worse on your side, drop feedback in comments as usual.