* main: (45 commits)
Display tag counts in the filter menu
Move Add Card button to header
Re-write help content, try a modal-like display
Move to internal registry
Show date instead of time for notifications older than 1 day
Ensure checks are visible for tags and assignments
Adjust padding so card number isn't cut off
Don't color the collection header in considering
Golden cards bubble to the top of Considering, too
Adjust card collection header when colored golden
Allow cards in Considering to gilded
Hide focus ring on new card titles and step inputs
Add hover effect for comment edit button
Add hover effect to overflow button
Improve multi-account behavior of the PWA
Remove unneeded *
Rename test
Review the code to move cards
Update editor
Generalize and delete mentions too
...
- It does not make sense to scan "event summaries" for notifications.
- Placing them at the message level prevents us from using the generic approach to extract the mentionable content
This introduces a more dynamic system of activity scoring, to improve
the way bubbles "bubble up" due to their activity. There are a few
different parts we can tune here, and it's likely we'll need to make
adjustments once we get a feel for how this works in practice.
The basic idea here is:
- We assign points for certain types of event that happen on a bubble. A
boost gets 1 point, a comment gets 10 points, and so on.
- These points decay over time, at a rate of 50% per day. So old
activity is worth much less than new activity. Bubbles should rise up
quickly when acted upon, bit will float back down if left idle.
- Some comments can score higher than others: the first comment from
each person on a bubble is worth more (20) because it signals that
more people are getting involved; and comments that follow a comment
by a different author are also worth more (15) because that signals
there's ongoing conversation between people, not just a series of
notes being left by one individual.
In terms of implementation, we persist the score on the bubble
whenever it changes, but we handle the decay on the client side. That
allows us to cache the bubble representation without having to
continually change it while its activity decays.
We also keep a separate `activity_score_order` attribute on the model.
This can be used to sort the bubbles in order of "most active", without
having to think about the decay.
Stanko K.R.