If the Republicans could successfully mount a concerted filibuster, you might have a point. The moderate Republicans might as well be Democrats for the purposes of trying to filibuster something.
Again: If the Democrats could get their moderates onto the party bus, the Republicans wouldn’t stand a chance at stopping anything the Democrats wanted to roll through. Yeah, if the Republicans could get their own moderates to toe the line, they might stand a chance at opposing it... but we all know that hasn’t happened, so quit pretending it’s all the Republicans’ fault.
"Close Guantanomo within a year? Umm, no" He tried, the Republicans shut him down.
Anybody who claims that the President/Senate/House “tried” to do something but the Republicans “shut them down” is being downright dishonest.
With their huge majorities in both houses of Congress, the Democrats can do anything they damn well please if only they could get all their fellow Democrats onto the party bus. The moderate Democrats are the ones who shot it down.
A Faraday cage does not need to be grounded in order to block out RF. The reason for grounding is entirely unrelated: it is a large conductor and it poses an electrocution hazard if a hot conductor should happen to short to it.
Oh, and by the way... your plumbing system, if it is metal, is probably already grounded. However, attaching it to the pluming is not considered safe as a means of grounding something.
You are correct about apertures in the surface but these would be fairly directional and relatively small. If a window does not shield against RF, your cell phone might work if you are standing right in front of the window, but the signal strength will probably be pretty negligible a few steps away.
The fix is expected to address a issue in iOS 4 related to radio frequency calibration of the baseband. Readers who saw the original forum discussions say that the issue is believed to occur when switching frequencies; because the lag is allegedly not calibrated correctly, it results in the device reporting "no service" rather than switching to the frequency with the best signal to noise ratio.
iOS 4 introduced some enhancements to how the baseband selects which frequencies to use, so it makes sense that the error may have crept into those changes. Additionally, this explains why iOS 4 has also caused similar problems for iPhone 3GS users.
I seriously thought this thread had died out by now. Just came back and it seems that it’s going quite nicely without me. Those last two pictures were not posted by me, by the way, so keep shadow-boxing with Anonymous Cowards if that’s what floats your boat. I’m sure if you sent a nice DMCA notice to Slashdot they’d give you the IP address of your new target.
You’re kidding, right? What you’re calling the “minimum should-be-readable size” would only be readable with a magnifying glass... that’s something like a 45 characters per inch, 2-point font.
The tl;dr version, if my memory serves me accurately:
The panes of glass which are thicker at one side are the side effect of the imprecise glass manufacturing skill of that time. The panes were usually installed thickest-side-down because that is the most sensible from an engineering point of view: center of mass as low as possible for the most stability. However, some examples have been found of glass that was installed upside-down (thickest side at the top, either by accident or by chance), refuting the notion that the thickness at the bottom is caused by the glass deforming slightly over time.
You could probably verify all that by looking online for an article that doesn’t require subscription to access but I’m to lazy to bother right now...
Just deposited a $5000.00 in cash at 9:00am if I write a check at 3:00pm the check will bounce. because they process debits before payments as a lump at 12:01am the next morning.
How on earth? If it’s being electronically debited sure, but for a normal paper check even if it was deposited before banks close today it’d still have to go through the clearing house. Unless maybe they deposited it at the same bank it was written from (your bank) and they did everything in-house, but that’s a stretch.
The cached JS file would, of course, be run as if it was from the requested domain, not the domain it was originally downloaded from (that would likely screw up badly by triggering all sorts of cross-domain scripting protections... you’d get a bunch of JS errors and the thing wouldn’t run). As the two JS files themselves are bytewise identical, I see no possibility of XSS attacks.
It's people using AdBlock that cause sites to have annoying adverts in the first place.
That is simply false. In fact, reality is exactly the opposite: It’s the sites having annoying adverts that cause people to use AdBlock in the first place.
Annoying advertisements (particularly annoying, the blinking animated gif ones) have been around at least since when I was first starting to surf the web back in the days of Netscape Navigator 2. AdBlock was pretty much unheard of back then, which meant I had no choice but to look at Flash ads for fungal foot cremes on my Hotmail account.
Any request that takes longer than 2 seconds will be uncomfortable to the user.
The opening comment here sez pages are closer to 5 seconds now, which means the web is a lose.
Not necessarily. Enough content should be rendered nearly immediately that the user is not discomforted by the wait, even though parts of the page are still loading. Now, granted that whether or not the page is responsive at that time is another question... if part of the page has rendered but it wasn’t the part I need, and the page won’t scroll for ~5 seconds as it loads, then yes, that is inconvenient.
Republicans are a singular block?
That must be why they were able to successfully keep Obamacare from passing. Etc. etc. etc.
You mean like their filibuster of the health care reform bill? Or the jobs bill? Or the appointment of Patricia Smith?
If the Republicans could successfully mount a concerted filibuster, you might have a point. The moderate Republicans might as well be Democrats for the purposes of trying to filibuster something.
Again: If the Democrats could get their moderates onto the party bus, the Republicans wouldn’t stand a chance at stopping anything the Democrats wanted to roll through. Yeah, if the Republicans could get their own moderates to toe the line, they might stand a chance at opposing it... but we all know that hasn’t happened, so quit pretending it’s all the Republicans’ fault.
"Close Guantanomo within a year? Umm, no"
He tried, the Republicans shut him down.
Anybody who claims that the President/Senate/House “tried” to do something but the Republicans “shut them down” is being downright dishonest.
With their huge majorities in both houses of Congress, the Democrats can do anything they damn well please if only they could get all their fellow Democrats onto the party bus. The moderate Democrats are the ones who shot it down.
Try changing the router to channel 1.
A Faraday cage does not need to be grounded in order to block out RF. The reason for grounding is entirely unrelated: it is a large conductor and it poses an electrocution hazard if a hot conductor should happen to short to it.
Oh, and by the way... your plumbing system, if it is metal, is probably already grounded. However, attaching it to the pluming is not considered safe as a means of grounding something.
You are correct about apertures in the surface but these would be fairly directional and relatively small. If a window does not shield against RF, your cell phone might work if you are standing right in front of the window, but the signal strength will probably be pretty negligible a few steps away.
My parents had a wireless phone that killed the wifi every time it rang.
I changed the wifi channel. Problem solved.
The fix is expected to address a issue in iOS 4 related to radio frequency calibration of the baseband. Readers who saw the original forum discussions say that the issue is believed to occur when switching frequencies; because the lag is allegedly not calibrated correctly, it results in the device reporting "no service" rather than switching to the frequency with the best signal to noise ratio.
iOS 4 introduced some enhancements to how the baseband selects which frequencies to use, so it makes sense that the error may have crept into those changes. Additionally, this explains why iOS 4 has also caused similar problems for iPhone 3GS users.
Death threats?
I seriously thought this thread had died out by now. Just came back and it seems that it’s going quite nicely without me. Those last two pictures were not posted by me, by the way, so keep shadow-boxing with Anonymous Cowards if that’s what floats your boat. I’m sure if you sent a nice DMCA notice to Slashdot they’d give you the IP address of your new target.
Some days I’m funny, some days I’m not. Oh well.
6, 9, 16, 19, and 21 are indistinguishable in written Arabic? No wonder they invented numerals...
2 + 2 = 1
That wasn’t his opinion, it was merely an illustration of his opinion that people should be allowed to say that if they want to.
Real-life neuralizer... (ok, more like blinding people)
Your 300dpi color inkjet (or laserjet) doesn’t print halftoned images, and that’s what GP was talking about.
78 um and 102 um. They used the Greek letter Mu, which Slashdot helpfully strips out.
You’re kidding, right? What you’re calling the “minimum should-be-readable size” would only be readable with a magnifying glass... that’s something like a 45 characters per inch, 2-point font.
The tl;dr version, if my memory serves me accurately:
The panes of glass which are thicker at one side are the side effect of the imprecise glass manufacturing skill of that time. The panes were usually installed thickest-side-down because that is the most sensible from an engineering point of view: center of mass as low as possible for the most stability. However, some examples have been found of glass that was installed upside-down (thickest side at the top, either by accident or by chance), refuting the notion that the thickness at the bottom is caused by the glass deforming slightly over time.
You could probably verify all that by looking online for an article that doesn’t require subscription to access but I’m to lazy to bother right now...
You can avoid all of these with the right tricks
EasyList for Adblock Plus must know some of those tricks, then, because I haven’t noticed those.
Whoops, yeah, slipped my mind when posting. 1 byte per second = 8 baud (bits per second).
You pay: Monthly for a cellular package with unlimited texting
You get: 20 baud
Just deposited a $5000.00 in cash at 9:00am if I write a check at 3:00pm the check will bounce. because they process debits before payments as a lump at 12:01am the next morning.
How on earth? If it’s being electronically debited sure, but for a normal paper check even if it was deposited before banks close today it’d still have to go through the clearing house. Unless maybe they deposited it at the same bank it was written from (your bank) and they did everything in-house, but that’s a stretch.
The cached JS file would, of course, be run as if it was from the requested domain, not the domain it was originally downloaded from (that would likely screw up badly by triggering all sorts of cross-domain scripting protections... you’d get a bunch of JS errors and the thing wouldn’t run). As the two JS files themselves are bytewise identical, I see no possibility of XSS attacks.
It's people using AdBlock that cause sites to have annoying adverts in the first place.
That is simply false. In fact, reality is exactly the opposite: It’s the sites having annoying adverts that cause people to use AdBlock in the first place.
Annoying advertisements (particularly annoying, the blinking animated gif ones) have been around at least since when I was first starting to surf the web back in the days of Netscape Navigator 2. AdBlock was pretty much unheard of back then, which meant I had no choice but to look at Flash ads for fungal foot cremes on my Hotmail account.
Any request that takes longer than 2 seconds will be uncomfortable to the user.
The opening comment here sez pages are closer to 5 seconds now, which means the web is a lose.
Not necessarily. Enough content should be rendered nearly immediately that the user is not discomforted by the wait, even though parts of the page are still loading. Now, granted that whether or not the page is responsive at that time is another question... if part of the page has rendered but it wasn’t the part I need, and the page won’t scroll for ~5 seconds as it loads, then yes, that is inconvenient.