-439

Update February 26th,2026

As was mentioned on February 20th, we have another post covering more of our thinking and plans on how we are going about improving question closure.


Update February 24th, 2026

The new Stack Overflow beta experience is now available. Users can visit the beta site directly at https://beta.stackoverflow.com/ or by clicking the "Try new site (beta)" toggle on stackoverflow.com.

We are currently in the process of rolling out and troubleshooting certain issues with the beta. Additionally, we wanted to proactively communicate the features not yet accessible on https://beta.stackoverflow.com/. As we continue to make updates to the beta site, please use the classic site to access these features:

  • Viewing comments on a question, or adding a comment on a question
  • Editing posts
  • General purpose moderation tooling
  • Changing your vote on a post (except for the default Troubleshooting / Debugging type questions)
  • Viewing most post notices
  • Real time notifications without reloading the page (updates on a post, inbox notifications, etc.)
  • Changing the list of one's Communities in left navigation menu
  • Certain actions on a post like Follow, Save, Start a bounty, etc.
  • Staging Ground

Update February 20th, 2026

We’d like to clarify the announcement that review queues and question closure will not be going away for the time being. We do believe that curation is important. It has been central to what makes Stack Overflow valuable. Removing all review queues or curation altogether is not the direction we currently plan to go. We also want to have more flexibility in the content we allow and make our experience more welcoming. We do believe that there's room for improvement on how site curation is implemented and plan to work more collaboratively with the community on the best way forward. You can expect to hear more from us by February 26th, 2026 to learn more.

As we roll out the beta, we'll continue to add in features. The review queues and question closure will not be a part of the initial release, but will be included in the scope of the overall redesign and will be incorporated as the beta graduates to general availability.


Last July, we announced a redesign of Stack Overflow. In October, we shared a first look into the upcoming design changes and our reasoning behind them. After several rounds of discussion with the community, we’re happy to announce that the first stage of our redesign will soon be ready for you to try out.

Starting next week, head to beta.stackoverflow.com and try the first stage of the redesigned experience! We welcome your thoughts as we shift over to our new design and brand image. Details follow.


Three upcoming major milestones for the Stack Overflow redesign

The team has worked hard to bring you a new design for Stack Overflow, and we’re proud and excited to be able to share it with you soon.

We are breaking the release of the new design into three major milestones:

  1. Soft beta launch: Users will be able to try the site, but not all parts of the site will be built yet. We will continue to make updates, fix issues, and release updates and features on a rolling basis. During this phase, users will be able to switch between the beta site and the “classic” site experience. We’ll be here soon.
  2. Full beta launch: All major features of the platform that are on our roadmap will be implemented and converted over to the new design. Shortly after the full beta launch, we will begin automatically redirecting some users to the new design as we prepare to transition fully onto the new design. We’re targeting this release for around the end of March.
  3. Full release: Stack Overflow will switch fully onto the new design, which will be accessed directly on stackoverflow.com. After a full release, the “classic” site design will be decommissioned. A date for this phase has not yet been decided.

As for when network sites might see the new design, it’s far too early to speculate. We expect that work leading up to a release on Stack Overflow alone, as well as the work that will come after, will keep our arms full for a while to come. Network sites will probably see certain rebranding elements, such as a change in the Stack Overflow logo, in the coming weeks. Aside from these minor updates, however, we don’t expect to update the network this year. You’ll hear more from us once we’re ready to begin work on a network-wide rollout.

What should users expect during the soft beta launch?

During the early period of the beta test, the new Stack Overflow design is still being built. At the time of this release, only the homepage and question pages will be using the new design. We will be actively working to convert more pages over to the new design during the beta. We want to leverage this time for constructive feedback from the community while we are still on this new path.

Most pages that have not yet been converted to the new design will still be accessible through beta.stackoverflow.com; however, they will be using some of the base styles of the new design system. That means some pages may not work exactly as expected until they have been converted to the new design. This is normal and expected at this point in the process.

You will also notice that not all of the tools currently available to users on Stack Overflow have been implemented in the new design. (This includes moderator workflows – mods, please continue to use the main site for now.) We expect some of these tools to be built before full release. However, please note that we plan to retire certain curation workflows, such as close votes and most review queues, in the new design. Additionally, certain post states, such as posts with bounties, community wiki posts, or locked post states, do not yet have a way of being displayed in the new design. During the initial beta phase, posts with these states will be styled the same way as normal posts.

Finally, before full beta release towards the end of March, we expect that questions in the new beta experience will be displayed in a format more similar to that of opinion-based content because we believe it expands how people engage with Stack Overflow and how content is created and shared. We are seeing positive engagement with this format, and we want to continue to evolve it to include accepted answers.

How to provide feedback on the Stack Overflow beta

We are open to all feedback on the new design for Stack Overflow and hope to hear from you soon. You are welcome to provide feedback here on Meta Stack Overflow. There will also be a link in the left sidebar, which says “Help improve beta,” that you may use to submit bug reports, feature requests, and general feedback to the company. Look for this button once you have access to the beta:

Screenshot of the left sidebar menu with a button that is highlighted in a box that says "Help improve beta"

For bug reports and feature requests, please be aware that only the homepage and individual question pages are currently using the new design. Bug reports and feature requests concerning these two pages are our highest priority during the early release. We expect issues with the new design on pages that haven’t been fully implemented yet. That said, if you notice any serious issues on any page, we always encourage you to provide those reports as well.

When submitting bug reports and feature requests on Meta Stack Overflow, please ask a new question and tag it with . Please don’t use answers on this post to report bugs or request feature changes. We do not have a way to track our responses to reports in answers over the long term - we’re definitely going to want the ability to do that for this project. Asking a new question and tagging it appropriately helps us categorize questions and quickly respond to issues you raise. (If you forget, we’ll still try to keep an eye out, but a little help from you will make sure these issues don’t fall through the cracks.)

Discussion and general feedback is always welcome and belongs in answers on this post, in new questions, or using the feedback link on beta.stackoverflow.com mentioned above.

We know it can take time to adjust to design changes, especially when the site is so integral to many people’s workflows. Everyone has a chance to try it out now so we can put the most important work in over the next two months. We want to make sure that the classic version of Stack Overflow is still available to use until we’re ready to move over to the new format. We look forward to your feedback soon!

84
  • 95
    I’m upvoting because I like the principle of a beta launch and gathering feedback. But do I believe our feedback would make a difference? Let's just say that I’ve seen this movie before and I hate the ending. Commented Feb 18 at 16:28
  • 103
    Please stop asking for feedback. It will be ignored this time too. We do not want to give feedback. I had it with that ten feedback posts ago. Commented Feb 18 at 16:31
  • 228
    "please note that we plan to retire certain curation workflows, such as close votes and most review queues, in the new design" way to bury the lede... Commented Feb 18 at 16:31
  • 41
    Is there a discussion post about the new curation user experience, given the apparently planned removal of some of our most effective tools and workflows? Commented Feb 18 at 16:38
  • 146
    It's telling to casually hide a statement such as "we plan to retire certain curation workflows, such as close votes and most review queues" in a post about site design. Commented Feb 18 at 17:12
  • 30
    Well sure, in the traditional sense of "closing." But closing is our primary curation technique. Are we simply abandoning curation? Commented Feb 18 at 17:30
  • 40
    The last time you asked for feedback you (SOCorp) only responded to 3 out of 11 responses, given theres already 2 answers here it seems as though you've almost reached your feedback quota Commented Feb 18 at 17:56
  • 75
    Is there a point to this post? It's pretty clear you, as the company, will ignore all the feedback and do whatever you want anyway. Just like you've done repeatedly for the last few years. Do you not realize that it's your constant changes to SO making things worse that is driving away users? Complete cluelessness from the company. Commented Feb 18 at 20:13
  • 69
    @Hoid there is an appearance, that you are attempting to hide, what is one of the biggest changes in the history of the site as a 'design change'. If this is the place for feedback on the decision on curating workflows, that should be front and center. And expect to hit a new record for downvotes if it is. Commented Feb 18 at 22:56
  • 42
    @Hoid "Not to dismiss it, this is the time, place, and opportunity for discussion." This is a bit late considering you already have a roadmap and significant work to actually build that thing, isn't it? You're talking roughly one month here until you already have a full, alternative site live. How much of it is actually up for discussion, not just commenting? Commented Feb 18 at 22:59
  • 57
    @Hoid once again, you came to us asking for feedback when you have a plan, i.e. we plan to retire certain curation workflows. We gave you feedback regarding experiment with open-ended questions with more than 250 downvotes; what did you do with it? You are expanding it to the whole site. Fool me once, ... Commented Feb 18 at 23:43
  • 37
    @Hoid, I'm going to be polite and say this is a controversial proposal. If you want to get any feedback that is useful, and not leave both sides feeling ignored and frustrated, can you please clarify what has already been decided, and what can change based on feedback? Commented Feb 19 at 0:08
  • 121
    @Hoid: I think it would be really useful if you could explain why the crucial aspect of removing closure and various review queues has so little prominence in this post. Did you truly believe it was relatively unimportant, or were you trying to avoid attracting attention to it? Do you understand why this reduces the community's trust in the company? Commented Feb 19 at 9:17
  • 39
    The latest edit does not imbue confidence. Feels like when in Hitchhiker's Guide the Galactic Planning Council announced the scheduled demolition of Earth: "The process will take slightly less than two of your Earth minutes. Thank you." And then followed that up with, "don't panic, we are happy to take community feedback over the next two minutes." Commented Feb 21 at 8:53
  • 30
    I'd like to pile on my displeasure at the continuation of the company thinking / saying that traditional Q&A is just debugging questions. it's not. we've said this before, ex. here, and here, and I said this during a call with the product manager / designer of the opinion-based content experiment (having been invited- by you, hoid!, IIRC- to provide direct feedback). I'm quite frustrated at this point. it's as if I haven't been heard at all. and this is something pretty fundamental. Commented Feb 24 at 18:20

49 Answers 49

1
2
19

A minor aside:

we expect that questions in the new beta experience will be displayed in a format more similar to that of opinion-based content because it we believe it expands how people engage with Stack Overflow and how content is created and shared.

The new style questions expand how content is shared? What does that mean? That sounds like it might be a win. We all could use a win. Could you give more details on how the thread-style questions have been improving the sharing of content?

3
  • 21
    “Trust me bro...” Commented Feb 18 at 21:28
  • 3
    There is no deeper meaning behind the use of "shared" beyond its reference to how people share information as content. It's not alluding to someone posting about it on another platform or anything like that. Commented Feb 19 at 15:20
  • 3
    @Hoid OK, in that case I still wonder what about information sharing is improved by the display, in particular, of the opinion-based responses vs the Q&A answers. I can see that the new style functions, but other than that it looked more difficult to me. It's likely I'm missing something. Commented Feb 21 at 0:48
19

You bought a site because of its successful model that produced high quality answers that many people are looking for. Currently you don't try to hold this business model and integrate features; you try to transform the site into something no one came here for (and maybe ever will).

I really thought you had just been clumsy in designing a UI that includes space for additional content. But this announcement makes it obvious, you try to deport people into a new space they don't want to be in.

Even though I don't believe that these changes will have as much impact as you might wish them to have in attracting new users to join us, I do believe this (sometimes over-)curated site will become uncared-for and inevitably die.

4
  • Big tech GAFAM (=Google/Apple/Facebook/Amazon/Microsoft) are successful by buying the competitors less so by copying or destroying them. If you want a monopoly you better put up some money. Commented Feb 25 at 10:49
  • I think you made the mistake of assuming that the company even got a clue of what they are doing. They are just winging it. Commented Feb 25 at 11:51
  • @Lundin after an investment of 1.8b dollar I would suspect they should have a clue, but apparently they do not. Commented Feb 25 at 11:59
  • 5
    They already covered the entire loss of buying SO with the sale of the company that did recruitment for the Russian invasion of Ukraine. Between the different diverse branches such as programmer Q&A and war crimes against humanity, they made a net profit of $0.6 billion. SO is just peanuts, something to idly amuse yourself with while there are no massacres of civilians to watch on TV. Commented Feb 25 at 12:08
17

Users don't read. They scan.

(from Steve Krug’s book Don’t Make Me Think)

The new design breaks this golden rule and makes the page less scannable.

  1. The big bold number of upvotes sitting next the top of the answer is (was) an important signal wether I should even read the answer at all.

  2. Telling where the last comment ends and the next answer starts now involves tons of friction.

  3. etc...

Don't try to be reddit. People don't come here to talk.

By the way, there's a reason reddit has never replaced Stackoverflow. And the old UX design is a big part of that reason. But now that you look EXACTLY like reddit I guess I'll just go to reddit, since it looks identical anyway.

New contributor
Alex from Jitbit is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
2
  • 2
    It just occurred to me... "Don't try to be reddit" - well, unless that's exactly the goal? To add more "social" signals, inflate the engagement metrics, slap AI on top of it all, and then sell the whole thing. Also "Makes the page less scannable" - well, unless that's exactly the goal too? Unscannable wall of text drives up the engagement ("hey, number of scrolls has grown, average time spent on page too") and makes it easier to inject some ads? Gosh, I really hope I'm wrong. Commented yesterday
  • This will also be important later if non-SO sites lose the current scannable layout. Posting to Reddit usually gets more eyes on it—what advantages would we be left with? Please let's not lose the advantages we have. Commented 19 hours ago
16

This marks the first time I have ever posted an answer on Stack Overflow Meta. Normally, it would be a small but noteworthy personal achievement, a little memory tucked away that I could revisit later when feeling nostalgic.

Unfortunately, this also likely marks the last time I will ever post an answer on Stack Overflow Meta; allow me to explain why.

When I first joined Stack Overflow, it felt as though I had walked into a digital library containing a vast trove of technical knowledge, carefully organized and preserved by the giants who came before me. And now I, a newbie developer, could stand on their shoulders and pore over detailed answers to even the most basic programming questions. Later that day, I got stumped by a coding problem and eagerly headed off to SO with my crude search query, "remove item javascript array," only to discover someone asked the same question eight years earlier.

Except they had worded it more succinctly: "How can I remove a specific item from an array in JavaScript?" which explained the 40+ (as of 2019) unique answers. The sheer amount initially made me nervous, but I quickly noticed one answer stood out. It was the accepted answer, conveniently at the top of the list, and had over 10,000 upvotes. I quickly understood why: the explanation was thorough yet simple enough for me to understand, and it even had an example code block. I confidently returned to my code editor to apply my newfound knowledge of the arr.splice() method.

Today, I was curious enough to wander over to the SO beta site. Needing a familiar reference point, I located that same initial question I found years ago. What a tragedy! I could hardly believe my eyes.

It was as if all forty answers had been reformatted into a run-on sentence and submitted as a single post. I must have read 10 or 11 answers back-to-back, not to mention the associated comments without even realizing it.

Finally I noticed the tiny shift that marked the end of the current answer and the start of the next. And despite being a developer for six years now, after sifting through everything I read, I am less confident in my ability to edit array elements right now than I was before I ever learned how in the first place.

I would rather CTRL-F through the documentation... I would even rather search page-by-page through a stack of programming books than use SO beta again. If there was a Stack Overflow hell, that site would be the portal, and if that design actually gets implemented, it will be a cold day in hell before I spend another second here. SO has become a cesspool of empty promises and product enshittification. The mod strike exposed their true nature, the forced AI slop rollouts devalued the core product, and apparently all that remains now is to decompile the entire platform into alphabet soup.

I leave you with this side-by-side comparison of the same question, both then and now.

Old Version New Version
the old (current) format of questions on Stack Overflow the proposed (beta) format of questions on Stack Overflow
New contributor
killshot13 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
2
  • 2
    It's a bit disingenuous to cut the old versions screenshot after the first question when you don't do the same for the beta screenshot. I generally agree with your argument but that severely weakens it. Commented yesterday
  • 8
    Fair enough. I was showing how far down I scrolled before realizing I was no longer reading the same answer; however, the term "side-by-side comparison" does invalidate my intent. Updated image to show only the initial question and top answer for unbiased comparison. Commented yesterday
15

If this new design goes live in the current state (assuming all missing features are added), you'll once again lose a big chunk of your daily users / moderators - killing the last chunk of the remaining 'community'.

I'll sum up some of my "huh" moments, not all, it's a waste of my time for this dying platform.


  1. The home page is completely black & white

  2. The new 'copy' button already made code blocks too large, why did you make them even larger? enter image description here

  3. What are these? Where are my Gold - Silver - Bronze badges (as they're called on your profile)
    enter image description here

  4. No way to sort answers

  5. No way to flag

  6. Share button copies the link, were are the other options

  7. 'Protected question' banners etc are missing

  8. No comment collapse (omg reddit), on a big question I need to scroll 6 times to pass all the comments of the first answer

  9. No clear distinction between elements / questions / answers

  10. 'Edited 5 years ago' does not show by whom

  11. Sidebar titles are smaller then there content

  12. Inbox button does not work

  13. Maybe add a bit more spacing around these complete useless parts:
    New: enter image description here

    Old: enter image description here

  14. The reputation tab showed around 8 rows, this has now become 4. Yea just hide the only information that modal is suppose to show.


Bye Bye Stock Overflow

1
  • 6
    is there a major connection to these issues and why you see stack overflow as no longer useful to you? all of these seem like fixable issues, as opposed to the whole... everything is an open ended question now with no curation. Commented Feb 25 at 14:42
12

I'd like to add an alternate perspective.

I am exactly the person you seem to be targeting with this 'redesign'. I love AI. I think the community pushes too hard to close and delete questions that have potential. And I'm perfectly happy for SO to make money using my questions and answers here.

And yet, this is a terrible design, and the plan to stop review queues and question closure is a terrible one. You put a questionable AI front and center, but we want the questions to have that place. I want fewer questions to be deleted, but we can't get rid of deletion (we need to guide new users on how to ask better questions and existing users to be friendly to new users).

Please, please, please rethink this plan.

11

Broken answer links

The old links to answers are broken. I've picked a random one I can see from my own profile: https://beta.stackoverflow.com/questions/10588644/how-can-i-see-the-entire-http-request-thats-being-sent-by-my-python-application/10593572#10593572

If I click on this, I get a 404 error.

Removing the trailing /10593572#10593572 fixes it, but there's nearly 18 years of old links like that. It would be good to keep them compatible.


No delimiter between question and answers

When I look at that same Q&A (working link): https://beta.stackoverflow.com/stack-content/questions/10588644/how-can-i-see-the-entire-http-request-that-s-being-sent-by-my-python-application

The old layout had a horizontal line between each answer. This new layout does not. That, and the fact that the comments now use a larger font, make it much harder to see when a question or each answer starts and end when you scroll through.

I'm not particularly bothered about this because it's "my" answer, but even I can barely find it looking like an answer, in between comments from the previous answers and comments on my own.

This is the new look:

enter image description here

Maybe put a box around or something. In the old look, we had both a vertical delimiter between answers and the answer's score as a marker on the left-hand side to clearly suggest it was a different answer.

As it stands in the new layout, if the answer itself has horizontal delimiters, it becomes even worse for visual separation with other answers.

This new layout is bad for both long and short answers.

This is the old look:

enter image description here

Even "Hacker News" has a better threading layout.

I'm not sure why making the answer's score far less visible is meant to be an improvement either.


New style

It's quite subjective, but the black logo and general layout colours look a bit bleak.

8
  1. Full release: Stack Overflow will switch fully onto the new design, which will be accessed directly on stackoverflow.com. After a full release, the “classic” site design will be decommissioned. A date for this phase has not yet been decided.

Instead of decommissioning it, why not keep hosting it on a domain such as old.stackoverflow.com and stop supporting it? Having this here would allow people to choose a design they think is better, and it wouldn't too much work, since you already have this UI built. Additionally, userscripts might be broken on the new design and this could prevent a lot of rewrites.

However, please note that we plan to retire certain curation workflows, such as close votes and most review queues, in the new design.

OK, you're removing old questions completely?

There will also be a link in the left sidebar, which says “Help improve beta,” that you may use to submit bug reports, feature requests, and general feedback to the company.

Where will this link go? A private message to Stack Overflow?


Additionally, if you plan on removing curation workflows, you do plan on hiring hndreds of employees to constantly keep an eye on things, right?

8
  • 5
    i imagine old.stackiverflow.com would pretty quickly become unusable Commented Feb 20 at 2:26
  • 10
    @starball FWIW, old.reddit.com still works 8 years on, even if it's missing some features Commented Feb 20 at 3:34
  • 1
    The only thing I think would actually be unusable would be the content more than the UI, since it will still function. Commented Feb 20 at 4:37
  • 8
    "why not keep hosting it …" Because they want to get rid of "certain curation workflows such as close votes" that are tied to UI support. Commented Feb 20 at 11:01
  • 1
    Old questions wouldn't be removed; they would still be accessible, and the UI would be updated with some tweaks, but they would remain. For feedback on improving the beta, it would go to the relevant teams working on it. Commented Feb 20 at 15:13
  • 7
    all the existing "userscripts" of SO will become meaningless because that will no longer be SO. it will be a golem in the shape of reddit. Commented Feb 20 at 20:28
  • @MisterMiyagi If the features don't work, it's a backend thing. What I'm saying is to keep hosting this frontend, even if some features no longer work. Commented Feb 20 at 21:07
  • 1
    I note old.reddit.com is still a thing. Commented Feb 26 at 7:26
6

I couldn't find anything here about whether being able to accept answers has changed, so it looks like I should still be able to accept answers. But I can't find the option to accept an answer on this question of mine where I haven't accepted any answers: https://beta.stackoverflow.com/stack-content/questions/50033134/headless-chrome-script-to-use-the-same-session-and-skip-two-factor-authentication

screenshot of an answer without an option to accept it

2
  • It might be covered under the "Certain actions on a post like Follow, Save, Start a bounty, etc." bullet? But it's not explicit, so I'm not sure... Another bug here though is definitely that code highlighting color theme, oof. Commented Feb 24 at 23:00
  • @zcoop98 yea I was going to make a separate one about that but there's so much here I don't like I just don't feel motivated enough Commented Feb 24 at 23:18
6

FYI: Sorry for too much images, please look at them carefully I couldn't separate them any better on this answer:

enter image description here

And now compare that with

enter image description here

I just saw this place says two answer but it is just a long text flow. The comment ends and the same user gave answer below. Please use separator lines they are still modern.


enter image description here Such a flow is not bad for reddit where messages per user are often maximum 5 lines. Here the content can't be read without scrolling. Even they use good lines:
enter image description here

5

If you have to make comments under a post indistinguishable from a post, at least there should be way to remove comments that are obvious chatter (maybe the flag feature), no? Please look at the following example:

example

Unless you're carefully reading word for word, it is difficult to see where chepner's comments end and answer starts just by scrolling.

4

There will also be a link in the left sidebar, which says “Help improve beta,” that you may use to submit bug reports, feature requests, and general feedback to the company. Look for this button once you have access to the beta:

For those on smaller screens, using "vertical tabs" in Firefox, tiling their browser window next to a console, etc. who are wondering: the icon at the top left of the page (the rounded rectangle with an off-centre vertical line through it) causes the left sidebar to appear overlaying the page. (The main site has something similar using a "hamburger" menu, but the left sidebar persists at much narrower page widths.)

-3

In the classic view, it's very easy to go to another StackExchange site (as StackOverflow's meta site), as follows:

Current ribbon

How can this be done in the new layout?

New layout

... and despite what's mentioned in a comment, it's not in the left menu:

Left menu

3
  • 1
    it’s in the left menu. Commented Feb 25 at 8:50
  • 1
    Keep scrolling. Commented Feb 25 at 9:25
  • 2
    @user400654: Jezus, I found it! You should understand I have the habit of having a StackOverflow window on the top or the bottom half of my screen (in landscape mode), so that I can follow build procedures, test executions, ... in background in the meantime. That won't be that easy anymore if that Beta-thing becomes the standard. Commented Feb 25 at 9:41
-5

Absolutely horrible. Scrap it.

The only "redesign" I want to see here is a rollback to 2015... and a SE dedicated to opinion-based programming questions.

1
  • 2
    I've edited your post. Calling for the resignation or firing of staff is not appropriate. Commented 20 hours ago
-6

About curation:
Quora have very similar to SE trend while being much more permissive on new questions. Reason of activity decrease is in the intersection between both sites, while curation experiment is outside of intersection.
And also, why the general idea is that Reddit has less curation or is more friendly? It actually shadowbans up to 1/3 of all user's messages, especially of new users, which is much worse than new user's experience on SE.

How it can be addressed positively:
Introduce automated filter on SE which give real-time feedback to person who writes Q or A. LLM can easily detect too bad English, misspelling, wrong tags, lack of reproducible example, wrong site to post Q or A, before they are downvoted for these trivial reasons. Which will fix half of the existing negative sentiment.
Real-time downvote/question block from LLM is much less annoying than downvote from SE expert after hours of writing.

About activity:
Policy of "any question matters" (removing downvotes, closure and so on) will just ruin signal-to-noise ratio (is the very reason SE exist) which is probably mentioned on every Meta discussion. Let's say SE IS desperate to create a window for some low effort activity (and community pushback here will be ignored no matter what). What if there is still minimal damage solution in contrast to current breaking changes:

Allow limited copy and paste activity specifically if it addresses problems:

  • removes outdated information
  • improves readability or modularity
  • narrows solution to specific set of versions

Introduce separate archive site or special tag (separate site will help greatly with search request "keyword site:stackoverflow.com" and to avoid dupes on the same domain).

  1. QA older than ~5 years with outdated top answer (by vote trend) are detected and labelled automatically

And then a procedure of low effort QA update is recognised:

  1. after labelling old QA with outdated tag matching creation date (for example, Python 3.9, end-of-life on 10.2025), a dupe copy-paste of the old Q is allowed specifically if updated Q mentions why previous top A is outdated; that dupe must be tagged with recognised by platform modern tag like 3.15. Old QA is dropped to archive when dupe passes curation.

Archived QAs are not read-only, but just live in clearly separate search results space.

  1. copy-paste of answers from archive is allowed specifically if they are tested and improved in some way. For example, very high amount of old code answers can be wrapped into function.

Steps 2 and 3 create that room for low effort activity for new users while possibly minimising damage to signal-to-noise ratio (or even improving it).

8
  • 5
    Just slapping an LLM onto the input isn't a solution. It's an extremely expensive band-aid on a gaping wound. Commented Feb 24 at 11:51
  • 1
    Reddit's shadowbans are more about preempting spammers (and possibly for some subreddits, about group cohesion), rather than trying to enforce any notion of post quality. Commented Feb 24 at 20:38
  • 1
    Why does everything has to use an LLM? I've seen so much people go "Just use an LLM" but why? There are other forms of AI and other systems that are more suitable. Commented Feb 25 at 6:49
  • As for LLM can "easily detect" - I've seen way too many posts that include AIGC evaluation in them that praises the post as perfectly suited for the site. Because the poster copy/pasted the entire response from a chatbot which takes the form of "<question> Yes, it's a great fit for the site...". But those questions are not, in fact, a good fit. I've also seen posts like "Here is a re-written version of your question that fits the Stack Overflow guidelines: <post>" but it doesn't fit the guidelines. Commented Feb 25 at 6:50
  • So, I really have to wonder where the confidence comes that LLMs are infallibly aware of how to use this site. Commented Feb 25 at 6:50
  • @VLAZ Just to clarify, there was never part about replacing curation, only to replace routine quality checklist before curation. With a benefit of fast LLM feedback (your question shall not pass, improve it!). People here don't downvote for fun, there is usually very obvious reason why question/answer is bad. Except this answer, of course :). Just kidding, we really at the point "I can't just give up hope and stop opening dear SE which was best Internet site 2010-2020, let me at least try to think with others for some miracle solution". Commented Feb 25 at 7:27
  • At no point I considered what you said as a replacement of curation. I'm questioning the suitability of LLMs for what you propose them to be used for. First, I question why an LLM should be used as opposed to other automated systems. Second, I question the claim that LLMs can evaluate a question's suitability before it's posted. Because I have already seen questions that were deemed suitable to be posted but were not, in fact, suitable. Commented Feb 25 at 7:33
  • @VLAZ Oh, I see. It's indeed just more of a guess with some confidence that LLM will be good to detect lack of paragraphs, misspelling, lack of code formatting and incorrect site (i.e. posted on SO instead of SuperUser) and similar. And then fast and non-personal feedback benefit is too fundamental advantage. Commented Feb 25 at 7:38
-7

I don't get the curation workflows stopping.
Imagine I create a bogus e-mail address and from there I create a StackOverflow account.
First I ask a normal question and/or give a normal answer, and once I'm in I flood the site with a million questions.
If curation workflows are deleted, then how will such a spam attack be handled?

6
  • 12
    Spam deletion doesn't use the closure system right now so it's at least not affected by the explicitly stated curation removals. Commented Feb 19 at 8:27
  • 2
    for what it's worth, current state has rate limiting. dunno what future state would look like. Commented Feb 19 at 8:41
  • @starball: I think some of those rate limits can relatively easy be circumvented by creating multiple e-mail accounts, or pretending to work from different so-called sources, can't they? Commented Feb 19 at 8:55
  • 1
    @Dominique That's possible right now; these changes probably won't directly affect it. When it happens, we fight it with spam and R/A flags, which (as cafce25 said) don't use closure. Pure vandalism doesn't happen that often, though, because of the aforementioned spam and R/A flags. Commented Feb 19 at 17:54
  • 9
    Then the number will go up by a million and everything will be working perfectly according to the company kpis. Commented Feb 19 at 21:04
  • They have defense even for much more sophisticated attacks. They do not disclose any details, but there are many long bans for "voting irregularities" or for spam. My opinion is that starting to play with them in this sense simply does not worth, beside basic moral principles, also the gain is not even close to the effort and risk. Btw, I have not seen spam here since heck a long time, there are also even volunteer user groups for the early detection & intervention. Commented Feb 24 at 10:48
-7

This post is mostly my own speculation, but it is a speculation of a long, avid site user, based on the currently available facts. But, anything what I foresee here, nothing is sure. I also say sorry for any company employee who might find the post critical, I tried to formulate it on a reasonable polite way. However, for the factual parts, I would happily dig out the reference on the comment ask.

As the company said many times, it is a design change. That partly matches their consequent, but probably never admitted behavior to dishonor and neglect the SE, where it is even possible, and give all their resources to SO, despite that currently the SE doubles the SO in the new Q / month stat (and about 3/2 of it in Votes+Feedbacks/month, I would happily give SEDE link for both statements).

Design change might cause some surprise side-effect with a feature decrease. For example, it is possible in the new design that no close review exist, although the company currently closes this out. But if it would happen, then the API side of the VtC queue could be removed from the backend later, after the new frontend went into release. But, as the company said, it is not happening now.

Design change can not cause feature increase, because in this case, it would not be a design change only. Beside that, that would mean that the company develops some new, something what is not superficial or finetuning. That is not their strong side since about 2012.

As the company says, the primary goal of new design is to move the SE sites into the SO on the design level. With it, they want to reach two goals:

  1. Importing the SE (currently double in size of the SO) into the SO, essentially sacrificing it, to give a bit of time to the SO.

  2. Importing it, but without any significant change. As I have said, they never change anything in the system significantly. Note, also that is the probable reason of that the VtC queue remains, and not your outcry. Obviously this "shared branding" should mean a shared database, or at least a seamless and usual migration everywhere. They won't do that. The concept of the "shared branding" between the SO and the SE is very likely a compromise, trying to reach this goal, but without any significant change (db schema, rules, api).

Thus, what I expect:

  • a. Majority of the changes will happen on the CSS level.
  • b. There might be some change on the HTML level, too.
  • c. Any change on the API/backend level is very unlikely.

I also do not expect a near change of the application of the design of the SE sites, despite that so was it reasoned originally. I do not expect this because the negligence of SE sites by the company seemed so strong until now, that they did not even "get" their wonderful new feature, the ads posted as content.

So, if they neglect the SE on the level that it does not even get more ads ;-), I do not think that it will get a new design.

If the soon opening beta.stackexchange.com will be significantly different of what I foresee here, I will happily retract this post and ask for your forgiveness. As I said in the first line, it is entirely my speculation, but based on my 1.5 decades of experience of an avid site member, and having also a large experience, how things are usually going by companies of this size, and other characteristics.

9
  • 2
    "how things are usually going by companies of this size, and other characteristics" SE isn't exactly an ordinary company. They've proven time and time again that they don't want to listen to the community, and that all they care about is more page views, at basically any cost. It was clearly stated that SE wants to phase-out some curation functionality. This is more than just a design change. Commented Feb 24 at 11:44
  • beta.stackoverflow.com has opened and what I have foreseen, happened until now. No review queue was retired et all. I said, they said that it is a design change. My next prediction is that they won't really hurry to inject the design changes also into the SE sites. Even if they do, they will also get the affiliate ads. I am happy that I have seen it well, and I am sad that I could not predict it in a more optimist post. Commented Feb 24 at 17:26
  • 1
    @Cerbrus sounds like a typical company to me. Commented Feb 25 at 9:10
  • 5
    @peterh what you "predicted" is literally what the company post states, it's no prediction at all just parroting what the OP says would happen in the beginning: "At the time of this release, only the homepage and question pages will be using the new design." iow in the beginning the review queues will be using the old design and thus be accessible like they always have been. Commented Feb 26 at 8:12
  • @cafce25 SE sites. SE sites. SE sites. I think you, just like the company, have filter on your brain to acknowledge that there are 160 SE sites, and these are focal point of the post. I think it is the time to acknowledge yourself to their existence, considering that their traffic now doubles the SO. SE sites. SE sites. SE sites. If you want any reaction from me in the future, I want a positive feedback from you that you are ready to know about their existence. What will likely never happen. SE sites. SE sites. SE sites. Commented Feb 26 at 8:38
  • 3
    @peterh meta. stackoverflow .com is (unsurprisingly) about Stack Overflow. If you want to discuss the network, you're on the wrong site. But no clue how my previous comment even is affected by that, it's not about SO nor SE, it's completely orthogonal to that. Commented Feb 26 at 9:21
  • 3
    Repeating "SE sites" like that doesn't make your statement correct. It's tantamount to throwing a tantrum... This announcement is about Stack Overflow. Not about SE. Commented 2 days ago
  • @cafce25 It is part of the larger picture, long main topic on the MSE. the company wants the unify the branding of the SE and SO. Essentially, what is, for example, Physics Stack Exchange now, it will be Physics Stack Overflow, under the collective name of Stack Overflow Public Platfom. Also these sites would get the design. Part of the essence of the post is that I believe (predict), they won't do that, or surely not quickly. That was the last time as I tolerated from you playing that you don't understand, and I did it even now only because you are young. Commented 2 days ago
  • 5
    @cafce25 has been a member on this site longer than you have, peterh... Calling him "young" is just.... Weird. What you don't seem to understand is that SE's plans for unified branding are not the subject for SO Meta. That change is discussed on SE meta, and is completely irrelevant here. Commented 2 days ago
-13

It's dead, please accept that and create a proper burial place. Not a garbage bin.

You kicked away askers -> there is no site after that. Don't ask yourself "how do we proceeed?". Ask yourself "why would users return here?". They would not.

5
  • 10
    who's they, and how did they kick away askers? Commented Feb 21 at 6:30
  • 2
    The numbers show pretty clearly that just about every group has taken a severe hit, not just askers. It takes both Q and A to Q&A. It takes even more to be the kind of Q&A that SO claimed to be. Commented Feb 21 at 6:49
  • 2
    An interesting question would be who left first, the askers before the answerers or the other way around. It might be possible to answer with detailed visiting data that the company should have. Commented Feb 21 at 8:33
  • 2
    "Ask yourself "why would users return here?"" To find the still existing problems and solutions? This isn't a help desk. But this meta post is about their intent to turn it into. Commented Feb 21 at 19:28
  • 2
    Answers should not be in the form of a haiku. Please expand and clarify. Commented Feb 23 at 14:22
-13

The new site is ABSOLUTELY HORRIFIC, confusing, terrible to the core. Words can't even begin to describe how bad is it. AFAIU SO is doomed because you guys didn't understand 2 basic things:

  1. You don´t resist to disruptive tecnologies. You embrace them. The sooner the better. Trying to resist is just creating more and more problems for any company. You need to embrace AI to answer questions and let the community opinate in the answer and correct them if their wrong/incomplete.

and

  1. The problem with SO was never AI, nor it's design (which is very good as is). The problem was always TOXICITY. The problem was rude/harsh comments, downvotes without explantion, treating people bad... that is the real problem. As I said in my answer here: "(...) I can assure you that if there were any other options people would embrace them in a heartbeat." People accepted that because, for some time, SO was nearly the only way to solve specialized coding problems. This was nearly forced on us due to lack of options. Or at least known options. But when someone treats you bad, what you want more than anything is finding some way of being treated better. As I predicted, people found the alternative and flee from SO in large sums. Solution: Block downvotes without comments, create a zero tolerance for rudeness (comment/answer/moderate with care and comprehension for people or don't do anything), lighten the rules for bad questions and closing questions which can allow people to feel encouraged to ask questions rather than afraid to ask. However this solution should have been implemented years ago. Now is probably too late.

I know one thing: SO it's very near it's end. If you insist in putting that beta monstrosity as the default site, it will be like jumping off a cliff without a parachute. You'll hit the ground quickly.

5
  • 3
    why so toxic? it's hardly even half implemented yet Commented 2 days ago
  • @user400654 you mean there's more ? Lord help us all 🙄 Commented 2 days ago
  • 1
    "Block downvotes without comments" I will die on this hill. #1 reason I stopped using the site regularly. (anonymize downvote comments in4b smart replies) Commented 2 days ago
  • 2
    I dont understand whom you adress with "you guys". Though I also don't understand what the two points you raise have to do with the new design. Its a bit ironic that you talk about harsh comments and that this would be a reason for the new design to be horricifc while its not yet possible to write comments in the beta Commented 2 days ago
  • 1
    I can't understand what you mean about "toxicity", but I can certainly agree that there is a problem with "bad treatment" — just not from the same places you suppose. Commented yesterday
1
2

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.