@moehrenfeld I think most people think as you do right up until the function is weaponized against them. IMHO it is an opinion that helped ruin BirdChan. ‘I want what I want when I want it’ is a bad reason to further implement a feature to which a huge chunk of Mastodon is opposed. 1/2
@moehrenfeld 2/2 I don’t care that your feed was peaceful. I care about those who were hurt by it’s use. Until you can protect my right to consent to its use for my posts, until you can prevent its use for doxxing I will oppose further implementation. Proactive consent, my right to be safe, is part of what makes this place so special.
@moehrenfeld ‘Everyone else is doing it’ is an interesting take on Holocaust Memorial Day. Then wrapping it up with the tech version of‘thoughts & prayers’ is, honestly, bs. We (as in early Twitter users) created a lot of stupid things that we do not have to repeat here. And since I started in 2007 I blame myself too. Here’s an interesting notion: instead of saying you care, actually care.
@bed to assume that there will be real debate in which the pro-QT side would actually stop their push to implement is either deliberately disingenuous or incredibly naive.
And the holocaust didn’t spring up overnight. It happened one day at a time. One ignored wrong at a time. The tool as currently implemented removes a core principle of Masto: proactive consent. And that is worth fighting for.
@bed @LucyWildboots @moehrenfeld @_Jordan @gruber
“Quote tweeting is just like genocide because I don’t like either of them.”
“Blocking quote tweets will prevent doxxing.”
“The community is opposed to it, I speak for all of them.”
“Consent must be given for linking to a public web page.”
Kind of impressive how far people have to bend over backwards to argue against this and still make zero compelling points.
If you don’t like quote posts just don’t have one. 🤷🏻♂️
@MikeBeas This fixation on the Holocaust as being solely about the genocide is incredibly simplistic. When I made the reference I assumed my audience was sophisticated enough to understand that there were many bad choices and many steps that got the world to that point. My apologies for that assumption. 1/2
@MikeBeas oh good! We’re now at the mansplaining part of the argument.
@MikeBeas & we’re back to the Holocaust as a single event instead of a series of bad behaviors. I was never going to give you a reason you could accept because you don’t want to accept it.
Your only solutions are mansplaining the internet to a woman who’s first online game was MUD 1; a poor .gif post; & telling a significant group of people who disagree that they should go private because you can’t code well enough to find a real solution.
@MikeBeas are you referring to the picker for who can see my posts? If so, nice try but epic fail. Now if there was an actual setting that said “Allow QT” with the default being off I could live with that. And if you’re really so inept that I have to do a flow, then if you tried to QT my post you get a notice box telling you ‘users does not allow QTs of their material” I find it sad that all these codes can’t figure that out.
@bed I wish I had a flow chart app.
Settings -> Allow QT? - Yes/No default no
Poster tries to QT my post -> it is treated as an attachment -> Poster served info box ‘User does not allow QT’ -> attachment fails.
If they game the system I alert my sysop and the post is actioned.
@MikeBeas I get that you don’t like me for a whole list of reasons. That’s only fair since I think of you as an entitled white jerk. But now you ARE trolling and it’s childish. Just stop.
@MikeBeas at least it’s not repetitive or boring or dismissive or non-inclusive or arrogant or so sure that he’s right he couldn’t see the solution if it was laid in front of him. I asked you nicely to stop. I will ask you again: please stop, I’m feeling harassed.