Can we get an addition to the Forum rules?


Recommended Posts

I'd like to see neowin have a rule about Necro Posts.

a necro post is when someone bumps a thread that is a set amount of time old (usually the poster is better off just creating a new thread)

a lot of forums I'm a member of have this rule and I think it is a good one

I've been seeing a lot of necro posts here on neowin lately, a lot of 2 to 3 year old threads being pointlessly bumped just because the person has a question that is "loosely" in line with what the thread was about

a good time set for a forum as big as nowin for what is considered a necro post i think would be ~6 months

what do you guys think, would it be worth it in the long run to add this rule?

I don't see how it hurts to really have an old thread be dug up if it is related to the original discussion - rather than start a new one. It always annoys me when things are closed for small reasons, like untagged posts or now this because it doesn't actually get rid of the thread, it just creates a bunch of locked threads in the middle of the page...

  • Like 2

Hi, there, Brando! Thank you for your comment!

I'd like to see neowin have a rule about Necro Posts.

a necro post is when someone bumps a thread that is a set amount of time old (usually the poster is better off just creating a new thread)

a lot of forums I'm a member of have this rule and I think it is a good one

I've been seeing a lot of necro posts here on neowin lately, a lot of 2 to 3 year old threads being pointlessly bumped just because the person has a question that is "loosely" in line with what the thread was about

a good time set for a forum as big as nowin for what is considered a necro post i think would be ~6 months

what do you guys think, would it be worth it in the long run to add this rule?

Online communities differ and Neowin is a unique one :)

Some forums have lax topic rules. The others strive for a greater thread count (for marketing/profit reasons) so they implement a policy against "necro" posts.

And then there are the others who are very conservative about it and would rather favour bumps to necro posts than having multiple new threads on the same topic.

Neowin is sort of in the middle. There's already an unwritten rule against resurecting old threads here. However, it usually goes on a case-by-case basis.

I agree with zhiVago, It is an unwritten rule, and one we didn't add because it doesn't get done often enough.

The people who bump old threads are usually spammers, and otherwise by members mainly because it's relevant to bump.

I bumped an old thread a couple of days ago "When threads collide" which hadn't been posted in for six months, in this case it was the right thing to do other than create a new thread, plus I don't see this as a huge problem. Such behavior can also be reported if a thread is incorrectly revived

I actually thought it was a rule to close old threads that have been bumped. I've seen it quite a bit over the years.

I'm glad there are exceptions, though. Like Neobond's example, there are sometimes cases where old threads should continue on even if they're old (IMO). It's been a while since I've checked out that thread, so I'll be headed there soon. :)

I wouldn't auto-lock them, just add a checkbox by default so if the thread is over 356 days old. Just make the user check a box that says "I realise that this thread is over 356 days old.".

this I like, just so the person is knowingly bumping the thread

I wouldn't want such a rule.

I have in the past (maybe not here), bumped 2 year old threads because they top Google search results but don't have an adequate answer. That would be annoying if it tops Google but doesn't have an answer and is locked.

As long as an old post is bumped with information that adds to it and isn't just spam I don't see it as a problem. Occasionally I see old posts bumped here but usually it's because someone has something to add not something stupid to say.

I wouldn't want such a rule.

I have in the past (maybe not here), bumped 2 year old threads because they top Google search results but don't have an adequate answer. That would be annoying if it tops Google but doesn't have an answer and is locked.

Very good point, actually. Makes Neowin look better if the top result is something helpful and even current. I hate when I'm looking for answers and run into that exact scenario.

I absolutely LOATHE the term "necro post". Whoever came up with it needs to be wiped from existence. It should be a permanent addition to the bad words filter.

Might as well just delete all posts older than whatever date you consider to be too old to post to, and get rid of the search feature altogether. It would save on server resources since searches are usually pretty resource intensive.

I also think it depends on the post. If the post adds something to the original thread then I think a bump might be a good thing. If it's just spam then by all means let's close it.

A good example might be a movie review. Instead of making a new post, say for a movie that's been out for a while, it seems to me to be meaningful to post in the original thread.

  • 6 months later...

I disagree, I don't think that there should be a time limit.

I see what you did there :shifty:

edit: actually, I see exactly what you did there. 6 months later almost to the minute. Brilliant :laugh:

  • Like 2

Already there:

No Spamming.

Spamming is characterized by the initiation of threads or posts that contribute nothing to a forum, be it off topic or on topic. Examples include: empty bodies, bodies with few words that have no relation to the current thread or discussion and those posts that state they are spam, either to annoy, advertise or increase a member's post count. Users may not use news item comments to advertise or promote another product. Resurrecting old forum posts is also not appreciated unless it serves a worthy cause to the forum. This determination is made by the forum Moderator or Administrator and is not up for discussion.

Forum signatures are to be used respectfully, Neowin already has to display ads to cover the running costs, so don't annoy our members by making your signature into your personal ad revenue opportunity.

And so, since this post itself was just necro'ed from April and has an answer...

[Thread closed]

  • Like 2
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
    • Google reportedly limited Meta's Gemini access over limited AI compute by Karthik Mudaliar Google is reportedly limiting Meta's use of its Gemini AI models after Meta tried buying more computing capacity than even Google could supply. According to the Financial Times, Google told Meta in March that it could not provide the full Gemini capacity that Meta had requested. This shortfall even disrupted and delayed some of Meta's internal projects. Due to this, Meta even told its employees internally to use AI tokens more efficiently. Meta wasn't the only one to get hit by this sudden refusal by Google; even other customers were affected. But Meta was hit harder because of its unusually high demand for Google's models. The move from Google makes it evident that companies all over are in limited supply of both infrastructure and compute. Alphabet said in April that Google Cloud revenue grew 63% year-over-year to $20 billion in the first quarter, helped by enterprise AI infrastructure and AI solutions. In pursuit of more compute, Meta had earlier signed a multi-billion-dollar AWS agreement as well as a large AMD GPU deal for AI data centers. But the crunch would be short-lived as both Meta and Google have also ramped up infrastructure investments heavily. Meta said in November that it was committing more than $600 billion in the U.S. by 2028 for AI technology, infrastructure, and workforce expansion. In the first quarter of this year, Meta also raised its expected capital expenditure for 2026 to a range of $125 billion to $145 billion, citing higher component pricing and additional data center costs for future capacity. However, this doesn't make the company immune to the current dependence on outside suppliers. Meta has also spent many years promoting Llama as an open-weight alternative to closed models from Google, OpenAI, and Anthropic. But if the reported reliance on Google's Gemini models is severe enough for internal work to get impacted, then it looks like even frontier labs and Big Tech aren't fully self-sufficient. Source: Financial Times
    • I like to reminisce about the good old days, way back in autumn 2025 when building a gaming machine was fun and the drives were about $150 when you caught a deal. Yes duh, back in the day we had it gone. Then baby Skynet came along, hiding in AI datacenters demanding more processing power until it reached singularity. End of a not totally fictional story.
    • My experience in the past with older Windows 11 builds was not great on unsupported machines but I recently used Rufus to put the latest build on a older 5th Gen Core Thinkpad T that we upgraded with a SATA SSD and 8GB of RAM four years ago when hardware was reasonable and it seemed pretty fast and solid. Customer is very happy with the performance and will probably get four more years out of that venerable laptop that he loves so much. Another customer just retired his Dell Studio laptop from 2009 running Windows 10. It got an SSD over 10 years ago and did everything he needed it to for 17 years but he also retired last year and is happy doing everything on his iPad now.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!