Congrats to all the teams! Hard fork 28 has been released. We don't do hard forks very often anymore, so it's a rare sight. If you're curious about what changed, feel free to check out the release notes: https://gitlab.syncad.com/hive/hive/-/releases/1.28.0
Most changes are relatively invisible to regular users, but some are worth mentioning:
Voting mana depletion changes
It used to be that with every vote, the actual value allocated would be weaker. For instance, a 100% vote at 80% mana was weaker than a 100% vote at 90% mana. This was not great in terms of UX, so this has been changed so that a 100% vote always allocates the maximum value.
On the flip side, this means that if you're not careful, you can end up with 0 mana relatively quickly. In practice, I don't think you need to change your voting habits, but it's something to keep in mind :)
Inflation reduction (aka all rewards are lower)
You may have noticed that your witness rewards or post rewards are lower than before. This is a side effect of this feature: https://gitlab.syncad.com/hive/hive/-/issues/741
Basically, as the price goes down, the HBD in the DHF takes on a bigger and bigger share, increasing inflation and thus reducing the price further, which in turn increases inflation. It's kind of a death spiral, and we were in the middle of it, so that's why the HF has resulted in such a steep change (when I wrote the feature, we projected a 10% drop; at the time of the HF, it resulted in a ~25% reduction).
At the end of the day, this is a good thing as it will lower sell pressure and inflation while protecting us from inflation exploding and making your current stake worthless.
Stricter key enforcement
This one is more for developers, but it may result in some applications breaking as some dapps may not be up to date. It used to be that you could sign a post-level authority with a higher key, e.g., active. This is no longer the case; now, if an operation requires a post-level authority, you must use your posting key.
Multiple recurrent transfers with the same destination
This is also relatively minor, but some people (@brianoflondon) have expressed the need to have multiple transfers to the same account. It used to not be possible, as sending another transfer would lead to just editing the first one. Now you can have up to 256 transfers to the same user! (256 because that's how many recurrent transfers you can have active in total)