Consider removing maxActions

[hober]

ISTM exposing maxActions increases the fingerprinting surface of the platform to little benefit. It might be worth dropping, or perhaps not requiring implementations to expose it.

[beverloo]

In my view, the ideal number of buttons is platform (and OS version) specific as it largely depends on their presentation. Influencers include whether or not button icons are visible, horizontal or vertical stacking and/or whether they're in a drop-down menu that may hide other functionality.

Based on the sort of cross-platform inconsistency problems that developers run in to for notifications, I would personally prefer providing more information rather than less. Maybe even carefully erring towards some sort of getCapabilitiesAndImageResolutions() call. Is there a particular fingerprinting association that you're worried about that couldn't be derived from the user agent?

[annevk]

The other problem with this feature, and actions in general, is that it seems there's only one implementation.

[beverloo]

I would love to learn why other vendors haven't implemented support for actions. We're seeing that >5% of desktop and >10% of mobile notifications includes at least one.