Recent searches
Search options
I'm still on the fence about mastodon's choice not to notify people when they get quote posted.
In the past I wanted it this way. Because I believe getting notified created bad incentives.
"Is this person talking to me or about me?"
"Is this a dunk? I don't know, but I better assume it is."
Anyway, right now I'm thinking about the tradeoff. I think I'm missing a lot of discourse because I don't get notified of people commenting on my posts.
@polotek wait, what? Mastodon hasn't made that decision. Client's have done "quoting" via expanding links that happen to be on fediverse servers.
Mastodon's Quote Posts FEP is absolutely including the notifications and all the safety controls.
cc @renchap perhaps you can explain better than I on this.
@thisismissem @renchap I mean. It is a decision. Choosing not to implement is a decision. It seems that I'm frequently mistaken about the intentionality behind the priority decisions that mastodon has made. It seems like the answer to everything is "we're definitely going to do that, we just haven't yet." Honestly I'd prefer to see more of an opinion about these things.
But more importantly. The mastodon experience is not only what the official client does.
@polotek @renchap right, but what third-party clients do or not do isn't Mastodon making decisions. When you've a team of 3 people, you need to decide what to prioritize, because you can't work on all the things all the time.
Grouped Notifications were first, Quote Posts next, because that's how the funding flowed.
This goes back to something I've said before:
People's impression of a network is not just the 1P clients. It is a "mastodon feature" because when you are using "mastodon clients" to connect to a "mastodon server" that is the experience of users, regardless of who made what decision.
But I would note: if mastodon hadn't actively _fought_ the implementation of this functionality for so long, it would probably have helped the perception here.