We do not use offshore support departments in India!
I would so like a technical support engineer in India who isn't trying to imitate a US accent. My problem isn't with the Indian accent, it is with the US/British accents that they try to imitate.
Oddly enough, Bangalore's suburbs have a far higher population density than the central city. This is mostly because the new housing in the suburbs is multi-storeyed buildings, while the old town is single houses.
A middleman is someone who does not produce, not consume, but routes a product or service from a producer to a consumer. Someone like a shopkeeper, or a broker.
And no, not all Indians are bad at English. And your comments about the western world were stupid and ignorant. Perhaps you need to learn more about how the world really is.
I don't know many FOSS projects using "project management" and scheduling software. The code is ready when the developer(s) say(s) so. If it takes longer, it takes longer.
That is just bad programming. The people writing the query/gateway should check for a NULL as opposed to the string 'null'. Oh well, there _is_ http://thedailywtf.com/
Also, null@example.com is a perfectly valid email address. The only reserved ones are postmaster@example.com and abuse@example.com. Other commonly used addresses may also be reserved, such as root, hostmaster, webmaster, sales, etc. NULL is not in that list.
In this case, it is the fault of the developers for assuming that null@domain is invalid. They should have used a domain like example.com for testing.
Verizon's fault is accepting messages for invalid accounts in the first place, but your objection is null and void.
I did. Apple is not value for money for me. Battery life is probably the least important feature for me (30 minutes is good enough). Performance, OTOH, matters. And price.
Maybe in the US. In India, the only Macs I have seen belong to either Americans (or a few Europeans), or someone who has been given a Mac by the company. The popular geek portables are the Acer Turion based laptops (at ~ 1K USD), since battery life is not the important criterion for a portable here.
Getting access to electric power is easy, it is the price that is a killer issue.
Your loop is essentially a fixed cost. On top of this, there are administrative cost and there is a cost associated with how much bandwidth is being used. The bandwidth cost is not very variable, but it can appear quite high (it does get split over multiple users and is oversold).
Encouraging local P2P makes sense, particularly if you are peering locally The P2P traffic ideally should never go to a paid upstream. What can happen is that smaller ISPs end up uploading much more data than before, making it more reasonable for them to actually peer with others instead of just buying transit. This actually can reduce costs for smaller ISPs.
The problem is when ISPs want to keep overselling in the same ratio as before in assymetric streams, which doesn't quite fit the bandwidth usage model. All that is required is that the ISP start selling symmetric bandwidth, and life will be much easier on both sides.
Circuit switching would be the equivalent of private transport as it stands in the US today. Packet switching is more of a mass transit equivalent. Keep in mind that traffic engineering allows you to push the buying more bandwidth/lighting fibre from the 60% to the 70% mark (also known as a couple of quarters away, and then the whole amount you pend on TE is wasted).
The choke isn't at the backbone, it is near the edges, where the primary overselling occurs. DSL is oversold at high ratios, and when the DSLAM begins to choke, the only decent alternative is to push more bandwidth into that POP.
You still didn't get the point. We handle half a billion messages a day (thats inbound only). We _know_ about stopping spam via protocol errors.
There are no such things as non business hours for us.
We are already stretched to the max with the current load of spam. If we start using greylisting, spammers have a huge incentive to fix their implementations (or start retrying -- they already do after 2 minutes, regrdless of the status of the previous run).
Slashdot Mirror
We do not use offshore support departments in India!
I would so like a technical support engineer in India who isn't trying to imitate a US accent. My problem isn't with the Indian accent, it is with the US/British accents that they try to imitate.
Oddly enough, Bangalore's suburbs have a far higher population density than the central city. This is mostly because the new housing in the suburbs is multi-storeyed buildings, while the old town is single houses.
The US is _not_ open in the areas where the third world is better. The US is open in arwes where Europe, Japan and the US are competitive.
Unhappily for the US, India and china are now competitive in some of those areas.
The technology for validating email has been present for years. GPG, PGP, S/MIME...
Change your ident.
A middleman is someone who does not produce, not consume, but routes a product or service from a producer to a consumer. Someone like a shopkeeper, or a broker.
And no, not all Indians are bad at English. And your comments about the western world were stupid and ignorant. Perhaps you need to learn more about how the world really is.
I don't know many FOSS projects using "project management" and scheduling software. The code is ready when the developer(s) say(s) so. If it takes longer, it takes longer.
FOSS projects definitely assert copyright. They don't assert patent control. Public domain software doesn't do either.
Hiss on line 3, something about being compared to lawyers and libel....
Some people have much longer names. And I mean really, really long names.
f dscxhgb7kc?method=4&dsid=2222&dekey=P.+V.+Narasimh a+Rao&gwp=8&curtab=2222_1&sbid=lc06b
http://www.answers.com/main/ntquery;jsessionid=2b
That is a fairly short name.
That is just bad programming. The people writing the query/gateway should check for a NULL as opposed to the string 'null'. Oh well, there _is_ http://thedailywtf.com/
"null" != null.
Also, null@example.com is a perfectly valid email address. The only reserved ones are postmaster@example.com and abuse@example.com. Other commonly used addresses may also be reserved, such as root, hostmaster, webmaster, sales, etc.
NULL is not in that list.
In this case, it is the fault of the developers for assuming that null@domain is invalid. They should have used a domain like example.com for testing.
Verizon's fault is accepting messages for invalid accounts in the first place, but your objection is null and void.
Google can afford to lose data. Financial groups in organisations can't.
I did. Apple is not value for money for me. Battery life is probably the least important feature for me (30 minutes is good enough). Performance, OTOH, matters. And price.
Maybe in the US. In India, the only Macs I have seen belong to either Americans (or a few Europeans), or someone who has been given a Mac by the company. The popular geek portables are the Acer Turion based laptops (at ~ 1K USD), since battery life is not the important criterion for a portable here.
Getting access to electric power is easy, it is the price that is a killer issue.
Actually, think about that again.
Your loop is essentially a fixed cost. On top of this, there are administrative cost and there is a cost associated with how much bandwidth is being used. The bandwidth cost is not very variable, but it can appear quite high (it does get split over multiple users and is oversold).
Encouraging local P2P makes sense, particularly if you are peering locally The P2P traffic ideally should never go to a paid upstream. What can happen is that smaller ISPs end up uploading much more data than before, making it more reasonable for them to actually peer with others instead of just buying transit. This actually can reduce costs for smaller ISPs.
The problem is when ISPs want to keep overselling in the same ratio as before in assymetric streams, which doesn't quite fit the bandwidth usage model. All that is required is that the ISP start selling symmetric bandwidth, and life will be much easier on both sides.
Been there, don't want to do it again. You basically stop using the Internet if the service is being metered.
Circuit switching would be the equivalent of private transport as it stands in the US today. Packet switching is more of a mass transit equivalent. Keep in mind that traffic engineering allows you to push the buying more bandwidth/lighting fibre from the 60% to the 70% mark (also known as a couple of quarters away, and then the whole amount you pend on TE is wasted).
The choke isn't at the backbone, it is near the edges, where the primary overselling occurs. DSL is oversold at high ratios, and when the DSLAM begins to choke, the only decent alternative is to push more bandwidth into that POP.
Think different.
Think single user Unix.
Marry the daughter. That is a definite promotion move.
Except that in our current environments, _we_ are the meanest around.
What was your username again?
And exactly how many DSL users connect to that exchange, individually? How many people are running large full mesh, non routed networks?
You only need an instrument capable of switching to GSM when Wifi is not available.
a mless-wifi-to-gsm-voice-calls-017270.phpo nes/zyxel-dualmode-gsmwifi-phone.asp
:P
Something like this perhaps:
http://www.gizmodo.com/archives/motorola-cn620-se
http://www.voip-info.org/wiki-VOIP+Phones
http://blog.tmcnet.com/blog/tom-keating/mobile-ph
Enjoy
Except the Palestinians? Attacking Lebanon? Nah, you folks just didn't threaten nuclear holocaust.
You still didn't get the point. We handle half a billion messages a day (thats inbound only). We _know_ about stopping spam via protocol errors.
There are no such things as non business hours for us.
We are already stretched to the max with the current load of spam. If we start using greylisting, spammers have a huge incentive to fix their implementations (or start retrying -- they already do after 2 minutes, regrdless of the status of the previous run).