"Quote and reply controls appear to be bundled together in a single dropdown menu, where users can open the conversation to “Anyone,” or limit it to “Profiles you follow” or “Mentioned only.”"
@stefan there's work in progress or starting on both of these. Remember, threads has a dozen if not hundred engineers available to it, Mastodon has 1.5-2 core staff engineers, and a litany of volunteers.
@thisismissem Oh I know. But I really think most people would be satisfied with just having a proper preview, which some third-party Mastodon apps already do.
Maybe the implementation could've been done in two steps, start with the preview, and then focus on the spec?
I don't like this move by #Threads. Limiting who can do #quoteposts pretty much defeats the purpose of quote posts in the first place.
Oh well, I'm confident that #Misskey will not adopt this beyond not allowing blocked users to quote a post by the user blocking them (which I disagree with btw), so this will not affect me thankfully and I can still quote Threads users as long as they haven't blocked me. :seija_coffee:
@mima Quote Posts is a better version of link preview, even Mastodon Clients (Mastodon doesnt have Quoted Posts on Server side) does Quoted Posts exactly like that. So preventing it is stupid and wont get adopted on all of the Server Softwares
I have seen the downsides of the Quote Post feature on Threads lately. There it is in even wider, in constant use, because there is no shares shown on your profile.
Quoting a post often puts others in a spotlight and not always in very flattering way. I have made that mistake myself as well. It doesn’t feel good if you criticize someone this way and people start slandering and it’s out of your control. I sometimes feel like a bully using it.
So if/when we ever get a Quote Post functionality here on Mastodon, I hope it will be different. Perhaps in this case the problem is Threads and the algorithm and not the feature itself though.
@rolle Every functionality is just that - a functionality. Dealing with humans (ab)using it is the real issue, for which smaller instances are better suited than mega ones. Human interaction just doesn’t scale.
@rolle It’s not the feature but the people. There are always ways to go around limitations. Screen capture is another way to do a quote-post if the will is there.
#Bluesky supports #quoteposts, but not listing all known quotes of a post? And you're telling me this is supposed to be the most Twitter-like experience, when this feature has been a staple of #Twitter for many years?
This is worse than not having #hashtags. How tf am I supposed to know if a post got quoted? Even #Misskey supports listing all known quotes FFS! :parsee_angy:
@:mima_rule: Mima-sama That might be because Misskey quote-posts differently from Hubzilla (where my post is from) and (streams) (where Mike's post is from), and it doesn't expect there to be different implementations of quote-posts. Even though Hubzilla and (streams) do it just like Mistpark did in summer 2010.
So quote-posts that aren't linked references to posts but verbatim copies of posts are as unexpected as unsupported.
short version: we have a small set of bugs to fix and chores to do before an App Store release, and quote post UI will come after that, in version 1.8.
expect that to work on Treehouse, Akkoma, and some Misskey forks. vanilla Mastodon has yet to finalize a native quote post API but we'll try to support it when it arrives.
Feditext may end up including UI support for emulated quote posts, equivalent to just pasting in a link to the post, since that involves most of the same UI work as native quote posts.
As we know, #quoteposts aren’t really a thing in #mastodon (yet, hopefully) but in my phases of trying out different mastodon clients I have noticed that one of them actually gives you the option to ‘quote post’ something — but how is an iOS client able to have the feature when mastodon as a whole does not? If anybody knows/has knowledge about this and could shed some light on it, that’d be super cool. I’ve just always wondered.
So here I am ‘quote posting’ this Washington Post article just to go over to my other mastodon client, mammoth to see what it looks like. If anybody sees this and cares any amount at all, feel free to let me know what it looks like on your end! I just want to know if it actually works as a quote post on the other side of things. Because if so, well then Ice Cubes is awesome but again how does that work?
P.s. I’m so glad I moved back to the InfoSec instance. I never have to worry about running out of space when posting now. So, randomly, if you see this — thanks Jerry! 😂
@blakehensley@washingtonpost QPs are on the roadmap for Mastodon https://joinmastodon.org/roadmap. As for why some clients support a qp-like feature, it's a popular requested feature and not difficult (imo) in practice to provide. A QP is really just a link to another post where you can see the text and OP account. I think whether it works or not in other clients will vary.
If this "privacy setting" for #quoteposts is implemented with it enabled by default, the result will be disastrous. :reisensweat: Since there is no other way to enforce this setting other than #defederation, we are going to see Mastodon servers strong-arming those software developers who are "non-compliant" by threatening a #fediblock. :reisensweat: Developers of the -key and -oma families will suddenly have to scramble to make their implementation of #quotetweets compatible with Mastodon's "privacy-friendly" implementation. :satsuki_sadge: This way of "extending" the fediverse is not acceptable, and everyone who has opposed #Facebook joining the fediverse due to #EmbraceExtendExtinguish should also oppose this issue which just eventually leads to the same result.
Mastodon might introduce a "proprietary", home-brew "No quote-toots allowed" flag outside the ActivityPub standard that probably won't be documented anywhere. Just like their "sensitive image" flag, but even more critical.
And if that happens, all Fediverse projects that have a quote-post/quote-boost/quote-tweet/quote-toot/share feature will have to have that flag reverse-engineered from Mastodon's source code and implemented a functionality that greys out the corresponding button under "no quote-toot" posts. And all their instances will have to upgrade to a version that fully supports that flag before Mastodon rolls out that flag. Or else Mastodon will defederate all their instances for being non-compliant.
This will at least affect Friendica and everything that can be traced back to it, including Hubzilla and (streams), as well as Misskey and everything that can be traced back to it, including Firefish whose development is dead and dozens upon dozens of other Forkeys.
If this actually comes, and if it's enforced immediately after release with no grace period, Mastodon could just as well fully be defederated from the rest of the Fediverse due to being incompatible. It'd cause a rift between Mastodon and the non-Mastodon Fediverse anyway because the former would have a requirement for federation which the latter is incapable of fulfilling.
@Jupiter Rowland I think that is how the fediverse will grow. People will be invited to a place, and then they will learn about the fediverse afterwards.
In fact, that is my strategy for attracting people to Hubzilla. Build content and community websites that attract users, and once they are a member of the community, they start learning about the fediverse. They came for the content, stayed for the local community, and then reached out to the fediverse.
I see this as a natural progression, regardless of how they are introduced to the fediverse.
@Scott M. Stolz The major downside of letting people discover first decentralisation and then the greater Fediverse is that they get too used to their first impression of wherever in the Fediverse they land, they adjust their action to this first impression, and they may end up deeply disturbed when they find out what the Fediverse really is.
I've seen it all the time during the second wave of Twitter-to-Mastodon migration.
After spending one to three months on mastodon.social or wherever they've been railroaded, new Mastodon users discover that Mastodon is decentralised, like many big and little Twitters that are separate but connected to each other.
All of a sudden, Mastodon becomes very complicated. But they don't mind much. After all, it's working for them.
After spending three to six months on Mastodon, they discover that the Fediverse is, in fact, not only their beloved and oh-so-cosy Mastodon. They usually find it out the hard way when they come across the first post or comment from something that's very much not Mastodon, and that does totally weird things that they thought are impossible on Mastodon.
For not exactly few, this is too much. It's like an intruder in their beloved new home. They got used to the Fediverse only being Mastodon and Mastodon only being connected to more Mastodon and nothing else that they find this discovery deeply disturbing.
I think there have been dozens of Mastodon newbies who started following me because they needed Twitter-style background noise in their timeline, and who blocked me without unfollowing me when my freaky, so much non-Mastodon-like posts started tainting their timeline.
We do not need another case of #Mastodon strong-arming other developers of the #fediverse into being compatible with their implementation just because they're the most-used software out there.
Quote posts—which have already been implemented in several other Fedi projects and even some Mastodon clients—are on the Mastodon roadmap for 2024.
I'm looking forward to using this feature, but even more than that I hope its arrival in mainline Mastodon will finally put paid to the obtuse and often bad-faith arguments against the feature that were rampant a year ago.
@Ralph The main two would be a consistent presentation of what you’re quoting with less work (not that you’re doing a ton of work now), and—depending on how it is implemented—possibly some kind of notification and stats for the original poster.
On the other hand, one nice thing about a feature like this is if you would rather manually quote a portion of a toot inline like you do now, you can keep doing that instead.