@julian Interesting. Thank you.
…
I was writing a reply, and in all honesty went to check versions only to find I’m using “Tusker” and realized I lost track of which client I was using. My bad.
I get your point on it being a client implementation.
@julian Interesting. Thank you.
…
I was writing a reply, and in all honesty went to check versions only to find I’m using “Tusker” and realized I lost track of which client I was using. My bad.
I get your point on it being a client implementation.
I do wish, from the mastodon side, I knew whether there was something quoted or not.
I built a manual tool that can tell me (it also builds a blob of the quoted post that I can paste back to mastodon), but opening every bridged post in that tool when text doesn't make sense gets a bit old.
(Context note: I use tusky for mastodon most of the time and it doesn't have or show the "RE:" link that the mastodon web client shows.)
I have been subscribed to that github issue a while too. 
From what I saw quoted -- equipment already fcc certified is safe thankfully.
(Unless they clarify in a different way.)
@SwiftOnSecurity (that is what I usually say, yes. Worth it sometimes. But yeesh.)