When I followed this link via Chrome, a tool tip popped out of my address bar ("Did you mean reactjs.org?" with some warning about attackers using deceptive URLs). I wonder if there's a way to whitelist URLs with Google to prevent users from seeing this message. Especially since I believe ReactOS has been around long before ReactJS
ReactOS Updates
11–20 of 142 posts
Re: ReactOS Updates
#12The way Microsoft is moving, it's feasible to think that Windows 2000/XP will be open sourced before ReactOS is finished.
Re: ReactOS Updates
#13Re: ReactOS Updates
#14When I followed this link via Chrome, a tool tip popped out of my address bar ("Did you mean reactjs.org?" with some warning about attackers using deceptive URLs). I wonder if there's a way to whitelist URLs with Google to prevent users from seeing this message. Especially since I believe ReactOS has been around long before ReactJS
Re: ReactOS Updates
#15NTFS? Impressive.
That sounds like ntfs worked already if you had an existing non-boot partition.
Re: ReactOS Updates
#16Is ReactOS capable of running all the Windows software OK already? I'm curious if I can actually use it instead of Windows whenever I need a Windows VM.
ReactOS is a cool project, but it's an alpha-stage complete operating system with bugs as basic in nature as you shouldn't even expect the file system to live long without being corrupted, or the OS crashing constantly. Not to mention they primarily focus on Windows XP compatibility, Vista and newer software is generally unlikely to work.
Re: ReactOS Updates
#17Edit: reference to the question
https://www.quora.com/What-do-you-think-about-ReactOS?share=...
Re: ReactOS Updates
#18When I followed this link via Chrome, a tool tip popped out of my address bar ("Did you mean reactjs.org?" with some warning about attackers using deceptive URLs). I wonder if there's a way to whitelist URLs with Google to prevent users from seeing this message. Especially since I believe ReactOS has been around long before ReactJS
The best way to avoid having Google interfere with your browsing is to use a non-Google browser.
Re: ReactOS Updates
#19NTFS? Impressive.
-----
Dirty rumour + speculation time: I understand that, to an extent, ReactOS is supported by the Russian government to ensure they have options for running their IT systems in the event of US or NATO-led sanctions which would prohibit service and support from Microsoft corporation. Ordinarily I wouldn't be concerned (geopolitics, yey) but given Putin's current direction... I hope ReactOS is getting suitably security audited...
Re: ReactOS Updates
#20When I followed this link via Chrome, a tool tip popped out of my address bar ("Did you mean reactjs.org?" with some warning about attackers using deceptive URLs). I wonder if there's a way to whitelist URLs with Google to prevent users from seeing this message. Especially since I believe ReactOS has been around long before ReactJS
Stop using Chrome? :D
But for legitimate communities building honest software (or any honest product, really), it can be harmful to have potential users/contributors being scared off by a message like this. At the very least, it can make visitors question the legitimacy of the product. Since ReactOS has been around for decades at this point, it seems as if they're suffering a penalty for not being as popular as ReactJS, which is kind of bullshit, if there's no way for ReactOS (and other legitimate companies which may be affected) to let Google know "hey, we're doing our own thing, would you please mind not scaring potential users away". Whether or not I use Chrome, at least 60% of Internet users do. And I've never seen a warning when visiting reactjs.org asking if I didn't actually mean reactos.org, so the axe doesn't swing both ways here.