Gregory's ServerOnce implemented, you can expect proper support in the API, web frontend, and the official mobile clients (that we develop), and we intend to publish the API details in advance so any other client can support them.
We will also be publishing FEPs to ensure that this becomes a standard that can be supported by every ActivityPub implementation.
It will (if all goes fine) support notifications when someone quotes you, as well as controlling who can quote your posts (everyone, nobody, mutuals…)
|
Top-level
 36 comments
  @renchap @GottaLaff Protocolbros overthinking it as usual. The functionality provided by most mastodon apps of just showing the post preview for links to posts is really all we are asking for. I don’t see any reason to change the protocol. Just change the UI in your apps to support previews of linked posts like nearly everyone other than Mastodon gGmbH does and we will be happy. I’ve been using in Mona for at least a year, and have not needed answers to any of those questions. @bhawthorne @renchap @GottaLaff I can imagine getting notifications when someone quotes your post is useful though? seems to be what most of this complexity is from and I can understand why if they're already making a change like this to the mastodon feature set that they want to implement it with this feature  @renchap QT doesn't have to be this super complex thing. link previews are already good enough for 99% use cases. here are the answers to your questions:  > The quote post becomes unavailable once blocked, ”The quoted post is not available”. The problem is: for whom? How is this enforced? Ideally, if use A quotes user B and user B blocks user A, then the quote post goes away, or the link becomes completely invalid. Otherwise users C, D, E, etc. who view user A's post can still click through the link and harass the person. This was a serious problem on Twitter. @renchap @rolle I mean, you can always just post a hard link to a public post, or screenshot. The big thing is to make the easy path the one with the protections, which forces people to be actively malicious instead of just casually cruel, and also to make the easy path nudge people towards prosocial behavior. This is also why I continue to advocate for bottom text on QBs, because it encourages "yes, and..." and discourages "hey look at this asshole". Thank you so much. I appreciate that y'all are not just aping what other platforms do, but are trying to do what's best for the folks who spend time on fedi. ❤️ To answer some common questions I get: Yes, we want to have proper safety features for Quote Posts. We got enough feedback from Xitter to know how they can be used for harassment. Maybe this is not a concert to you, but it is for us. Yes, it takes time, but we are a very small team, with only one full-time developer for the backend. At the moment, handling the day-to-day (reviews, bug fixes, security) is already more than what we can handle, so everything takes more time that we would like. As always, you can help by contributing, either: @renchap @old_hippie any chance someone will be hired to focus on rewriting it on a more used language so development can be more efficient moving forward?  @renchap are you going to ignore the de facto standard implemented already in other fedi software or do you plan to support it? if yes, how? @renchap  @renchap What safety features do you have in mind? I think the dynamic this sets in motion won't really be receptive to features 🤨  @renchap thank you for the update, and for applying your collective talent to doing it well. It's appreciated 🙏  @amayer Quote Posts can (and will) be used for harassment and make it much more impactful than when people use a link (without a preview of the quoted post) or a screenshot.  @renchap as I've probably mentioned before we'll switch over to official quoting as soon as its available.  @renchap ooh, the controlling thing seems great. Probably should be opt-in seeing how many people were against Quote-Toots.  @renchap how do you plan on handling edits to a post that has been quoted? (Ie I make a post. Someone quotes it. I edit the post. What is/should be shown in the quoted post?) It is not uncommon or perhaps even surprising that the person quoting a post might be pointing out something that results in a later edit of a post or at least no longer relates to the later edited post I don’t have an easy answer. Perhaps quote to a specific version of a post & show that newer versions exist? |
Here are a sample of the hard questions we need to have answers for:
- Can you quote a post when replying to someone
- Is pasting a link into a post quoting? What if there are multiple posts linked?
- How to handle implementations, instances or clients not supporting quote posts
- How does this interact with moderation? Blocking?
- How do we handle ActivityPub implementations with slightly different formats, like if they support quoting multiple posts in the same status?