@mastodonmigration You are mistaken it, this is not about quote posts. Starting with Mastodon 4.5, when you view a post (after clicking on it), Mastodon will try to fetch replies from this threads from other servers, as your server might not know about them. It will then tell you if it found more replies, and ask if you want to refresh the screen to view them. We hope this will solve the "missing replies" problem.
@aslakr You can start your reply, then go to the post you want to quote, and press the boost button then quote. Same for edits.
We will make this easier in a future version by allowing you to paste a link, detect it’s a quotable post, and offer to transform it into a quote (but this is technically complex, so we will launch without it for now)
@GossiTheDog@Gargron As this is a very high profile feature, we are trying to minimise the time where some users have it while some others dont. We are not rushing things, but we planned from the start to release a stable version asap once we are confident it all works
@GossiTheDog@Gargron We are targeting next month for the 4.5 release, we need a bit of time to ensure there are no big issues reported now that we enabled it on mastodon.social, then we will release 4.5.0-beta1 (hopefully at the end of this month)
@tchambers@rimu The server covenant is purely declarative, I think that if we start sending the general public to a pool of servers there needs to be more checks here. But we have ideas in this area that I hope we will soon be able to make progress on.
@tchambers@rimu Yes it is, but I am worried about letting users pick their server from any server that opt in. You really want users to go on *well-managed servers* and avoid servers that depend on a unique person (high risk of the server disappearing), without proper moderation or correct operation practices. And that is without even without discussing about bad actors starting to exploit this.
@timbray the library Mastodon uses for image processing does not support C2PA. Fastly is a publicly traded company with hundreds of of devs. Are you really comparing it to Mastodon and wondering why they can do things we can’t? @leoncowle
This is built on FEP-044f (Consent-respecting quote posts, https://codeberg.org/fediverse/fep/src/branch/main/fep/044f/fep-044f.md), which requires the quoted account to provide a stamp proving that they approved the quote. If there is no such stamp (or it has been invalidated), then Mastodon (and other software supporting the FEP) will not display the quote. If the quoted account does not support the FEP, no stamps will be issued, and the quote will not be displayed either, only the link (as before).
And now thanks to @chaosexanima I can show you how the retractation works: - you get a notification when someone quotes you - on their post, you have a new menu to remove their quote of your post - you confirm, and your quote is removed and shown as having been retracted - the quote is no longer displayed on the original post
Coming soon on your Mastodon server… The long awaited quote posts, with user-control (you can chose if you want to be quoted on a per-post basis, change it later, and retract any quote of your post)
Amazing work by the team 🎉
Expect a blog post with all the details in a few weeks, support in the mobile apps, then we will enable the feature on mastodon.social, then release Mastodon 4.5
@linos We discussed "partial quotes" when working on quote posts, and decided not to explore this because you could easily change the text of what you are quoting to make it misleading but still attributed to the original author. Also it would probably have been good to have this discussion when we asked for comments, now we are deep into implementation and did not get much feedback when asked for it :(
@tchambers This does not have anything to do with an FEP as it does not touch ActivityPub. Software implementors can already do that, but as I explained above it adds a lot of complexity.
For Mastodon, I think this will be a multi-month effort touching a lot of the codebase to allow this. It can be done, but not a priority right now.
@tchambers Yes, on-demand loading could be done here, but this is quite complex. It will be an asynchronous backend operation that might take multiple minutes (or never finish because the remote server cant be reached), and you will need to have proper UX around this in the client. We are slowly moving towards having some asyncronous background loading in Mastodon, but this adds yet another layer of complexity to everything.
@tchambers And then you would still have all of those accounts (and their data) in your DB, so now you need to refresh them periodically to ensure their data is up-to-date. Or you need to garbage-collect what is in your database to avoid it growing forever with "useless” data (a real problem already, this will make it worse), but this adds again a lot more complexity.
@tchambers It may solve one issue (ensuring the follow is valid), but you still need to fetch all the follower’s account into your instance, which may be a lot of them. Then would you fetch those user's own followers, recursively? You would end up with million of accounts stored (database, profile picture, banner, pinned posts & their media…) on every Fediverse server.