Article View: alt.games.warcraft
Article #351900Re: *wind whistles*
From: Lewis
Date: Wed, 13 Apr 2016 08:25
Date: Wed, 13 Apr 2016 08:25
72 lines
5259 bytes
5259 bytes
In message <570dd318$0$23320$b1db1813$6557...@news.astraweb.com> | || ||| ||||| || | <|||||||||||||||||||||> wrote: > On 12/04/2016 9:19 PM, Urbin wrote: >> On Tue, 12 Apr 2016 10:43:31 +0100, Catriona R wrote: >>> On Tue, 12 Apr 2016 09:29:11 -0000 (UTC), Lewis >>> <g.kreme@gmail.com.dontsendmecopies> wrote: >>> >>>> In message <d0a705ed-3c6d-4667...@googlegroups.com> >>>> Shinnokxz <shin...@gmail.com> wrote: >>>>> And that's that with Nostalrius. Too bad. >>>> >>>>> Though it appears the vanilla server community and outcry has reached >>>>> levels it's never been before. Sooner or later Blizzard is going to >>>>> have to breach the subject and offer something up. >>>> >>>> No they will not. >>>> >>>>> The shutdown was typical Blizzard show, but really pissed on the >>>>> people looking for a reason to even bother with WoW anymore. I suspect >>>>> when Legion is released and subscribers have reached an all time low >>>>> post-xpac release, then Blizzard will consider giving it a whirl. >>>> >>>> No. That is never going to happen. >>> >>> That's a pretty confident assertion, I don't think anyone can say >>> "never" with Blizzard. >> >> While that is true... >> >>> Times change, and right now they're throwing away money by not offering a >>> service which would have interested a LOT of people >> >> ... but I am not convinced that operating vanilla servers would be >> economically viable for them. I don't know the inner workings of Blizzard >> but being a software developer I can tell you that at any company I have >> ever worked at, it would have taken quite a lot of effort to revive a >> software version of 10 years before. Apart from that effort, it would also >> mean running the servers (and while a lot of that is certainly automated, >> there is sure to be some human work required as well) and some kind of >> support infrastructure. >> >> And 15k (or even 150k) players sounds like a lot, that would justify a >> handful of servers and I doubt that the economies of scale would work for >> that low a number. >> >> So even considering people would be willing to pay a full subscription to >> play on vanilla servers, I am not sure it would pay. > It doesn't have to cost them, people have demonstrated they are willing > to do it without their involvement. Really, they don't need any Blizzard > support at all :-). No. Allowing third parties to run servers would endanger every Blizzard Trademark and could also jeopardize their copyrights. > All they need to do is establish some sort of mechanism so to play on > the 'Authorised but UNSUPPORTED BY BLIZZARD server' > caps part of name :-) It is not that simple, at all. > you need a Warcraft account that is active, or maybe has been active in > the last 3 months. Money for stuff all effort, a tiny bit of handshake. So this third party has to be able to authenticate against battle.net. Oh, and you have to patch WoW 1.x to work with Battle.net, too. -- Mister Teatime had a truly brilliant mind, but it was brilliant like a fractured mirror, all marvelous facets and rainbows but, ultimately, also something that was broken. --Hogfather
Technical Details
Message-ID:
<slrnngs0p7.11na.g.kreme@amelia.local>Path:
mbox-mo1.pugleaf.net!10ni11939qgx.0!nntp.google.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!kreme.eternal-september.org!.POSTED!not-for-mailReferences:
<dkerobF8t7lU1@mid.individual.net> <slrnne5otu.1go6.g.kreme@amelia.local> <dkgi6gFmg3cU1@mid.individual.net> <56e411c1$0$52718$b1db1813$e2fc9064@news.astraweb.com> <slrnne8bht.20ln.g.kreme@amelia.local> <dl3o81Fkbb0U1@mid.individual.net> <56ed034c.679228@News.Individual.NET> <dlicoaFcrahU1@mid.individual.net> <d0a705ed-3c6d-4667-ab2c-875ce3b4359d@googlegroups.com> <slrnngpg5f.k46.g.kreme@amelia.local> <dn3ua5FcvtU1@mid.individual.net> <slrnngpo5u.m72.urbin@stinky-local.trash.net> <570dd318$0$23320$b1db1813$65575428@news.astraweb.com>Show Full Headers
Complete Article Headers
X-Received: by 10.182.246.135 with SMTP id xw7mr4915078obc.19.1460536102925; Wed, 13 Apr 2016 01:28:22 -0700 (PDT) X-BeenThere: alt.games.warcraft@googlegroups.com Received: by 10.140.93.165 with SMTP id d34ls5476324qge.89.gmail; Wed, 13 Apr 2016 01:28:21 -0700 (PDT) X-Received: by 10.140.92.208 with SMTP id b74mr4911163qge.21.1460536101975; Wed, 13 Apr 2016 01:28:21 -0700 (PDT) MIME-Version: 1.0 Path: mbox-mo1.pugleaf.net!10ni11939qgx.0!nntp.google.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!kreme.eternal-september.org!.POSTED!not-for-mail From: Lewis <g.kreme@gmail.com.dontsendmecopies> Newsgroups: alt.games.warcraft Subject: Re: *wind whistles* Date: Wed, 13 Apr 2016 08:25:01 -0000 (UTC) Organization: Miskatonic U Lines: 72 Message-ID: <slrnngs0p7.11na.g.kreme@amelia.local> References: <dkerobF8t7lU1@mid.individual.net> <slrnne5otu.1go6.g.kreme@amelia.local> <dkgi6gFmg3cU1@mid.individual.net> <56e411c1$0$52718$b1db1813$e2fc9064@news.astraweb.com> <slrnne8bht.20ln.g.kreme@amelia.local> <dl3o81Fkbb0U1@mid.individual.net> <56ed034c.679228@News.Individual.NET> <dlicoaFcrahU1@mid.individual.net> <d0a705ed-3c6d-4667-ab2c-875ce3b4359d@googlegroups.com> <slrnngpg5f.k46.g.kreme@amelia.local> <dn3ua5FcvtU1@mid.individual.net> <slrnngpo5u.m72.urbin@stinky-local.trash.net> <570dd318$0$23320$b1db1813$65575428@news.astraweb.com> Injection-Date: Wed, 13 Apr 2016 08:25:01 -0000 (UTC) Injection-Info: kreme.eternal-september.org; posting-host="67a6ffcad0084cff2eaf00478b4e9e19"; logging-data="6568"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX1+A2VyyDtS47sRajCB+Atxq" User-Agent: slrn/1.0.2 (Darwin) X-Face: )^b5"R:T7U>9~:PEn3YkzMfW*[b1qKeU.fP9C8~8HpU9}lA&6`bH1z Cancel-Lock: sha1:QLa8JeNhbp+NuYesGYRbz1ggghU= X-Clacks-Overhead: GNU Terry Pratchett Mail-Copies-To: nobody Bytes: 4797 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit