Charlie StrossDec 24, 2022
@annaleen is absolutely right when she says this, and here's a demonstration. I mean, OCR of screecaps is literally an OS-provided service these days:
Show threadSteven L. JohnsonDec 24, 2022
@cstross @annaleen Hmmm... isn't your screen cap a pull quote from a longer thread? A longer thread that I don't know how to get to because there's no link back to the original context?
Show threadSteven L. JohnsonDec 24, 2022
@cstross @annaleen An advantage of a QT is it provides both recontextualization of an information source to an expanded audience *and* it provides a link back to the original context
Show threadAnnalee Newitz 🍜Dec 24, 2022
@steven @cstross You can also include a link with a screenshot. It's not hard to cut-and-paste some text.
Show threadSteven L. Johnson

@annaleen @cstross Agreed, adding a link would address provider a pointer back to original context. And, it's great that Mastodon has an edit button so @cstross can go back and add the missing link.

It sounds like we are in agreement as to what a good QT looks like... so I guess the question then is: should it require a multi-step error-prone manual process or should it be implemented more directly as a standard client feature to ensure all those elements are there in every QT?

Dec 24, 2022 at 8:31pmWeb
Show threadAnnalee Newitz 🍜Dec 24, 2022
@steven @cstross I would prefer the multi-step process, the friction, to prevent easy drive-by pileons. errors aren't an issue, as you already pointed out, because we can edit.