I find it interesting that the current StackOverflow moderators tend to say "in the past we used to accept too many questions but it was never the goal, so now we are doing it as it was meant to be".
Sure, but in the past, StackOverflow was growing, and now it's dying. Maybe something was better before, when "it was not done correctly"?
I think these sorts of things are just an unfortunate side effect of scaling. The bigger you get the more people get lost in the bureaucracy. However if you don't build up the bureaucracy the system collapses under its own popularity.
Wikipedia has a similar issue where editing declined around 2007, which is often blamed on stricter enforcement of rules, more complex rules, etc. I think its just a natural stage of growth. You can't be a free for all forever.
The "good" thing is, they're back to 2009 levels of postings. Now obviously that's what the mods let through but my guess is that traffic to the site is down precipitously as well. They can roll back their bureaucracy and head back to a lean path that worked for them in the past.
But I don't really think that's the problem. Reading zahlman's responses in this thread makes me think that the mods fell into the age old trap that's happened since Usenet, IRC, and still happens to this day wherever there's mods: they got tired of doing unpaid labor and instead of deciding to quit decided to become meaner and stricter. The age old mod trip.
> Sure, but in the past, StackOverflow was growing, and now it's dying. Maybe something was better before, when "it was not done correctly"?
You're presuming that the current volume of questions represent novel, unique posts instead of something you can find over and over again if you do a decent query.
Overwhelmingly, the people you're talking about are not moderators. I explained this to someone else a week ago (https://news.ycombinator.com/item?id=43927665) and you replied to that comment.
> Sure, but in the past, StackOverflow was growing
So what? Stack Overflow users get $0.00 for this, whether they're moderators, active curators or just signed up. For users, growing the site isn't the goal. Growing interaction with the site is not the goal. The goal is building a useful artifact (https://meta.stackoverflow.com/questions/254770). This frequently entails removing, closing or duplicating questions, for the same reason that building a useful program frequently entails removing lines of code, deprecating parts of the API, and refactoring.
> and now it's dying
Why should a reduction in incoming questions mean that it's "dying"?
> Maybe something was better before
Who do you think should get to decide what's "better" here? More importantly, why?
If the YC team decided to prioritize increasing site traffic (and introduce ads to capitalize on that) on HN and maximizing the rate of new submissions, at the expense or ignorance of the quality of the discussion, that would be clearly be bad, right? You'd leave, right? I would.
The same principle applies to sites that aren't about having a discussion. Bigger is not better.
> Overwhelmingly, the people you're talking about are not moderators.
I was actually thinking about you. You keep saying everything is great. My observation is that I used to be on SO every day, and I completely stopped contributing even though I would have plenty of stuff to add (more than ever, actually).
> Why should a reduction in incoming questions mean that it's "dying"?
There is "a reduction", and there is "being back to the amount of questions SO had in 2009 when it launched".
I say it's fine, because it is. I say that a reduction in question volume has advantages in terms of accomplishing the site's goals, because it does.
There are many things about the site that I'm unhappy with, mainly to do with initiatives the staff are taking that are also very much not true to the site's goals or purpose.
> My observation is that I used to be on SO every day, and I completely stopped contributing even though I would have plenty of stuff to add
... And?
> There is "a reduction", and there is "being back to the amount of questions SO had in 2009 when it launched".
If the amount of questions went to zero per day I would still not consider this a problem. It would be an opportunity to refine the existing publicly visible questions.
As a reminder: there are already more than three times as many of those as there are articles on Wikipedia. You say it's a problem that we don't see thousands more per day like we used to. I say it's a problem that we already have so many; and that if we had perhaps a tenth as many, it would become easier to find what you want.
> If the amount of questions went to zero per day I would still not consider this a problem.
So on the one hand you find it okay to delete old questions, and on the other hand you find it okay to not add new questions. But it's not dying.
> it would become easier to find what you want.
It has never happened to me that I could not find what I wanted on SO because there were too many similar questions. It has happened, though, that I could not find what I wanted because it was not there. And when I added it, I was closed by people who obviously had no understanding of my question (together with its answer).
Again, I am not saying that it should be forbidden to close questions. What I am saying is that SO has become a place where even good questions get closed. By people who know better, like you.
> It has never happened to me that I could not find what I wanted on SO because there were too many similar questions.
Back when I was trying to sort out the mess more actively, it happened to me daily. I distinctly recall multiple instances of spending hours at a time tearing my hair out over it, and complaining in the corresponding chat about the terrible questions, the unintentional clickbait, and the sensitivity of search engines to minor variations in the query.
> closed by people who obviously had no understanding of my question (together with its answer).
This is said by perhaps 90% of people complaining about their question being closed, and trivially shown to be incorrect in perhaps 90% of those cases.
But also, "people can't figure out what you're trying to ask" counts against your question. By design. Because questions are expected to communicate clearly. So that other people who read them don't have to waste their own time making sure they're in the right place.
Of course, there are other reasons a question might not be understood. But it's not hard to distinguish between "this person can barely write coherent English" and "I don't know anything about this technology". People are, broadly speaking, just not going around the tags for technologies they don't know about in order to close questions. What on Earth would they get out of that?
> What I am saying is that SO has become a place where even good questions get closed. By people who know better, like you.
Again: please show a link to an example of a question that you believe was unjustifiably closed, and make sure that you can clearly explain, in terms of existing policy why you believe the closure was invalid.
And why are you the one who gets to make this judgment?
the reality makes this judgment. something that was worth billions of dollars could probably be bought for $50m (this is too much…). a definition of dead
I don't think that is relevant, either. Nobody who asks or answers a question on Stack Overflow, nor comments, nor edits an existing post, does so with the specific intent of increasing the market cap of Stack Exchange, Inc.
AFAICR they've always said these lines about now is about better moderation from the slop. The reality is that the rule of thumb for that moderation was already out of date with advances that preceeded LLMs.. Even with the beginnings of computer aided flows we didn't need to alienate most to get the best content and develop the few. Content can be triaged from someone who may be human to others who may be human and maybe there's value or maybe you just didn't alienate anyone and some people will still climb to making higher levels of content that is worth condensing.
> Even with the beginnings of computer aided flows we didn't need to alienate most to get the best content and develop the few.
The large majority of new questions from new accounts are from people who are clearly there only to solve a personal problem, who show no interest in considering the value of their question to third parties, and rarely put any effort into attempting to even diagnose or specify a problem.
Even after it became possible for most of these people to get an instant answer from an LLM. Which is actively preferable from the standpoint of Stack Overflow curators. Before LLMs, the point was for them to use a search engine to find an existing question that lets them figure out the problem. But for the Q&A to help such users, they need to apply at least basic problem-solving and debugging skills. (It is explicitly out of scope for the Stack Overflow community to do that for others; and attempting to do this in an answer actively degrades the site for everyone else.) If an LLM can fill in some hypotheses for those users to test, then the LLM is doing what it's best at, and Stack Overflow is doing what it's best at.
Stack Overflow is not there to troubleshoot or debug anything for you, nor to reason about a multi-step problem and break it down into its natural logical steps. It's there to give a direct, objective answer to how to do each individual step, and to explain why the specific point of failure in a failing program fails, after you have identified it and made the problem reproducible.
So yes, we absolutely do need to "alienate most", because "most" are there for a reason that has absolutely nothing to do with getting the best content.
> So yes, we absolutely do need to "alienate most", because "most" are there for a reason that has absolutely nothing to do with getting the best content.
How many of the "desirable" contributors did you alienate in the process?
I may be naive, but when people say "I have been using SO for 10 years but it has become toxic so I left", it doesn't sound like new accounts asking for their homeworks.
The people who have been around for 10 years or so who disagree with the basics of question closing policy (or who act without any apparent awareness of it) are even worse than the people seeking a quick fix for their problem. Because they flood the site with inherently low-quality answers to low-quality questions. In doing so, they dilute higher quality content (it becomes harder to find with search engines, because search engines have no way to understand our internal quality rating systems) and incentivize the quick-fix-seekers. Both sides of that are ignoring policy and acting against the site's goal.
When people describe something as "toxic" I generally consider this to be content-less without further elaboration. It doesn't concretely describe what is supposedly wrong - it only dramatizes the complaint.
> The people who have been around for 10 years or so who disagree with the basics of question closing policy [...] Because they flood the site with inherently low-quality answers to low-quality questions
I see that you just don't hear the complaints.
I don't hear people who have been around for 10 years or so complaining because they can't answer to low-quality questions.
> I don't hear people who have been around for 10 years or so complaining because they can't answer to low-quality questions.
Because they usually can. There aren't enough curators paying attention. Stopping them generally requires three curators to find the same question and act on it before an answer is posted. And the person writing the answer also gets a grace period for in-flight answers.
Then when they finally get inconvenienced, they come to the meta site and make perhaps their first attempt in over 10 years to even find out what the policy is. Often they have a bad experience with this, loudly complaining as if they already know the policy while never having made any attempt to learn it, and being surprised to find out they're wrong. Sometimes they even try to make a meta post on the main site.
I wonder if I can't write coherent English, or if you can't understand it. You keep fighting to not understand what people complain about.
They complain about good questions being closed, you say "that's because they are bad questions". They say that they don't complain about bad questions being close, you say "that's because we don't close bad questions".
Sure sounds like you don't really know what you are trying to say other than "we are great".
Antisocial people flood the site with low quality answers to low quality questions and not indexing everything to the web is just too hard.. Imagine if every town and school was filled with the same pricks? Your kids are stupid and don't understand PhD level research so they should shut up.
It's all very logical for an older time when global communication was the kind of thing you needed to reserve for the top researchers as your total capacity was less than humanity needed. But now you are just repeating the mantras of older generations in an antisocial way.
I use Yubikeys as my passkeys, and in terms of security it's strictly superior to passwords.
> seemingly no one besides maybe Bitwarden supports exporting them. Which seems pointless, because I don't know of any platform that supports importing them
That may still change in the future :-). The thing is that the technology allows it, which is good, right?
Actually it is a feature. The whole point of the Yubikey is that you can't extract the key. Syncing keys would mean extracting them, which would defeat the purpose of the Yubikey.
Now I am not saying that it is a feature you want. That's why there are other kinds of passkeys. My point is that it is not a flaw in Yubikeys, it is by design.
There's a critical flaw in PGP actually. If you reply to any PGP encrypted email with "sorry, I couldn't decrypt" you'll, with high likelihood, get the cleartext version of the email soon after.
The joke is quite old and part of what I'm pointing to. Security doesn't work well if it isn't very usable. At least this is a bit better than secure communication, but it isn't as huge of a difference as it might appear.
The biggest boon in security has come due to making these tools easy to use. That's from decades of experience is realizing you can't get everyone to be technical.
> Brunelleschi's dome on the Florence Cathedral was the first major dome built in Europe in over a thousand years since the fall of the Western Roman Empire.
I don't think it necessarily means they forgot how to do it, though. Or does it? We too stopped building domes made of big stones, it doesn't mean we don't know how to do it.
For whatever reason they weren't building domes anymore in Europe where they had been (the fall of the Western Roman empire sort of changed priorities for a while). And after a generation of not building domes the artisans (in Europe) lost the ability to do it.
There's a much closer example: The US spent the 60s developing the capability to land humans on the moon. And they were successful. They did it about, what, 7 or 8 times? But then they stopped doing it. And now some 60 years later they're having a hard time doing it again (see the woes of NASA's Artemis and Boeing's Starliner). Imagine if the pause wasn't 60 years, but several hundred years.
I only want to add that's not something that we have a hard time doing because it suddenly became hard, but because it came out of fashion.
We had a really good time thanks to cold war and flexing between both sides, but now it's a just a enormous investment with no return. It's really sad to see NASA running on a shoe string budget, and Ingenuity being nothing more than a glorified student project that happened at the right time in the right place.
Nextcloud is about synchronising files. Some people may only sync media files, but surely you can imagine that others want to sync other files, right? It's not that crazy, Dropbox, GDrive, iCloud, etc. all do that.
Do you really think it seems unfair that a file sync app would want to access files?
And you can let it if they use Storage Access Framework to ask for that permission without them requiring blanket access to all your private data.
Perhaps you should get informed as well.
In the end this is again app developers refusing to do the work to protect privacy and trying to push through the laziest most privacy voilating solution because it's less work.
The person you are replying to has not denied anything you said, nor have they given any indication that they need to get informed. Your comment is wildly misplaced.
What did I say that was wrong? The comment I was answering to - that I assume you read - says: "This Nextcloud app seems to be [...] It isn't a file manager, it isn't a backup utility, it's a cloud provider with local mirroring."
Sure, but in the past, StackOverflow was growing, and now it's dying. Maybe something was better before, when "it was not done correctly"?
reply