fuchsiaaaaaaaaaaaaaaaaa
quote tweets
while I get that it's a possible harassment vector, it seems only marginally easier than sharing a link or a screenshot of a toot?
something i think properly implemented QTs would add though is that they can re-use the toot-dereference/signing logic a boost has for example, so a remote instance you have blocked still won't be able to quote toot you, or see the toot a qt is referring too (because it always has to contact your instance for the content, and it'll just say no
re: quote tweets
@Cyborgneticz yeah...
we're cautiously researching them for GoToSocial, but we'll only implement something in this vein if we're absolutely sure it's good, and keep community in the loop
re: quote tweets
@f0x Makes sense
Oh Website Boy
re: quote tweets
@f0x does any fedi software actually implement a thing where the fetching post contents is authenticated and not just with any key? Like, it seems a bit pointless to me to stop an instance I blocked from fetching my public posts when they are … public?
re: quote tweets
@yuka what do you mean? requests are signed so they're verifiable to a remote instance, and if you block them (or have something like an allowlist that doesn't include them) the request won't succeed
quote tweets
@f0x I worry Website Boy would fuck this up