nostr:npub15y6x73rcu0867mulkdd7mdp28mrx6zlh6206suwsm3a7e7v5fsdqq4azut What do you mean sending an extra notification? Servers might be able to get that info via ActivityPub, but clients only work with Mastodon API.
nostr:npub1svs3dzxhfc3mtdr7a59jsj48wdg0f0fgy0au2yataxu6vza6n8userp66u nostr:npub1zf74eseytr2qwva2pa7lek9029hhmk22a4ah5yy28ja4hd87kyuqf9zwqy Well, yes, currently no Mastodon app will be able to implement this (as servers will only notify the original poster of a boosted post). However, that is *no* limitation of the protocol (#ActivityPub) in itself – it's a design decision of #Mastodon! Or at least I don't see any reason why it couldn't be done: The information who boosted is already there, you'd just need to send an extra notification to the server of that person, no?
Discussion
nostr:npub1svs3dzxhfc3mtdr7a59jsj48wdg0f0fgy0au2yataxu6vza6n8userp66u I read "a limitation of the protocol" as "a limitation of ActivityPub" since that is the protocol Mastodon is using. It's true that the Mastodon API doesn't support this feature and that's what stopping clients from implementing it, but that's on Mastodon itself, not the protocol it's using. As far as I can tell, ActivityPub doesn't do anything to prevent this feature from being implemented as described.