Windows 8 Sales are actually Amazing - 40 million sold


Recommended Posts

Additionally, countless Windows programs depend on this functionality as this allows them to ensure they open the default browser instead of figuring out what browsers users have installed (the app sends the url to the API as if it were a file to execute). So it isn't that arcane or odd.

I'm not sure if you're serious or not... But if you are... I'd recommend you read some of the fundamentals of the craft such as Hunt's The Pragmatic Programmer and understand why the DRY Principal he mentions is considered a fundamental part of software engineering.

You can also Google it... But actually learning the concepts is far more important.

The point is that the search dialog uses entirely different code and calls form the run dialog, but it can still do the same thing. Sure they could use the old run dialog code to do stuff the search dialog can already do. OR they could more effectively just let the search dialog do all the stuff itself, more efficiently and without calling other code.

OR is your idea of effective coding to first check if the code is a call for a local executable (btw at this point, it can already execute it), then if it finds out it is, then it passes on the call to the run dialog...

seriously, THINK about it.

and if hands are already on the keyboard it's slower just to take your hands off the keyboard and put it on the mouse.

win+e then type. allt+tab then type, win+# then type.

normally the site I'm looking for is already open in one of my 30+ tabs though.

The point is that the search dialog uses entirely different code and calls form the run dialog, but it can still do the same thing. Sure they could use the old run dialog code to do stuff the search dialog can already do. OR they could more effectively just let the search dialog do all the stuff itself, more efficiently and without calling other code.

OR is your idea of effective coding to first check if the code is a call for a local executable (btw at this point, it can already execute it), then if it finds out it is, then it passes on the call to the run dialog...

seriously, THINK about it.

win+e then type. allt+tab then type, win+# then type.

normally the site I'm looking for is already open in one of my 30+ tabs though.

No, my point is the RUN dialog and the Search function "run" capabilities share the same underpinnings. Otherwise, MS would be violating the DRY principal by having two separate pieces of code doing the same thing in two places. The RUN dialog and the "run" functionality in search are merely two separate windows into the same room.

It's far from even being a Windows-only (or even OS/distribution-only) dilemma - look at the earlier-in-this-thread comparison between Adobe Creativity Suite (CS) products and Microsoft Office products; even on OS X - which has far greater UI cohesiveness than even Windows pre-8; look at how the Adobe CS products behave within that UI compared to Microsoft Office products. Different approaches to the same problem. Heck - just look at the differences between Pagemaker and Word (again, on OS X, not Windows).

Don't necessarily disagree with your point or conclusion but comparing Adobe Graphic Design software to Office Products, and PageMaker (InDesign for some time now :) to Word, is like comparing apple's to oranges.

and if hands are already on the keyboard it's slower just to take your hands off the keyboard and put it on the mouse.

I don't know about that one. We're so well trained, even novice users can slide that right hand over and grab that mouse pretty darn quick.

No, my point is the RUN dialog and the Search function "run" capabilities share the same underpinnings. Otherwise, MS would be violating the DRY principal by having two separate pieces of code doing the same thing in two places. The RUN dialog and the "run" functionality in search are merely two separate windows into the same room.

Except they don't, the search dialog by it's function has to do thing other ways than the run at an earlier stage, and at that stage it can already launch the app. so they don't share the same principles, not in any meaningful way that would make it any way sensible for them to share the same code.

it's not just the start screen. it's metro apps in general. The messaging map give you absolutely no option to turn it off. it's on perpetually and everytime someone sends me a message it give me no way to stop the annoying pop-up box on the desktop informing me I have a message. Trying to uninstall that particular app uninstalls 3 or 4 others including the calendar and mail, and people apps. This is a product that Microsoft should truly be sorry for. This is the 'batman and robin' of OS's. I get why they tried to do and I think that's cool. It was executed so horribly

I agree with you, Metro apps, particularly Microsoft's, are unfinished and IMO, and an embarrassment. The decision to bundle the core messaging apps was a choice.

I wouldn't write of Windows 8 though. Aside from the apps, and that is big, I only truly miss unified search and the ability to perform context actions on the result with the click of a mouse. You can still do that if you search with Explorer in the desktop environment. The Modern UI simply will not be able to duplicate that productivity.

Someone here used fast an efficient in the same sentence with Modern UI Search. I need some of whatever they're smoking.

Except they don't, the search dialog by it's function has to do thing other ways than the run at an earlier stage, and at that stage it can already launch the app. so they don't share the same principles, not in any meaningful way that would make it any way sensible for them to share the same code.

I think you're completely missing what I'm saying here... The RUN dialog has to pass its "run" command to the OS to tell it to execute the application. The Start Screen "run functionality" has to do the exact same thing. Sure, it has to do searches and a variety of other tasks, but once it has decided it needs to do "run functionality" then it has to pass that off to the OS somehow. Unless you're implying that the Start Screen is executing that code itself independent of the OS it is running on?

The RUN dialog really isn't doing anything but calling whatever API endpoint MS has exposed for starting processes. I'm sure this is the same endpoint used by Explorer itself and all over the OS.

The dialog itself was not what I was referring to.

I think you're completely missing what I'm saying here... The RUN dialog has to pass its "run" command to the OS to tell it to execute the application. The Start Screen "run functionality" has to do the exact same thing. Sure, it has to do searches and a variety of other tasks, but once it has decided it needs to do "run functionality" then it has to pass that off to the OS somehow. Unless you're implying that the Start Screen is executing that code itself independent of the OS it is running on?

The RUN dialog really isn't doing anything but calling whatever API endpoint MS has exposed for starting processes. I'm sure this is the same endpoint used by Explorer itself and all over the OS.

The dialog itself was not what I was referring to.

That's completely irrelevant of your original argument though, as that's the execution call, which is used not just by run, Search, but also shortcuts, other programs, start screen, ANYTHING that launches ANYTHING on the OS. and is not even part of the run dialog as such. just something it uses on the same line as search.

This was not your argument, you said the run dialog had to be kept and that search used the run dialog code. that is something completely different form using the execute call. The run dialog is far more than just the execute, call, which again isn't part of it, but rather part of the core OS.

That's completely irrelevant of your original argument though, as that's the execution call, which is used not just by run, Search, but also shortcuts, other programs, start screen, ANYTHING that launches ANYTHING on the OS. and is not even part of the run dialog as such. just something it uses on the same line as search.

This was not your argument, you said the run dialog had to be kept and that search used the run dialog code. that is something completely different form using the execute call. The run dialog is far more than just the execute, call, which again isn't part of it, but rather part of the core OS.

This thread has been moving pretty quickly today so I'll forgive you for pulling my statements out of context.

I never said the run dialog had to be kept. I merely stated that it should be kept.

I later responded to a post from Dot Matrix that stated the run dialog should be removed because the code is redundant. My point was simply that the code doing the same task between the two isn't repeated and is most likely shared, as long as MS adhered to good engineering principals.

It's a great read this thread :) One trying his best to outdo the other, neither getting anywhere, both arriving back at the same start position :woot:

Great for a giggle at the end of a hard day.

It's a great read this thread :) One trying his best to outdo the other, neither getting anywhere, both arriving back at the same start position :woot:

Great for a giggle at the end of a hard day.

Very much agreed. I needed the distraction from work ;)

You're talking about using a consumer-oriented OS like some kind of nerd's plaything, which is never going to happen. You're most likely the one person still using the archaic run dialog that should have been stripped from windows in Windows 7.

Dot, you know better than that - I have personally told of using the Runbox in Windows 8 (and Server 2012, for that matter) to avoid two issues that have plagued all versions of Windows (desktop and server) - desktop-shortcut clutter and (starting with Vista/7) Taskbar-Superbar pin clutter. (With the Start menu itself gone, my biggest reason for leveraging Run also went away - however, that does NOT take away from the usefulness of the Runbox - especially since it's the ONE area that the addition of Index Server to the Windows core - starting with Windows 2000 - has always and never-failingly worked.)

The more I use an application, the LESS likely I am to create either a desktop shortcut OR pin said application to the Taskbar or Superbar, for the simple reason that I can Runbox the application in question. (Thanks to Index Server, the Run dialog actually has a memory - it remembers the fifteen last-used commands, batchfiles, scriptlets (including PoiwerShell scriptlets) - and it's been in there since Windows 2000. That is, in fact, why I don't miss the application shortcuts that Office hasn't created by default since Office 2003 for ANY of the applications - Office 2000 only created a shortcut for Outlook by default.)

It's a great read this thread :) One trying his best to outdo the other, neither getting anywhere, both arriving back at the same start position :woot:

Great for a giggle at the end of a hard day.

what ever he says he gets you doing it wrong..

and i'd say they are losing if this was a debate.

atleast i tried to sya linked to the topic at hand lol

some of these cheerleaders lose it and go off about using the mouse for 13 pages or whatever lol

why would zoom in on one micro aspect of how this one guy uses windows ?

insist "he's doing it wrong" ?

DotMatrix what is you deal buddy ?

I'm really wondering if you have issues or something..

Why are people not allowed to have their own way of using windows or opinions other than butt kissing about win 8 ?

DotMatrix what is you deal buddy ?

I'm really wondering if you have issues or something..

Why are people not allowed to have their own way of using windows or opinions other than butt kissing about win 8 ?

I'd rather see Microsoft streamline Windows. Strip away the outdated components, and unify what's left. Unless you're Andrea Borman, do we really need compatibility all the way back to the earliest days of the desktop? Do we really need options for every damn little toggle in the OS? Do we need all this excess baggage in Windows?

I'd rather see Microsoft streamline Windows. Strip away the outdated components, and unify what's left. Unless you're Andrea Borman, do we really need compatibility all the way back to the earliest days of the desktop? Do we really need options for every damn little toggle in the OS? Do we need all this excess baggage in Windows?

So, you want MS to throw out Windows and start fresh? You should ask Netscape how that worked out for them...

So, you want MS to throw out Windows and start fresh? You should ask Netscape how that worked out for them...

It's essentially what they've started to do with Windows 8.

It's essentially what they've started to do with Windows 8.

Not really. They are trying new tricks on the old horse hoping to get it ahead in a new race, but they are racing the same horse. If they were to seriously kick legacy support in Windows to the wayside to the extreme you want they will fade to history faster than the Olson twins.

In the new race they want Windows to get into MS has no serious pull with consumers or developers so they need that legacy card to offer them some possible advantage.

Luckily for them you're not running the show otherwise they'd be looking a lot like RIM.

Not really. They are trying new tricks on the old horse hoping to get it ahead in a new race, but they are racing the same horse. If they were to seriously kick legacy support in Windows to the wayside to the extreme you want they will fade to history faster than the Olson twins.

In the new race they want Windows to get into MS has no serious pull with consumers or developers so they need that legacy card to offer them some possible advantage.

Luckily for them you're not running the show otherwise they'd be looking a lot like RIM.

Extreme? If your app is pre-XP then that's on you. If your company is still actively deploying crap that's pre-2001, that should be on you, not Microsoft. Any code pre-2000's should be considered fair game for the chopping block. To be honest, any reputable software maker should be up to date with Windows 7.

But, yes, they are essentially starting over with Windows 8.

Start Menu - GONE.

Networking window - GONE.

Old Search window - GONE.

Dialog boxes - GONE.

etc...

Extreme? If your app is pre-XP then that's on you. If your company is still actively deploying crap that's pre-2001, that should be on you, not Microsoft. Any code pre-2000's should be considered fair game for the chopping block. To be honest, any reputable software maker should be up to date with Windows 7.

That's where you show how truly clueless you are. Each Windows release builds upon the last. So the #1 software on Windows depending on pre-XP code is Windows itself! If MS drew a line in the sand and stripped anything pre-XP then Windows 8 wouldn't even boot...

That's where you show how truly clueless you are. Each Windows release builds upon the last. So the #1 software on Windows depending on pre-XP code is Windows itself! If MS drew a line in the sand and stripped anything pre-XP then Windows 8 wouldn't even boot...

Vista+ was coded from the Server codebase, not XP. Anything stripped can be replaced by Modern components or unified elsewhere in the system. The Control Panel for one should have been unified under the Modern UI. Microsoft can finally get rid of all these damn control widgets that plague the OS.

Vista+ was coded from the Server codebase, not XP.

:huh: And the "Server code base" came from where? Do you honestly think MS rewrites Windows from scratch regularly? Surely you're not that delusional Dot.

:huh: And the "Server code base" came from where? Do you honestly think MS rewrites Windows from scratch regularly? Surely you're not that delusional Dot.

Do we really need to go all the way back? My point being is, Windows carries so much legacy baggage that it's overdue for a complete overhaul. At some point in time you have to draw the line. A similar point passed around Vista's time. You saw what happened with XP... it was being picked apart by malware after malware. Now, Windows is being picked apart by slimmer, more agile operating systems. Surely that's not cause for concern? Did you not just read the news where users are concerned with the amount of space Windows takes up? Buy a 32 GB Windows tablet, and tell me, how much space do you have left? What do you want Microsoft to do?

Do we really need to go all the way back? My point being is, Windows carries so much legacy baggage that it's overdue for a complete overhaul. At some point in time you have to draw the line. A similar point passed around Vista's time. You saw what happened with XP... it was being picked apart by malware after malware. Now, Windows is being picked apart by slimmer, more agile operating systems. Surely that's not cause for concern? Did you not just read the news where users are concerned with the amount of space Windows takes up? Buy a 32 GB Windows tablet, and tell me, how much space do you have left?

As I said earlier, Microsoft is hoping this legacy support will be their saving grace. So, they don't agree with you here.

Microsoft has deliberately chosen to offer "full" Windows in the tablet space and not a slimmer and leaner mobile focused OS, like they do with Windows Phone. They are hoping that users want this legacy support and that developers do as well. Is MS right? Who knows. But I do know one thing. If users are allowed to pick an OS in mobile they largely don't choose Windows, irrespective of variant. So without the legacy card MS comes to the table with nothing in the new race and they are already a few laps behind.

As I said earlier, Microsoft is hoping this legacy support will be their saving grace. So, they don't agree with you here.

Microsoft has deliberately chosen to offer "full" Windows in the tablet space and not a slimmer and leaner mobile focused OS, like they do with Windows Phone. They are hoping that users want this legacy support and that developers do as well. Is MS right? Who knows. But I do know one thing. If users are allowed to pick an OS in mobile they largely don't choose Windows, irrespective of variant. So without the legacy card MS comes to the table with nothing in the new race and they are already a few laps behind.

If they're dragging the legacy support with them on purpose, then why is the desktop on RT a dead duck? I can't so **** on the desktop besides run Office, and that's Microsoft's own doing!

If they're dragging the legacy support with them on purpose, then why is the desktop on RT a dead duck? I can't so **** on the desktop besides run Office, and that's Microsoft's own doing!

The better question is if the Desktop is a dead duck that is being primed for slaughter then why is it on RT at all to any serious extent? Office could have been sandboxed into a very limited desktop experience.

The better question is if the Desktop is a dead duck that is being primed for slaughter then why is it on RT at all to any serious extent? Office could have been sandboxed into a very limited desktop experience.

Which is why I believe you're going to see the Metro-ification of more elements in Windows 9. Hell maybe even in "Blue".

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

    • No registered users viewing this page.
  • Posts

    • Go for a Echo Dot or Pop instead. These Echo shows just advertise to you.
    • NetSpeedTray 1.3.3 by Razvan Serea NetSpeedTray is a lightweight, open-source Windows network monitor that shows live upload and download speeds directly on the Taskbar. Designed for efficiency, it quietly sits in the system tray, conserving CPU and battery with dynamic updates. It blends seamlessly with Windows 10/11, adapts to light/dark themes, and auto-positions to avoid overlaps. Features include accurate interface detection, customizable display, optional mini-graph, color coding, granular font and unit control, detailed per-interface history graphs, safe data management, and easy CSV export—bringing the network monitoring Windows forgot. NetSpeedTray key features: Lightweight & Efficient Runs quietly in your system tray without consuming resources. Features a "Dynamic Update Rate" that lowers refresh frequency when the network is idle to save CPU and battery life. Native Look & Feel Blends seamlessly with Windows 10/11 UI. Smart detection for light and dark taskbar themes ensures text is always visible. Intelligent & Adaptive Positioning Automatically finds empty space next to your system tray and shifts to make room for new icons, preventing overlaps. Seamless OS Integration Behaves like a native Windows component. Hides instantly with auto-hiding taskbar Hides when a fullscreen app is active Smart Network Monitoring Accurate by Default: Auto mode identifies your main internet connection and ignores noise from VPNs or virtual adapters. Easy Interface Selection: Switch effortlessly between Auto, All, or Selected network interfaces via intuitive radio buttons. Total Visual Customization Free Move Mode: Unlock and place the widget anywhere on your screen. Optional Mini-Graph: Real-time graph of recent network activity with adjustable opacity. Color Coding: Customize colors and speed thresholds to quickly see network status. Granular Display Control Text & Font: Adjust font family, size, weight, and alignment. Units: Automatic (B/s, KB/s, MB/s) or fixed Mbps display. Precision: Set decimal places and always show them for uniform appearance. Detailed & Intelligent History Graph Smart Scale: Logarithmic scale shows low-level traffic and large spikes clearly. Per-Interface Filtering: View speed history for specific adapters (Wi-Fi, Ethernet, VPN). Safe & Efficient Data Management: Adjustable retention, automatic cleanup, optimized database. Easy Data Export: Export raw data to .csv or save high-quality graphs for reports. NetSpeedTray v1.3.3: The Updater Fix A stabilization release that repairs a critical regression in v1.3.2: the app shipped without OpenSSL, which silently broke every HTTPS request — including the built-in update checker (the "Could not check for updates" error many of you hit). This release restores it, hardens the build so it can't happen again, and fixes a startup crash plus four other reported bugs. Changes: Fixed update checking — Resolved a critical issue that prevented the app from checking for updates ("Could not check for updates"). Fixed startup crash with Auto-Cycling — The app no longer crashes on launch after enabling Cycle display mode. Fixed incorrect network speeds on 10GbE adapters — Multi-gigabit network cards now display speeds correctly instead of being stuck at 0. Improved color coding — Default color is shown when idle, and color/threshold changes now apply immediately without restarting. Fullscreen visibility fix — The widget now correctly stays visible over fullscreen apps when Keep Visible is enabled. Improved AMD Ryzen temperature detection — More reliable CPU temperature monitoring for Ryzen processors. Cleaner upgrades — Installer now removes outdated application files during upgrades, preventing DLL/version conflicts while preserving user settings. Improved stability — Fixed potential DLL loading issues by excluding critical OpenSSL and NumPy components from UPX compression. Better settings window — Scrollbars removed and layout improved for a cleaner experience. Localization improvements — Updated translations and completed missing UI text across all supported languages. More reliable releases — Added regression tests covering recent critical fixes, bringing the test suite to 196 passing tests. [full release notes] Download: NetSpeedTray 1.3.3 | 87.9 MB (Open Source) Download: NetSpeedTray Portable | 101.0 MB View: NetSpeedTray Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Why Delta Chat is the best decentralized messenger you have probably never tried by Paul Hill There is no shortage of messaging apps out there; we have WhatsApp, Messenger, and Telegram, just to name a few. While Meta has taken steps to incorporate encryption into Messenger and WhatsApp, they still leave a lot to be desired. If you are in the market for a messaging app that promotes security, privacy, and optional anonymity, you'll want to read what I have to say about Delta Chat. For those not familiar with Delta Chat, rather than relying on centralized servers as you do with Facebook Messenger, it relies on email. Essentially, it is a chat interface that feels like a messaging app, but secretly in the background, it is firing off emails. In the past, you used to have to sign in with your email account. When you sent messages to people, it would just be sending encrypted messages to their inbox, which their Delta Chat client would decrypt. When I first learned about Delta Chat, it required users to sign in with an email account, but I was pleasantly surprised upon trying it in 2026 that this is no longer a requirement, or the preferred method was to use the app. Recently, I’ve tried UAD-ng on my old Nokia 3.4 to disable most of the Google apps because the bootloader is locked, and this is the next best option. While finding replacement apps in F-Droid, I came across Delta Chat again, and it has undergone quite a big change since I last used it, with its new chatmail relays, which no longer require you to sign in to your own email account, providing anonymity, and they offer greater security. Android and Desktop Delta Chat apps. Not only does it run on my de-googled phone, but it also works on desktop computers and iOS, making it truly ubiquitous. For me, Delta Chat is a wonderful alternative messenger because it gives you more control. It supports switching between different profiles, which you can set up super quickly; you don’t register a username, you don’t register a password. The only thing you do have is a random string email address on a chatmail relay (which you don’t have to memorize). To maintain access to your profile, you just need to add a second device to your account via QR code or make a backup of your account, which you can restore later. Fail to do these, your account is gone - as it should be if you don’t want to leave accounts that could get hacked later on. My decision to block Google stuff on my Nokia was done for practical reasons; the device sucked when it launched, and it sucks even more now. The nice thing about F-Droid and the apps within is that they’re usually lightweight, free of bloat, and work well on that device. What was inconvenient for me was that it was hard to send messages from that device, say if I wanted to copy a code over to my main phone or send family members a link from that device. That’s when I decided to look at the available chat apps and saw Delta Chat. Another nice thing about Delta Chat is its notifications. Some messaging apps rely on Google’s ecosystem for notification transport on Android; however, with Delta Chat, it can use Google’s solutions if you have Play Services or MicroG installed. Otherwise, it is able to keep a background connection to the chatmail relay server so that you can get notified when you receive a message. As free software, the code of Delta Chat is open for all who want to take it and build upon it. In the future, if the developers of Delta Chat make a catastrophically bad decision and take the app in an undesirable direction, users can take the code and fork the project. This contrasts with closed-source apps from corporations that can take their products in any direction they like. By relying on free software instead of closed-source programs, you actually control your computing. I’ve spoken at length about how running this type of software is like owning your own home rather than renting it. The same applies here; if you use Delta Chat, you don’t need to worry about it going away in the future. Whether it is Telegram, WhatsApp, or Messenger, you are required to register a username and password to use these services. A major flaw in this design is that anyone can try various passwords and potentially break into your account with your complete chat history intact. Sure, there is encryption in Messenger, where you need a second PIN and two-factor authentication in Telegram, but breaches happen all the time. Unlike before, when you used to sign in to your email account to send and receive messages, the primary way to do it now is to create an account on a chatmail relay. The resulting email address is a random string followed by the name of the relay you pick. This means you can start and begin adding contacts Without a username and password, you either need to ensure you have a backup or at least one device running your Delta Chat profile. The primary way to log in on another device is to go to the settings and add a second device. Then, you’ll just scan a QR code with your new device, and it’ll log in to your account and sync all your chat history and contacts. To end users, Delta Chat just looks like any instant messenger; however, it is really sending your messages as encrypted emails to your contact. This is pretty cool from a censorship perspective, as it makes the service more difficult to block. Previously, the main way to use the app was by logging in with email, but nowadays, it’s recommended that you use chatmail relays. Chatmail relays temporarily hold messages in case your device is offline. They are cheap, simple servers that don’t store data as group states. Other information, like your name and avatar, only exists on your device and the devices of those you share your contact information with. The relays are also decentralized and operated by various groups and individuals. It is even possible to set up your own chatmail relay, but most people will want to use one hosted elsewhere. To keep your messages secure, Delta Chat uses a secure subset of the OpenPGP standard that gives you automatic end-to-end encryption. It also uses Secure-Join to exchange encryption setup information through QR-code scanning or invite links. Autocrypt is also used to automatically establish end-to-end encryption between contacts and all members of group chat, but sometime this year Autocrypt v2 will be rolled out, bringing post-quantum resistant encryption and forward secrecy. The Delta Chat FAQ is an interesting read that explains many more details about the app. Credit: Pexels Delta Chat is unique among messaging apps because it is built on email, a technology that’s decades old and isn’t going anywhere soon. What’s more is that email is not centralized either, so it’s far more difficult for any authoritarian regime to disrupt the Delta Chat app. I haven’t spoken too much about features yet, so I will do that now. Delta Chat allows you to do one-on-one chats, group chats, and create channels. It also supports file sharing and making audio and video calls when chatting one-to-one, but it’s not available for group chats right now. At the time of writing, the calling functionality is disabled and can be enabled in Settings > Advanced > Debug Calls. I have used the video calling feature, and the quality is excellent. It works over WebRTC, another open standard. The app also lets you send voice notes, enables disappearing messages, and has its own app ecosystem. I did try playing chess one time there, but it was a bit spotty; though, we did manage to complete the game with a victory for me. To add people to Delta Chat, you can either give them your Delta Chat link or your QR code to scan. These are the only ways to add users, so you won't have any spam bots bothering you. If the people you want to chat with don't have the app yet, just send them your link, and it will take them to a webpage where they can install the app and then add you. It's really quick for them to install it and get started, which is nice. Credit: Microsoft. The Majorana 2 quantum chip unveiled in 2026. I do not think quantum computers are too far out now, and I do hope that Delta Chat is able to push out Autocrypt v2 sooner, rather than later, so bad actors do not attempt to collect encrypted communications and then decrypt them in the future using quantum computers. By getting people’s messages post-quantum-safe now, users won’t have to worry when quantum computers start cracking legacy encryption. Overall, I would recommend this app to people who are already past WhatsApp and Messenger and have perhaps begun using apps like Telegram or Session. It shares a lot of characteristics with these apps and goes a lot further than Telegram in terms of security. By being based on email, it is also resistant to censorship, and the lack of a username and password makes you anonymous (if you want to be) and safe from brute force password cracking attempts. Let me know in the comments if you’ve tried Delta Chat recently. Do you think it's a good bulwark against governments that are tightening their grip on the internet?
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!