Or just random connection trouble due to not being able to pipeline the requests into a single connection (connection: keepalive), or just a random disconnect in general? I'm sure people have seen a "site without its css" thanks to a disconnect before, this is no different I'd think.
Also, why didn't they use a subdomain? desc.ebay.com?
Technically, latency is for a packet size, it's not an absolute, because it's to the end of the packet, not the start. It's normally measured with 32 bytes of payload, and in that case the cable line massively beats the pidgeon. But with a 4GB payload, the pidgeon wins easily. The pidgeon takes 1 hour, and then you get the entire packet. The cable network breaks your 4GB into 1kB packets (possibly) and transmits those with a 200ms latency (possibly) at 256kbps (possibly). You get some data in 200ms, but it's useless to you until you finish receiving the entire packet 50 hours later. In other words, for 4GB packets, the pidgeon is much better latency.
Technically a DoS would be anything which denies service, including a shotgun. You could even do a DDoS by putting out a bouny on pidgeons and getting a lot of people with shotguns to join in:)
Incidentally if anyone knows how to set a linux machine with a dynamic public IP up as an IPv6 tunnel (6to4 presumably) for my LAN, that would be awesome to know.
Unlimited = Use the internet 24/7. Always on. Example - Cable, DSL, FIOS.
Limited = Pay per Min. Example - AOL Dial-up.
That was a redefinition. In the dial-up days you could get "unlimited" dial-up, which was unlimited time* and data. *they usually cut you off every few hours, which made it really difficult to download over night.
On Slashdot, you are truly a god among men. Even though you didn't predict this future, to have witnessed the history between then and now is an honour many of us have not had.
How many of the rest of us wish we could have been where you have? To have watched the Internet unfold from the ARPANET into truly unimaginable thing it is today?
For like 25 centuries doctors have been swearing the Hippocratic oath, which explicitly states "do no harm."
Is not forcing someone to live in pain, with no dignity, not causing harm? Is it truly harm if the person is granted the relief they desire? Have you hurt anyone?
This reminded me instantly of Asimov's 3 Laws of Robotics. Specifically, the first: "A robot may not injure a human being or, through inaction, allow a human being to come to harm." A conflict between the two caused the robot to freeze, so unfortunately it is no help to us with resolving this...
They do say that Japan was about to surrender anyway, but that America could not have known that at the point the bombs were dropped. They did somewhat finish the whole thing though.
That is pretty fundamental to the design -- it's a SHA1 hash. It's also not incredibly difficult -- cut and paste. When your SVN revisions hit four and five digits, they don't really have much more meaning than that hash, do they?
Well, except that SVN revision numbers are in order. Could you tell at a glance which of two binaries with the git SHA1 hash in the filename was newer? What about with an svn revision number?
To me, it would make more sense if there was an incremental part to a git changelist id, even if it was "number of seconds since 2000" or something else unreadable, as long as you could ask someone "which revision crashed" and get back an answer you could easily use to tell if they were up-to-date or miles out of date.
or configuring everyone's different laptop to work with that specific model of router (a nightmare with WiFi).
First of all, I don't consider configuring WiFi a nightmare hell, and I work on IT, doing it frequently. It is one of the things that simply just work.
You should try this one: Connecting laptop to company wifi. You have the SSID and a WPA password. You attempt to connect to said network (it's advertising) and put in password. It says the password is wrong. You try a few more times to be sure. It still says it is wrong. You verify password with other laptops. It is correct. You try a few more times and eventually successfully connect, saving the connection details to auto-connect in future. The wireless status widget reports that your saved connection settings are incorrect for the connection, despite being the same ones you connected with and being working. You ignore it. A little later, after the laptop is restarted and needs to reconnect... It refuses, claiming the saved password is incorrect.... what's caused it, and how to fix it? Ask any additional questions you need to.
Note: we solved it. If it helps, that laptop still reports the settings are wrong, but will auto-connect with the saved settings fine.
Hell, last time I went to a private store, those idiots weren't even charging for their parking lot. I'm not surprised they're fucking this up.
The largest shopping centre in the European Uniondoesn't charge for parking. It has a total of 10,000 spaces, including three multi-story carparks. It also has it's own bus station, and train station.
That should tell people something about how to do parking right.
Use "Plain old text" posting mode in the options. It's not really plain text (that's extrans), it still allows html tags for formatting, but it does automatically add <br> tags for line breaks.
So, yeah, if W2K3-64 supports it XP-64 supports it, but not a lot of, say, bleeding edge video cards bother to support Server OS's because who the hell puts a 1GB graphics card in a server?
Strange, I could swear my bought-on-day-of-release nVidia GTX 285 works perfectly...
Not to mention the nVidia 8800GTS, and 2x nVidia 6600GT I used before that. (Yes even SLI works)....and nVidia 7800 GT, ATI X800 and ATI X1900XTX which I have tried at some point but didn't keep for whatever reason. (So ATI cards work too). One was a borrow when one of mine died, another was fault-finding on someone else's machine, and the last was a spare card someone had, but don't ask me which was which.
I have benchmark results for the LOT on "Windows Server 2003 (x64)" (according to 3dMark, but it's actually XP x64). So don't say that bleeding-edge graphics aren't supported on XP x64 because it only gets drivers from Server 2003 x64.
Slashdot Mirror
However, if the core gameplay is only "ok", playing with friends does improve it.
More accurately, it stops a decent game getting boring after playing it through once.
Or just random connection trouble due to not being able to pipeline the requests into a single connection (connection: keepalive), or just a random disconnect in general? I'm sure people have seen a "site without its css" thanks to a disconnect before, this is no different I'd think.
Also, why didn't they use a subdomain? desc.ebay.com?
Two negative feedbacks? That doesn't sound like much. I've bought from sellers with more negative feedback than that, like this person: http://feedback.ebay.co.uk/ws/eBayISAPI.dll?ViewFeedback2&userid=omar.m786&ftab=AllFeedback
Makes your story seem fishy.
HTTP in fact.
Give this guy the mod points, I've ran out, and he's right.
And nVidia instead of ATI
Technically, latency is for a packet size, it's not an absolute, because it's to the end of the packet, not the start. It's normally measured with 32 bytes of payload, and in that case the cable line massively beats the pidgeon. But with a 4GB payload, the pidgeon wins easily.
The pidgeon takes 1 hour, and then you get the entire packet.
The cable network breaks your 4GB into 1kB packets (possibly) and transmits those with a 200ms latency (possibly) at 256kbps (possibly). You get some data in 200ms, but it's useless to you until you finish receiving the entire packet 50 hours later.
In other words, for 4GB packets, the pidgeon is much better latency.
But that's picking holes.
Technically a DoS would be anything which denies service, including a shotgun. :)
You could even do a DDoS by putting out a bouny on pidgeons and getting a lot of people with shotguns to join in
http://www.dynamicarcade.co.uk/pictures/Matchbox_mini.jpg
That's my home router (I got sick of my real home router locking up on me, and wanted a mini-itx to tinker with). Built from a Jetway J7F2 Fanless 1.2GHz Eden C7 Mini-ITX Motherboard with Jetway 3x Gigabit LAN Motherboard Module, 512 MB of DDR2-667, and a 4GB compact flash card in a laptop-hdd-bay-mountable CF adapter, all in a Thin Client Fanless case. Running linux, with IPTables for NAT.
Something like that should be plenty powerful enough.
Incidentally if anyone knows how to set a linux machine with a dynamic public IP up as an IPv6 tunnel (6to4 presumably) for my LAN, that would be awesome to know.
I don't think it would automatically route any more, due to the crazy agreements between ISPs over who can and who can't transmit whose data.
Unlimited = Use the internet 24/7. Always on. Example - Cable, DSL, FIOS.
Limited = Pay per Min. Example - AOL Dial-up.
That was a redefinition. In the dial-up days you could get "unlimited" dial-up, which was unlimited time* and data.
*they usually cut you off every few hours, which made it really difficult to download over night.
On Slashdot, you are truly a god among men. Even though you didn't predict this future, to have witnessed the history between then and now is an honour many of us have not had.
How many of the rest of us wish we could have been where you have? To have watched the Internet unfold from the ARPANET into truly unimaginable thing it is today?
Is not forcing someone to live in pain, with no dignity, not causing harm? Is it truly harm if the person is granted the relief they desire? Have you hurt anyone?
This reminded me instantly of Asimov's 3 Laws of Robotics. Specifically, the first:
"A robot may not injure a human being or, through inaction, allow a human being to come to harm."
A conflict between the two caused the robot to freeze, so unfortunately it is no help to us with resolving this...
They do say that Japan was about to surrender anyway, but that America could not have known that at the point the bombs were dropped. They did somewhat finish the whole thing though.
I will admit to having checked my email over telnet, typing in pop3 protocol.
I have also done http (both as the client and server), ftp and xmpp (aka Jabber IM aka google talk).
A few of those required a telnet-like I wrote which accepts a connection instead of connecting to someone else.
That is pretty fundamental to the design -- it's a SHA1 hash. It's also not incredibly difficult -- cut and paste. When your SVN revisions hit four and five digits, they don't really have much more meaning than that hash, do they?
Well, except that SVN revision numbers are in order. Could you tell at a glance which of two binaries with the git SHA1 hash in the filename was newer? What about with an svn revision number?
To me, it would make more sense if there was an incremental part to a git changelist id, even if it was "number of seconds since 2000" or something else unreadable, as long as you could ask someone "which revision crashed" and get back an answer you could easily use to tell if they were up-to-date or miles out of date.
We're talking about the single-user case here.
You are going to get so many troll replies after that, despite being genuinely insightful.
"Trollbait"?
Neither ebay nor paypal have to set up a massive warehouse in Australia to successfully operate there...
or configuring everyone's different laptop to work with that specific model of router (a nightmare with WiFi).
First of all, I don't consider configuring WiFi a nightmare hell, and I work on IT, doing it frequently. It is one of the things that simply just work.
You should try this one: ... what's caused it, and how to fix it?
Connecting laptop to company wifi.
You have the SSID and a WPA password.
You attempt to connect to said network (it's advertising) and put in password.
It says the password is wrong. You try a few more times to be sure. It still says it is wrong.
You verify password with other laptops. It is correct.
You try a few more times and eventually successfully connect, saving the connection details to auto-connect in future.
The wireless status widget reports that your saved connection settings are incorrect for the connection, despite being the same ones you connected with and being working. You ignore it.
A little later, after the laptop is restarted and needs to reconnect...
It refuses, claiming the saved password is incorrect.
Ask any additional questions you need to.
Note: we solved it. If it helps, that laptop still reports the settings are wrong, but will auto-connect with the saved settings fine.
Hell, last time I went to a private store, those idiots weren't even charging for their parking lot. I'm not surprised they're fucking this up.
The largest shopping centre in the European Union doesn't charge for parking. It has a total of 10,000 spaces, including three multi-story carparks. It also has it's own bus station, and train station.
That should tell people something about how to do parking right.
Only xhtml has the "/" in the <br> tag
Use "Plain old text" posting mode in the options.
It's not really plain text (that's extrans), it still allows html tags for formatting, but it does automatically add <br> tags for line breaks.
What's with all the colour banding? Compression problems?
It was almost painful to watch because of it.
The rest wasn't bad for realtime.
So, yeah, if W2K3-64 supports it XP-64 supports it, but not a lot of, say, bleeding edge video cards bother to support Server OS's because who the hell puts a 1GB graphics card in a server?
Strange, I could swear my bought-on-day-of-release nVidia GTX 285 works perfectly...
Not to mention the nVidia 8800GTS, and 2x nVidia 6600GT I used before that. (Yes even SLI works). ...and nVidia 7800 GT, ATI X800 and ATI X1900XTX which I have tried at some point but didn't keep for whatever reason. (So ATI cards work too). One was a borrow when one of mine died, another was fault-finding on someone else's machine, and the last was a spare card someone had, but don't ask me which was which.
I have benchmark results for the LOT on "Windows Server 2003 (x64)" (according to 3dMark, but it's actually XP x64). So don't say that bleeding-edge graphics aren't supported on XP x64 because it only gets drivers from Server 2003 x64.