Forum Discussion
Stable version of Edge insider browser
- Thanks for the discussion. We feel this has come to a natural conclusion, so we are closing this off to new comments - it's good to be aware of using content from other sites, but we do understand this was used to help make an argument rather than passing it off as your own content. But it doesn't seem like anything productive will come from further discussion here.
tomscharbach wrote:HotCakeX "Public means it is accessible by 7 billions people on this planet. [T]hat sounds meaningful enough to me."
We are using the term "public" in two different senses.
The best way to think about the "Stable" deployment (both this deployment and the one we discussed 6-8 weeks ago), perhaps, is to think in terms of a "pre-production environment", that is, deployment on the actual server from which the release version will, in time, be released, but deployed in a way that the version is not accessible to the public. That does not mean that a hacker cannot, through luck and diligence, find the build and "leak" the URL (common enough), but it does mean that the build is not "public" in the sense that Microsoft wants outsiders testing or using the build.
In this case (as was the case with the earlier "Stable" version) a person needs to know the exact URL to get to the build. Microsoft has not provided a path to the "Stable" version through the Edge Insider site or the Office365 site, and coding of the URL removes the site from web search engines. That tells me, anyway, that Microsoft did not intend for this version to be tested or used by the public, but instead intended the version to be "deployment tested" internally from a production server that will, in time, be used for deployment.
The practice of pre-production testing is standard in the industry, or at least that was the case when I was working in an enterprise IT environment. (I have to remind myself that I have been retired more years than many IT folk in their 20's and 30's have been working, so the concept of pre-production testing may have gone the way of the dinosaurs for all I know.) But unless things have changed in that regard since my working days, pre-production deployment testing is probably still a requirement for deployment. If it isn't, it should be, particularly in a case like this, where installation is complicated and appears to involve changes to the Windows 10 environment.
Do you mind telling us where you got the URL? It is just idle curiosity on my part, so if you don't want to, no harm, no foul.
I think that we've reached the end point of usefulness in this discussion.
I think you need to read a lot about how files work on servers and how securing them is done.
Microsoft Creates servers and data centers, I think they know pretty well how to secure a simple file and how to restrict it to their employees only.
I already know they haven't published the link on their websites, I said that in my first post. but it is Not necessary anyway. it's not hard to find what's publicly available on a server.
there are certain, and very basic to be honest, rules and protocols that define how securing a file on a server must be done, properly.
the file (stable Edge browser) on their server is Not secure, Not private and it IS public. period
unless you get an "Access Denied" error then it is public.
there are links to all kinds of operation systems and software on Microsoft servers that are otherwise hidden by website UIs, forms and such 🙂
but none of them are unintentionally or by mistake put there, just like the stable version of Edge is Not unintentionally or by mistake put there for Public to be able to download.
HotCakeX "... just like the stable version of Edge is Not unintentionally or by mistake put there for Public to be able to download ..."
I take it that you think that Microsoft intends that members of the public-at-large download and install the so-called "Stable" version. For what purpose?
- Yes i'm sure,
when I said resurfaced I meant the link is resurfaced on the web again HotCakeX "I don't think so, the last link is still working 😉"
Are you sure? As I remember, the link to the former so-called "Stable" version was deactivated shortly after you published the URL on this Forum, and (as you point out above) the URL seems to have "resurfaced" (as you put it) to permit download of the newer so-called "Stable" version.
Whether I remember right, or not, about whether the link URL was deactivated earlier, the "new" link is identical to the "old" link that you published on 08-25-2019 05:01 AM in a thread discussing the earlier so-called "Stable" version.
I clicked on both a few minutes ago (the link in this post and the link in the 08-25-2019 thread), and both download the same file, the current so-called "Stable" release.
I think you were correct earlier in the thread when you characterized the situation as "resurfaced". Or perhaps "reactivated" when referring to the link itself.
- I don't think so, the last link is still working 😉
HotCakeX " [I]t's been in lots of tech news sites and Microsoft knows this too and haven't taken down any of the links."
Hold on and it will probably go down. That's what happened with the last so-called "Stable" version. This has got "ooops" written all over it.
- Spoiler
tomscharbach wrote:HotCakeX "... just like the stable version of Edge is Not unintentionally or by mistake put there for Public to be able to download ..."
I take it that you think that Microsoft intends that members of the public-at-large download and install the so-called "Stable" version. For what purpose?
If i knew that I wouldn't make this post to ask Them that.
and yes the public can and is downloading it even right now. it's been in lots of tech news sites and Microsoft knows this too and haven't taken down any of the links.