Forgot your password?

Comment: Re:Yahoo does make money. (Score 4, Informative) 108

by Whip (#46788079) Attached to: Investors Value Yahoo's Core Business At Less Than $0

Not just "popular" -- Yahoo News is the #1 news site in the world (by traffic), Yahoo Finance is the #1 finance site in the world, Yahoo Sports is one of the top three sports sites in the world (tends to bounce around a little), and Yahoo as a whole trades the #1 ComScore spot back and forth with Google quite regularly.

I'm sure there's a lot of "hip" companies out there that *wish* they could even come close.

Comment: Re:Seems reasonable. (Score 1) 262

by Whip (#45785189) Attached to: Linux x32 ABI Not Catching Wind

So, I'm not sure about how the current linux implementations work, but when Solaris went 64-bit, they added an optimization where when you run an *unchanged* 32-bit executable, the libc would recognize that it's on a better processor, and use the improved features of the processor in places that it could, for performance. So, for example, if you called memcpy(), it would use 64-bit load/store instructions (and registers) to copy, giving you twice (or more) the performance for those calls, with no changes to your old code -- you don't even need the source code available!

Is this at all what is intended to be possible with the x32 implementations on linux, now? That would be an additional advantage that I haven't seen mentioned yet.

Comment: Re:Mod parent up. (Score 4, Informative) 257

The magic words you're looking for on accounts are "with rights of survivorship," which will give the named individuals direct access even after one dies. It's something you can just ask for on a joint account (if they don't give you the choice directly). I have my savings & investment accounts (and my deposit box) set up this way -- the last thing I want is for my partner to have no access to funds immediately after my passing.

Comment: So, why can't it... (Score 1) 158

by Whip (#39648955) Attached to: Mosh: Modernizing SSH With IP Roaming, Instant Local Echo

Why can't they add local echo, predictive typing, and resumable sessions to ssh or another TCP-based protocol? Yes, TCP can *possibly* take longer to recover from network errors, but this isn't something where you can just drop some missing packets (like some audio streaming things) to keep things flowing.

It's implemented over UDP, which means you *still* have to basically do all the functions of TCP, but now you get to do them with code that hasn't been tried and tested over the past several decades. Plus a new crypto implementation on top of that. And for what? Slightly better response time during network loss, which you shouldn't notice anyhow because of the predictive typing?

UDP just seems to solve no real problems, yet *adds* a lot of problems -- the firewall problem, for one. Fresh new daemon with unknown security issues.

I see no reason why you couldn't just tunnel this over ssh and get the vast majority of the benefits -- or better yet, patch the predictive typing/session resume/etc into ssh directly. Then you get to take advantage of the decades of work and bugfixing that's already been done for the majority of your protocol stack.

(And I don't buy for a minute that it's significantly more difficult to handle session resume when it's a TCP connection...)

Comment: If only it didn't suck! (Score 4, Informative) 537

by Whip (#35984816) Attached to: On Monday, AT&T Customers Enter Era of Broadband Caps

The caps wouldn't be that bad if the service didn't *utterly* suck.

The gateway they give you is the only thing that works with the service (you can't use your own hardware, or at least nobody has found a way to). It won't do any kind of bridge mode. It won't talk to more than one IP per MAC address, so you can't put a router behind it (unless that router is doing NAT for *everything*). It randomly drops connections, especially long lived ones -- I can't make local backups of my server in a remote datacenter anymore, because the connection will almost never stay alive long enough to transfer the whole ~400MB. Sometimes it starts blocking random incoming connections, even to static, un-natted, unfirewalled addresses -- one day I can't get to my webserver from the outside world for a few hours... the next I can't ssh into my home server ("unknown inbound session stopped" ... of course it's unknown, it's the first packet of a new connection, you piece of garbage). It supports logging to syslog, but outputs a constant stream of useless messages so thick that it's almost useless.

Recently I've started to notice having periodic problems downloading content (like the slashdot style sheet!) from akamai-based sites, which a little bit of goggling shows to be an ongoing U-Verse problem since 2008.

The support sucks massively. If you call with basically any problem beyond "my internet is down" they will forward you on to their "advanced" support department, who has a fee of $39 (might be $29... don't remember)... which they'll charge you even if all they do is tell you that they can't help you and you need to call regular support.

Netflix, on my 24Mbit downlink, varies from "great quality" to "OMG you can barely do SD quality"... many other people report this as well. Some days the performance is great, some days the performance is just absolutely miserable. I'd try to see if there was some common network path causing problems, but they basically disable traceroute for all of their internal nodes (I'm guessing they just stop them from sending TTL exceeded datagrams completely).

You can't switch back to ADSL -- they wouldn't even let me get U-Verse service unless they disconnected my ADSL at the same time. But it is "no longer available" so now I'm stuck with this garbage.

I'd gladly take a usage cap if it meant any of this crap would get better. I'm somehow doubting it, since not a bit of it seems like it's related to network saturation... just lousy service. And my only other choice in this area (AFAIK) is Comcast, who also has caps, along with their own set of problems...

I'd say "welcome back to the 90s" ... but my network worked a lot better back then. So I guess... welcome to the future!

Someone is unenthusiastic about your work.