OK, besides feeling embarrassed as hell at the last post that turned out to be nothing more than a rant, I also feel guilty that this did not go up as soon as I had promised earlier; but that’s that, and here is the post ;)<\/p>\n
Basically this can be summed up in one sentence, or even, a fragment of a sentece: Where do those builds come from?<\/strong> <\/p>\n Funny how this turns out to be such a short post, eh?<\/p>\n","protected":false},"excerpt":{"rendered":" OK, besides feeling embarrassed as hell at the last post that turned out to be nothing more than a rant, I also feel guilty that this did not go up as soon as I had promised earlier; but that’s that, … Continue reading
I’d really like to know. Its not just 5259 here; I mean every single build out there that gets reported as “Stolen” then “Released;” how do they steal<\/em> a program that has not been released? At the risk of stating the obvious: Doesn’t it seem as if the builds are leaked from within<\/strong> the company???<\/em> Its not just Microsoft either. When you have leaked versions of internal builds for Symantec, McAfee, WindowsBlinds, and all the rest, it makes you wonder: from where?<\/p>\n