Hot Topics and Pinned Topics


Recommended Posts

Whilst I agree that having the pinned topics stand out does make the forum more organised and much clearer to tell the pinned topics from the normal threads, it didn't work efficiently on Neowin. Obviously. I mean, take Grand Maester for example, most (if not all) of the questions in his many topics in this forum can be found in the FAQs and other pinned threads in Neowin forums, however, this user obviously didn't read these pinned threads before he asked some of his first questions.

It is because of issues like this why Neowin have decided to take out one of the indicators which was there, but still leave in the needed and obvious indicators - an icon of a pin and paper and the text "Pinned:".

To me, it's very obvious which topics are pinned, straight away and whilst it doesn't look as neat as it does with the separators, you can't really blame Neowin for this move can you?

Joel is just doing his job and trying to inform you all of this. You can still easily tell which threads are pinned and which are not, but this move means it will save everyone on Neowin (especially the staff) a lot of time as it will decrease some of the unneeded threads which tend to appear.

This is because even with the indicators its still not easy to determine which is which. The way it was before was much better.
Maybe instead of adding headers then is it possible to make the "Pinned" text bolded? Or maybe in a bigger size or even all in capitalized letters; anything to make it stand out just a bit more.

Funny thing is, when I look at that vBulletin example, it's perfectly fine; but when I come back to Neowin, the transition doesn't seem to be as clear.

I'm in agreement here. The new way is much harder to see and, although not unusable, is somewhat counter-intuitive. Not sure why a simple thing like this can't be addressed? ;)

The whole point of pinned topics is to get people to read them. If they aren't important then they shouldn't be pinned.

This was a conscious change because far too many people were skipping over the pinned topics and beginning to read the list of non-pinned topics. If you prefer the old way then you can still use an old skin but this will be the change going forward.

The whole point of pinned topics is to get people to read them. If they aren't important then they shouldn't be pinned.

This was a conscious change because far too many people were skipping over the pinned topics and beginning to read the list of non-pinned topics. If you prefer the old way then you can still use an old skin but this will be the change going forward.

Really all I wanted was an explanation as to why it was removed, rather than a straight up "No it's not coming back, why do you need more anyway?"

Really all I wanted was an explanation as to why it was removed, rather than a straight up "No it's not coming back, why do you need more anyway?"

Well, that's the reason then. When they were off on their own little island then people were ignoring them.

It WAS addressed, because it was obviously done on purpose. ;)

You know, this is the board that cries over every lost pixel; you'd think people would be thrilled that we removed 2 headers.

Then our definition of "addressed" seem to be varying here. :p

The header removal is fine, but something like a more prominent and/or more obvious "Sticky" indication is really all that's needed to create a visual distinction.

Then our definition of "addressed" seem to be varying here. :p

The header removal is fine, but something like a more prominent and/or more obvious "Sticky" indication is really all that's needed to create a visual distinction.

You see though, the problem here is that you want more visual distinction so that you can skip over them. We don't want people to skip over them because we consider them to be important.

You see though, the problem here is that you want more visual distinction so that you can skip over them. We don't want people to skip over them because we consider them to be important.

They are important, but frequent visitors know what's in them and know when to go to them. Although I see your argument for new members the fact of the matter is this site strives on those who frequent.

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

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      596
    2. 2
      +Edouard
      188
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!