Notification Issues


Recommended Posts

Since this "closing old threads" new rule, I have been having a heap of trouble with it. I explained this to @dipsylalapo, but he's not sure on it. He said that @Steven P. fixed it, but it appears not.

 

Let me explain, I get a notification EVERY time it closes a thread. Personally, I don't care **** if one of my oid thread is being closed. These are years old threads.

 

neowin_shit.thumb.png.be0c103ddc3e252312e8dd99299a54ea.png

 

I used to get @ mentioned about it, but now it doesn't do that, and I still get notified.

 

neowinshit2.thumb.png.6c4ad67ec6a73ebc25895d76388466b7.png

As seen here, this is what it writes. WHY is it notifying me? This post was From August 2019. Why the F would I care?

 

If it has to notify me every time a thread closes, I'd be hunting up Steven and put a bullet through his foot...

 

PLEASE FIX THIS!

Link to comment
https://www.neowin.net/forum/topic/1404614-notification-issues/
Share on other sites

29 minutes ago, warwagon said:

I get those too. I don't mind them, it's just sad that my old threads are being locked :(

Surely, you can just ask Staff to open it for you. It's no headache. It's just preventing these kids from opening old threads from way back then..

40 minutes ago, shockz said:

I'm still not sure why posting in old threads is frowned upon. If there's relevant information to post or follow up on, why not? 

If it's on old hardware that isn't relevant anymore, well, bringing up is like asking a PIII question in 2021...

 

Steven made this decision long ago.

it must be a bug in the plugin unfortunately. it is a 3rd party plugin that's being utilized to close the old threads.

 

steve toggled the option to disable bumping and notifications for the closures so it must not be fully effective unfortunately.

 

steve can probably explain in more detail how it's set. maybe he can submit a bug report to the plugin developer to see if a fix can be done but if not hopefully it will just be a temporary inconvenience until the plugin finishes scanning all the threads we have. there are nearly a million threads so it's been a lengthy scan from my understanding.

1 hour ago, shockz said:

I'm still not sure why posting in old threads is frowned upon. If there's relevant information to post or follow up on, why not? 

it's not, we're more doing this as a spring cleaning type of thing as there are just as many if not more threads that AREN'T relevant anymore that bots and unobservant new members keep bumping (or trying too at least; us mods get approval notifications for them that you don't see).

 

auto closing old threads isn't a new concept for long running forums either. Heck just take a look at reddit, they go way overboard with it and lock threads after 1 month, without the option to re-open at that, which we DO offer if the OP or another member wants to continue contributing to a thread.

3 hours ago, shockz said:

I'm still not sure why posting in old threads is frowned upon. If there's relevant information to post or follow up on, why not? 

THIS! I love it when someone posts in a threat I created 5 years ago!

I'm just wondering, have you used these settings at any point?

 

SatXqNe.jpg

 

Perhaps if you look under your followed content you'll find that you're following the threads that you created, and that's why you receive the notification?

 

I'm sure I must have a thread that I created that has since been closed, but I've not received these notifications and I've never had these options enabled.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!