5 ms·

I remember having to fight a mod for him to restore a reply penned by Mike Pall, to a LuaJIT question. Mike Pall is the author of LuaJIT. The reply had been e

by pygy_ 2mo ago

I remember having to fight a mod for him to restore a reply penned by Mike Pall, to a LuaJIT question. Mike Pall is the author of LuaJIT. The reply had been either deleted or edited to the point of being wrong (memory is foggy), because Mike Pall wasn't an expert at SO, and had somehow not used the site exactly as intended. The mod was very dismissive and patronizing.

20k 2mo ago
I was going through some answers on a stackoverflow thread, and noticed that every single one had been edited by the same guy, just.. adding his own personal opinions and 'corrections' to them, and in the process making them universally worse and less correct The idea that answers should be editable, and the gamification of stackoverflow, was an absolutely terrible combination
- xxs 2mo ago
  Editing used to be fine, back then like 15-16y ago. Personally I posted mostly everything as community wiki (no reputation gain) as I got the mod-alike reputation anyways. At some point the (say 2013-2014 or so) the site deteriorated quite massively, though - as folks considered stackoverflow CV worthy material...
- jay_kyburz 2mo ago
  The gamification was a key reason the site became popular, but as the site grew, the rules and game mechanics did not evolve. An edit that made a response worse should have knocked the mod down so that they were unable to mod any more. The quality of the edit should have been determined by the original author. "Did this edit make your question better?" Moderators should have been ranked and scored based on their ability to help and welcome new users. It should have been very costly for them to make a new users feel unwelcome.
  - rcxdude 2mo ago
    Being able to edit answers isn't even a mod thing. In fact, for most of SO's life, it wasn't even a 'being logged in' thing (you could just edit an answer anonymously). How they wound up with a Q and A site where you could edit another user's answer far more easily than leaving a comment on it I still will never fully understand. (this kind of thing IMO really added to the utterly arcane set of rules and conventions that makes it feel so inaccessible)
    - zahlman 2mo ago
      You could not unilaterally edit anonymously; your edit would have been put in a review queue. It is good that leaving comments is hard. First off, because it was learned repeatedly, the hard way, that removing that barrier leads to ungodly amounts of literal spam. Second because even insightful comments detract from the main intended flow of using the site, which is: you find a question from a search engine, read the question and verify that it reflects what you're trying to figure out, then scroll down to the answers and learn something. The entire point is to not be a discussion forum (which is also why comments were not threaded for most of the the site's life). In fact, the site came into existence specifically because of frustration with what ends up happening on a discussion forum where people can discuss endlessly.
      - rcxdude 2mo ago
        See, what you're saying makes some logical sense in a vacuum but it's so utterly unlike how any other website works that unless you take a huge amount of effort to explain this to people, gently, then it's not at all surprising that people just bounce off of it.
        zahlman 2mo ago
        > but it's so utterly unlike how any other website works that unless you take a huge amount of effort to explain this to people, gently, then it's not at all surprising that people just bounce off of it. It is, and that's fine. It's incompatible with a site becoming large; and that, too, is fine. A large site was not required to accomplish any of Atwood or Spolsky's goals aside from perhaps making a profit off of ads. Many other choices were also counterproductive to the goals aside from profit. Everyone involved would have loved to "explain this to people gently". There was no space provided in which to do it. We had no access to modify the help pages or do anything about user onboarding flows. Downvotes were the tool provided to de-emphasize things and take them out of the way, and to rate quality; so they were used appropriately. (Despite this, and despite public perception, voting was historically very biased in the positive direction.) Because new questions were open by default, they had to be closed explicitly and in public in order for them to be dealt with. People walked away with the completely incorrect impression that closing a question is inherently a rejection; the explicit purpose and sole effect of closing a question is to prevent answers unless and until it is fixed. It is done with an explicit expectation that fixable questions will get fixed; but the nature of some problems (in particular: missing information) is such that only the OP can do this. There was a period of time in which "closed" was rebranded as "on hold" in the interface, to try to impress upon people that no, they aren't being turned away, they are being asked to take further action. But this was reverted because it was somehow apparently making things even worse. But also, yes, after telling countless people the same things daily, sometimes humans lose their ability to be gentle. But nobody who's dealt with roughly ever gets to see what the other side had to deal with earlier. The way that people talk about "toxicity" on Stack Overflow comes across like they think it was constantly full of insults and slurs. The evidence shows that the large majority of that sort of content (which explicitly violated the Code of Conduct, and there was a full system in place to deal with this, that pundits often ignore or even lie about) was directed at the curators. One of the most common questions on the meta site is "why aren't people required to explain downvotes?", with the main retort being "why don't you think they should be required to explain upvotes?". But the main answer to that question is because people who stuck out their necks to try to explain the site's standards politely, would frequently get sworn at and even threatened. (I was once openly called sexist for applying these standards, with no evidence beyond the fact that the OP was a woman, which I didn't know at the time).
  - zahlman 2mo ago
    > An edit that made a response worse should have knocked the mod down so that they were unable to mod any more. Literally everyone on the site is permitted to propose an edit, and everyone with at least 2000 reputation can make unilateral edits. The proposals are approved by a 2 out of 3 majority of random unilateral-edit-privileged users. None of this is considered "moderation" and is not done by "mods". Of millions of Stack Overflow accounts, only a few dozen have ever actually been moderators, and they do a tiny share of curation. Their main job is responding to flags. > It should have been very costly for them to make a new users feel unwelcome. The overwhelming majority of people who came to the site wanted the site to be something that it was fundamentally not trying to be, and often something it was fundamentally trying not to be. It was correct to make such users "feel unwelcome", because experience has shown that they typically cannot be reasoned with or explained to. The statistics make it clear that most of them never had any intention of trying to join a community (or, say, ask another question after the one that motivated account creation) in the first place.
    - amanaplanacanal 2mo ago
      So they have essentially killed the site. Congratulations I guess?
      - psd1 2mo ago
        What killed it in truth was RAG, but let's stipulate that it was policy that drove users away. The thing that killed it was the thing that made it prominent. According to a blogpost i can't find any more about "how to speedrun social media" or similar, it's basically impossible to pivot a community once established given the levers of voting mechanics and mod policy. (I distinguish between Facebook's and Reddit's enshittification and a pivot.) IOW, the seed of a community property's growth is also the seed of its decline. Analagously, the charming village is attractive to new residents because the existing residents resist the changes that new residents embody. Very broadly and by no means universally: techies don't like lusers, because lusers don't put effort into understanding, they just want turnkey answers. This is totally counter to the archetypal techie value system. SO optimised for grumpy misanthropes over bumbling newbies, which, in tech, is roughly congruent with optimising for people with knowledge to share over people who want their homework done for them. The questions are not the scarce resource - you can browse Microsoft Community Answers to verify that. The answers there are correspondingly useless, which is why "blindly copy from SO" is a meme and "blindly copy from Microsoft Answers" is not. Here ITT, and more generally on HN, comments are excoriating about the cost of being offputting to new users. Those commenters should recognise that it's not a pure cost, it's a tradeoff, and the upside has been a treasure for a decade. A million projects completed by people who found quality answers, mostly by searching for existing questions. That resource is still relevant for stacks other than the latest web framework hotness, and i personally still get benefit from it in my archaic hobby of learning to code. That resource is not still directly relevant for coders deeply plugged into AI, but it did train that AI. It's one of the most successful endeavours on the web and a towering community achievement. It is a superficially a shame that people experienced gatekeeping, but if "gatekeeper" has only negative connotations in your lexicon, then I advise you to compromise your principles and firewall your network.
- kstrauser 2mo ago
  I reverted nearly every single edit to my answers other than obvious typos. If I’d have meant something other than what I said, I’d have said it. You want to see your own words on the page? Write an answer of your own. Lordy, that use to piss me off most fiercely. I don’t want someone else’s words attributed to me.
  - zahlman 2mo ago
    It is taken very seriously in Stack Overflow editing policy that edits are not supposed to go against the author's apparent intent. But it does involve removing a lot of things that you might want the answer to say, but don't meet the guidelines for what answers are supposed to contain. When you join the site, you agree to Terms and Conditions that, among other things, grant a Creative Commons license to the community over your contributions, which gives them the right to make those edits. The site is explicitly not trying to accommodate people who want to say things in a specific way because it's their way of saying it. The site is explicitly trying to accommodate people who want to collaborate to produce a polished, coherent work of reference. If that isn't you, unironically, that's what tech blogs are for. People with the attitude you demonstrate here are consistently among the worst-behaved and hardest-to-deal-with participants on the meta site, because of a stubborn refusal to accept a core principle of the site. (Yes, the reputation system was an unfathomably bad design choice in light of the site's goals. In retrospect I genuinely don't understand how it survived past 2011 or so with tweaks as minor as it got.)
    - kstrauser 2mo ago
      That's ridiculous and you're wrong. I grant them a CC license to my content to fold, spindle and mutilate it for their own purposes, but not to leave my name attached to the folded, spindled, mutilated version. My answer has my name on it. It's right there saying "kstrauser said these words". If I didn't say them, I don't want the site lying and saying that I did. I don't mind if someone fixes an obvious typo, or updates a URL that had bitrotted. That's fine. They're what I obvious intended to say. But I've had people add extra sentences or paragraphs, and oh hell no. That was never a core principle of the site, at least not when I joined it before you. If it'd been an expressed core principle that people could edit my words, attributed to me, so that my user account ends up saying things I never said, I never would have signed up and not many other people would have, either.
kazinator 2mo ago
These kinds of incidents always remind me of https://wiki.c2.com/?KornShellStory https://wiki.c2.com/?KornShellStory

by pygy_ 2mo ago

20k 2mo ago

I was going through some answers on a stackoverflow thread, and noticed that every single one had been edited by the same guy, just.. adding his own personal opinions and 'corrections' to them, and in the process making them universally worse and less correct The idea that answers should be editable, and the gamification of stackoverflow, was an absolutely terrible combination

xxs 2mo ago
Editing used to be fine, back then like 15-16y ago. Personally I posted mostly everything as community wiki (no reputation gain) as I got the mod-alike reputation anyways. At some point the (say 2013-2014 or so) the site deteriorated quite massively, though - as folks considered stackoverflow CV worthy material...
jay_kyburz 2mo ago
The gamification was a key reason the site became popular, but as the site grew, the rules and game mechanics did not evolve. An edit that made a response worse should have knocked the mod down so that they were unable to mod any more. The quality of the edit should have been determined by the original author. "Did this edit make your question better?" Moderators should have been ranked and scored based on their ability to help and welcome new users. It should have been very costly for them to make a new users feel unwelcome.
- rcxdude 2mo ago
  Being able to edit answers isn't even a mod thing. In fact, for most of SO's life, it wasn't even a 'being logged in' thing (you could just edit an answer anonymously). How they wound up with a Q and A site where you could edit another user's answer far more easily than leaving a comment on it I still will never fully understand. (this kind of thing IMO really added to the utterly arcane set of rules and conventions that makes it feel so inaccessible)
  - zahlman 2mo ago
    You could not unilaterally edit anonymously; your edit would have been put in a review queue. It is good that leaving comments is hard. First off, because it was learned repeatedly, the hard way, that removing that barrier leads to ungodly amounts of literal spam. Second because even insightful comments detract from the main intended flow of using the site, which is: you find a question from a search engine, read the question and verify that it reflects what you're trying to figure out, then scroll down to the answers and learn something. The entire point is to not be a discussion forum (which is also why comments were not threaded for most of the the site's life). In fact, the site came into existence specifically because of frustration with what ends up happening on a discussion forum where people can discuss endlessly.
    - rcxdude 2mo ago
      See, what you're saying makes some logical sense in a vacuum but it's so utterly unlike how any other website works that unless you take a huge amount of effort to explain this to people, gently, then it's not at all surprising that people just bounce off of it.
      - zahlman 2mo ago
        > but it's so utterly unlike how any other website works that unless you take a huge amount of effort to explain this to people, gently, then it's not at all surprising that people just bounce off of it. It is, and that's fine. It's incompatible with a site becoming large; and that, too, is fine. A large site was not required to accomplish any of Atwood or Spolsky's goals aside from perhaps making a profit off of ads. Many other choices were also counterproductive to the goals aside from profit. Everyone involved would have loved to "explain this to people gently". There was no space provided in which to do it. We had no access to modify the help pages or do anything about user onboarding flows. Downvotes were the tool provided to de-emphasize things and take them out of the way, and to rate quality; so they were used appropriately. (Despite this, and despite public perception, voting was historically very biased in the positive direction.) Because new questions were open by default, they had to be closed explicitly and in public in order for them to be dealt with. People walked away with the completely incorrect impression that closing a question is inherently a rejection; the explicit purpose and sole effect of closing a question is to prevent answers unless and until it is fixed. It is done with an explicit expectation that fixable questions will get fixed; but the nature of some problems (in particular: missing information) is such that only the OP can do this. There was a period of time in which "closed" was rebranded as "on hold" in the interface, to try to impress upon people that no, they aren't being turned away, they are being asked to take further action. But this was reverted because it was somehow apparently making things even worse. But also, yes, after telling countless people the same things daily, sometimes humans lose their ability to be gentle. But nobody who's dealt with roughly ever gets to see what the other side had to deal with earlier. The way that people talk about "toxicity" on Stack Overflow comes across like they think it was constantly full of insults and slurs. The evidence shows that the large majority of that sort of content (which explicitly violated the Code of Conduct, and there was a full system in place to deal with this, that pundits often ignore or even lie about) was directed at the curators. One of the most common questions on the meta site is "why aren't people required to explain downvotes?", with the main retort being "why don't you think they should be required to explain upvotes?". But the main answer to that question is because people who stuck out their necks to try to explain the site's standards politely, would frequently get sworn at and even threatened. (I was once openly called sexist for applying these standards, with no evidence beyond the fact that the OP was a woman, which I didn't know at the time).
- zahlman 2mo ago
  > An edit that made a response worse should have knocked the mod down so that they were unable to mod any more. Literally everyone on the site is permitted to propose an edit, and everyone with at least 2000 reputation can make unilateral edits. The proposals are approved by a 2 out of 3 majority of random unilateral-edit-privileged users. None of this is considered "moderation" and is not done by "mods". Of millions of Stack Overflow accounts, only a few dozen have ever actually been moderators, and they do a tiny share of curation. Their main job is responding to flags. > It should have been very costly for them to make a new users feel unwelcome. The overwhelming majority of people who came to the site wanted the site to be something that it was fundamentally not trying to be, and often something it was fundamentally trying not to be. It was correct to make such users "feel unwelcome", because experience has shown that they typically cannot be reasoned with or explained to. The statistics make it clear that most of them never had any intention of trying to join a community (or, say, ask another question after the one that motivated account creation) in the first place.
  - amanaplanacanal 2mo ago
    So they have essentially killed the site. Congratulations I guess?
    - psd1 2mo ago
      What killed it in truth was RAG, but let's stipulate that it was policy that drove users away. The thing that killed it was the thing that made it prominent. According to a blogpost i can't find any more about "how to speedrun social media" or similar, it's basically impossible to pivot a community once established given the levers of voting mechanics and mod policy. (I distinguish between Facebook's and Reddit's enshittification and a pivot.) IOW, the seed of a community property's growth is also the seed of its decline. Analagously, the charming village is attractive to new residents because the existing residents resist the changes that new residents embody. Very broadly and by no means universally: techies don't like lusers, because lusers don't put effort into understanding, they just want turnkey answers. This is totally counter to the archetypal techie value system. SO optimised for grumpy misanthropes over bumbling newbies, which, in tech, is roughly congruent with optimising for people with knowledge to share over people who want their homework done for them. The questions are not the scarce resource - you can browse Microsoft Community Answers to verify that. The answers there are correspondingly useless, which is why "blindly copy from SO" is a meme and "blindly copy from Microsoft Answers" is not. Here ITT, and more generally on HN, comments are excoriating about the cost of being offputting to new users. Those commenters should recognise that it's not a pure cost, it's a tradeoff, and the upside has been a treasure for a decade. A million projects completed by people who found quality answers, mostly by searching for existing questions. That resource is still relevant for stacks other than the latest web framework hotness, and i personally still get benefit from it in my archaic hobby of learning to code. That resource is not still directly relevant for coders deeply plugged into AI, but it did train that AI. It's one of the most successful endeavours on the web and a towering community achievement. It is a superficially a shame that people experienced gatekeeping, but if "gatekeeper" has only negative connotations in your lexicon, then I advise you to compromise your principles and firewall your network.
kstrauser 2mo ago
I reverted nearly every single edit to my answers other than obvious typos. If I’d have meant something other than what I said, I’d have said it. You want to see your own words on the page? Write an answer of your own. Lordy, that use to piss me off most fiercely. I don’t want someone else’s words attributed to me.
- zahlman 2mo ago
  It is taken very seriously in Stack Overflow editing policy that edits are not supposed to go against the author's apparent intent. But it does involve removing a lot of things that you might want the answer to say, but don't meet the guidelines for what answers are supposed to contain. When you join the site, you agree to Terms and Conditions that, among other things, grant a Creative Commons license to the community over your contributions, which gives them the right to make those edits. The site is explicitly not trying to accommodate people who want to say things in a specific way because it's their way of saying it. The site is explicitly trying to accommodate people who want to collaborate to produce a polished, coherent work of reference. If that isn't you, unironically, that's what tech blogs are for. People with the attitude you demonstrate here are consistently among the worst-behaved and hardest-to-deal-with participants on the meta site, because of a stubborn refusal to accept a core principle of the site. (Yes, the reputation system was an unfathomably bad design choice in light of the site's goals. In retrospect I genuinely don't understand how it survived past 2011 or so with tweaks as minor as it got.)
  - kstrauser 2mo ago
    That's ridiculous and you're wrong. I grant them a CC license to my content to fold, spindle and mutilate it for their own purposes, but not to leave my name attached to the folded, spindled, mutilated version. My answer has my name on it. It's right there saying "kstrauser said these words". If I didn't say them, I don't want the site lying and saying that I did. I don't mind if someone fixes an obvious typo, or updates a URL that had bitrotted. That's fine. They're what I obvious intended to say. But I've had people add extra sentences or paragraphs, and oh hell no. That was never a core principle of the site, at least not when I joined it before you. If it'd been an expressed core principle that people could edit my words, attributed to me, so that my user account ends up saying things I never said, I never would have signed up and not many other people would have, either.

kazinator 2mo ago

These kinds of incidents always remind me of https://wiki.c2.com/?KornShellStory https://wiki.c2.com/?KornShellStory