Comment: Slahdot gets it wrong as usual (Score 4, Insightful) 183
Comment: Re:No way buddy. (Score 2) 123
Comment: Re:Please stop.... (Score 1) 291
-- Along with the versioning scheme comes lack of support for older versions
Actually, 3.6.x gets security updates to this day.
-- The version scheme is a pain in the neck for add-ons, which depend on versions
Every add-on worth installing has long since adapted and anticipates several versions in advance. I've never had a problem.
-- Normal version numbers give the user information; the version number tells us whether it has had major features, bug fixes, etc. Firefox's versioning has the effect of concealing this information from the user.
Yes. Like I said, it's silly. It's also not a big enough thing to make this huge fuss about, much less to stick to old and buggy versions. In my experience, FF has been getting much better and faster.
Comment: Re:Please stop.... (Score 5, Insightful) 291
Comment: Re:it's all the same root cause (Score 1) 171
Comment: Re:it's all the same root cause (Score 1) 171
Comment: FFS. (Score 5, Insightful) 171
Comment: Re:Easy solution (Score 1) 318
Comment: Re:Skype v SIP (Score 1) 236
The way Skype solves this problem is by identifying clients that aren't behind NAT. Those clients are used to proxy the media for other clients that are behind NAT. In other words, if you use Skype and you aren't behind NAT, there's a good chance you will be carrying traffic for those that are behind NAT.
That is not correct. The Skype proxy actually punches holes in the NAT on both ends so they can talk directly. See http://www.h-online.com/security/features/How-Skype-Co-get-round-firewalls-747197.html.
Comment: Been there, done that (Score 1) 480
I did pretty much exactly this, starting in 2004. It looks like you have the opportunity to make this fun for yourself. Show some initiative and try something new. Off-hand, my advice would be:
- Keep it simple, stupid. For a network that small, consumer-grade routers in combination with a few medium-grade switches will do fine.
- Screw the cloud; host everything yourself. You don't want confidential company data on computers managed by strangers.
- If non-Windows desktops are acceptable, I've had great success with Linux in combination with Linux Terminal Server Project. Saves boatloads on licensing costs and desktop hardware. You get to centralize all the management for free. LTSP comes integrated in Debian and a few other distros. There's a learning curve but it's very much worth it. XFCE makes for a good lightweight end user desktop environment.
- Even where Windows desktops are required, have all the network services run on Linux. No hassle with licenses and restrictions.
- Become fluent in Linux/UNIX shell. It's convenient and very powerful.
Comment: Re:The Mac sucks for all kinds of development! (Score 1) 831
The Mac also has a dearth of good code editors. On Linux, I really liked nEdit.
You claim to be aware of the existence of MacPorts, yet it never occurred to you that you can just use nEdit (or any other "Linux" editor) on the Mac?
Comment: Re:Better service.. (Score 1) 133
The record companies wanted to raise prices, particularly on the one or two hits that'd otherwise sell an album but Apple refused.
Actually, Apple has been allowing that since April 2009.
Comment: Re:SURVEY SAYS?? ...Meh. (Score 1) 327
1. All server-to-server communication is TLS encrypted and authenticated. All wave origins are verified using digital signatures, so, to quote from wikipedia,
Therefore, a downstream wave provider can verify that the wave provider is not spoofing wavelet operations. It should not be able to falsely claim that a wavelet operation originated from a user on another wave provider or that it was originated in a different context.
Thus, spam really ceases to be an issue
This reflects a common and unfortunate misunderstanding about spam. The vast majority of spam does not forge the sender and has no need to. Most spammers want responses, after all. Besides, email has already solved this problem (SPF, DomainKeys) and it did nothing to deter the spammers. Phishers now simply register domains that look similar to the real ones. Spammers register domains in bulk so they don't care if they get blocked or shut down. Wave would do nothing to solve any of this. Spam is a social problem, not a technical one, so it can only have a social solution.
2. Waves can be embedded. Blog comment sections can be replaced by waves; forum threads by waves. All comments would appear in your inbox. Email cannot even hope to replicate this other than with the clunky-and-annoying "notify me when someone responds" forum setting.
That is not a problem with email, but a problem with blogs. Besides, what is the difference between "notify me when someone responds" and "all comments would appear in your inbox"? Nothing is stopping blogs from sending all comments to your inbox now. There is a reason why they don't usually do that, and that reason would apply equally to Wave.
3. You can easily add people to the discussion. The only way to do so with email is to re-forward the whole chain of emails to them and ask them to reply-all; or to include them in the next reply-all and hope that noone else responds first. This is a pretty glaring flaw of email that Wave fixes.
Mailing lists fixed this in the 1970s. Even simple mailing lists are more efficient for discussions than Wave and blogs combined. All you need is a decent email program with threading and filtering. The recipient is in total control, and it's simpler to learn than Wave.
4. There are of course a ton of other reasons why Wave was more than just "chat with a couple of features", but these were big. Wave had the chance to completely redo how we communicated,
You bought the hype. But even if this were true, it would have put Google in total control of all our communications. No thanks.