This is one of those updates where there is a mix of very visible stuff, quiet backend/metadata work, and a handful of "why was this annoying before?" fixes.
Hopefully these updates will make your daily experience better 🤞
A first pass at a new Discovery Feed
A new Discovery Feed is now available from the user menu:
I want to frame this one properly: this is not me saying "here is the final perfect recommendation feed." Not even close.
What I wanted to showcase here is more of a working concept for what we can build using the social graph and public activity already available on Hive and HAF. The current version looks at recent votes from accounts you follow, finds posts that are being picked up by that circle, and mixes in content from both familiar and unfamiliar authors.
That algorithm will almost certainly change.
Maybe the weight of votes needs tuning. Maybe freshness is too strong or not strong enough. Maybe we need more signals, fewer signals, better filtering, or different behavior depending on the type of account. This is exactly the kind of thing that needs real usage before it can become good.
So for now, treat it as an experiment and a starting point. The important part is not this exact formula. The important part is that PeakD can start building more interesting discovery surfaces that are personal, explainable, and still based on Hive data.
I also added a small "How Discovery works" modal inside the page, because if we are going to experiment with ranking, the least we can do is be clear about what is happening.
Your existing preferences still apply after loading: hidden tags, ignored accounts, NSFW settings, and minimum author reputation are respected.
Better SEO metadata, now with JSON-LD
This is probably not the flashiest thing in the release, but it is important. Kudos to for suggesting this a while back.
PeakD now adds JSON-LD structured data in the generated page metadata layer. That means we are not only setting the usual title, description, Open Graph and Twitter tags, but also giving crawlers a more structured explanation of what the page actually is.
For example:
- post pages can expose
SocialMediaPostingdata - account pages can expose
ProfilePagedata - community/profile-like pages can expose
CollectionPagedata - generic routes still get sane
WebSite/WebPagefallbacks
This helps with cleaner previews, better machine-readable context, and a stronger base for search/discovery outside PeakD. It is the kind of work users may not notice directly, but it matters if we want Hive content to travel better around the web.
Witnesses, FAQ, and Support pages got some attention
A few pages got some data and visible updates:
- the Witnesses page now shows estimated witness reward stats in the header, including block reward, total daily witness rewards, and an average top-20 daily figure. Please help me double check the math here and report any issues you notice 🙏
- the FAQ page got a cleaner expandable layout and better dark mode handling
- the Support Us page was reworked into a clearer action-based layout, with progress across the different ways people can support PeakD
- the Snaps link in the top bar got a small redesign so it stands out a bit more
Faster-feeling image and app loading
This is probably not easily visible if you have a good network connection and a fast computer, but a decent amount of work was focused around image rendering and startup behavior.
Images now get more consistent layout attributes, which should reduce some of the jumpiness while posts render. The first image in a post can also be prioritized more deliberately, while the rest can stay lazy.
On the app side, more editor/media dependencies and non critical components are now loaded only when needed. This change is not immediately visible, but it should help PeakD and your browser do less unnecessary work upfront.
Notifications and chat got cleaned up
A few notification-related things landed together:
- opening chat now tries to mark chat notifications as read and sync that state across tabs
- generic notifications now show transaction IDs with direct HiveHub links
- strips autoplay from embedded iframe/video content more aggressively
- virtual operation references are handled more clearly with a link to the corresponding block
- some notification amounts using object/NAI formatting now display as normal HIVE/HBD values
Smaller fixes worth mentioning
A few other useful bits:
- Snaps now respects the low-author-reputation filter from your settings
- DHF header stats are clearer, including separate HBD stabilizer visibility
- hidden-tag filtering now handles unexpected uppercase tags better
- the publish/user menu got more mobile layout polish, including the new icon grid for publishing actions
- the image proxy setting is no longer marked beta
- tip-bot comments collapse more cleanly when they do not add anything useful to a thread
As usual all other minor changes and fixes are listed in the changelog: https://peakd.com/about/changelog
Feedback welcome
The Discovery Feed is the one I am most curious about right now because I think this direction is worth exploring. It's a first attempt at integrating content discovery directly into the platform.
This is exactly the kind of feature that should get better by being used, tuned, and probably argued about a little.
As usual, if something feels better, worse, confusing, or broken, let me know.