True, but with the average age of parents increasing year after year -- translating into more disposable income on average -- Kids have more and more spending power available on average each year.
Well sure, but once you've got enough tunnels poked for everything you need in a moderately sized organization, you may as well have installed a VPN in the first place. I agree with you that most small orgs don't really need VPNs, especially if they just need one service. However, as the number of internal services you need to access remotely increases, a VPN begins to make more and more sense.
It makes less sense if you replicate browse traffic over the VPN from 1000 workstations. hehehehe -l
Indeed, the point here is that "everything having a routable address" != "everything is insecure". By default, IPv6 DSL/Cable routers won't let traffic inbound unless the user specifies, but you gain the benefits of having a routable address, such as VPN being plug-n-play instead of plug-n-configure-a-bunch-of-annoying-crap.
People tend to confuse the firewalling features of routers with NAT. -l
Well... it hasn't decreased, though there was a cool study published in Nature a couple years ago that concluded that the world population will probably top out at about 10 billion depending on various factors. This is due to the "adverse" effects of affluence on population growth. Africa is an enormous factor. How Earth's population grows depends a great deal on how African war, poverty, and AIDS turn out.
People who use P2P need full-cone NAT, but assuming an average of 128 connections per user at peak times, you can fit about 500 users behind a single address even with full-cone NAT.
Just don't try to set them up on 500 different VPN clients!:) That's where admins will be happier with IPv6.
-l
I saw Wal-mart: The High Cost of Low Prices this weekend. It was pretty good. I wouldn't call it a documentary. It was more of an investigative journalism piece, like 60 Minutes likes to do, but without all the narration. It also encourages basic activism.
Stuff I learned from the movie:
Wal-mart intentionally does not hire enough workers for its needs.
Wal-mart coerces employees into working off the clock.
Wal-mart managers regularly alter timesheets to remove overtime pay.
One of the largest and most profitable companies in the world lacks affordable health insurance for its workers. Instead, managers keep lists of local, state, and federal services like Medicaid, WIC, etc. for employees to take advantage of.
Wal-mart enjoys tens of millions of dollars of direct tax subsidies from state and local entities.
Wal-mart bought a couple chains in Germany which were already unionized. Their workers enjoy reasonable benefits.
In one town, Wal-mart was given tax subsidies to build there. Shortly before the subsidy ran out, Wal-mart closed that store and moved a couple miles out of town.
Wal-mart has left many tens of millions of square feet of empty buildings across the United States.
The Waltons are selfish pricks who donate very little to charity. Even Bill Gates donates 58% of his income to charity.
Wal-mart parking lots are subject to unreasonable amounts of crime due to their lacking basic safety precautions.
Wal-mart is, at best, largely ignorant of environmental regulations and has been subject to a number of large fines.
Criticisms:
Not enough evidence is presented in the film to support the claim of systemic racial and gender discrimination.
The credits of towns and cities that successfully rejected Wal-mart repeats the names of the towns and cities which gives the impression of there being more of them than there are.
One wonders if large parking lot security is lax in general and in need of regulation to protect patrons.
You're making the database do the work of looking up the list of columns names every time that query runs.
Are you sure about that? Because when you spell them out, the database still has to verify you haven't asked for something it doesn't have. Obviously it needs the names in a SELECT *, but it doesn't need to error check them. Also, with databases that keep track of the version number of the table, I doubt they bother flushing the cache on "SELECT *" unless the schema changes. I mean, what would be the point since it knows if it's changed in advance?
I don't really know as I've never written a database or gone into optimization that far, so I'm asking you to elaborate for me, if you don't mind.
I agree with the 100 cols thing, although once you have that crap in there and you have users who are used to that model of thinking in writing their own reports, it's hard to get people to think otherwise. E.g., recently I had a bitch of a time convincing another employee that they should just use the stored proc I wrote directly rather than having us run the damn thing in a cron job every night to populate a column. But that's just one battle I won.
It's a crazy world out there and sometimes you just have to bite the bullet and add that 101st col while holding your nose!
-l
Ditto. I mean, what was the point? I remember posting being one of the reasons why I got one. Something like not wanting to be AC or something. Been awhile.
Searching the waybackmachine presently... Unfortunately, it yields "Path Index Error" and "Failed Connection" for the two oldest caches.
I think back then I was still posting with info inline if at all.
This is just my experience -- take from it what you will. I took a couple CS classes in college, but my jobs were always LAN Administrator type jobs. At one company, they needed someone to maintain a simple script on the servers. I did that. I hated the way it worked, so I made it better. And better. And even more better! (heh) After awhile, I decided I wanted to do programming instead of system administration and I've been happier since.
I thought the idea of Google Talk was Instant Messaging with cheesy Voice-over-Computer crap. I was thinking something more in line with Vonage or Packet8.
For the time being, I guess we can just do what I do below, which is equally semantic and has just as much available style markup available through judicious use of the span tag.
-l
So... we just need a new quantum encryption algorithm called "anti-Shor". Problem solved! :)
-l
Well, it did beat out decimeterball...
-l
Agreed. It's better to find a nice, small niche and make some money there, though you can still own your own company doing that.
-l
No shit!
-l
I always knew Darth Maul was the wise one!
Next year, I'm voting Palpatine!
-l
Save the Hubble or bite me. That's all I have to say about that.
-l
True, but with the average age of parents increasing year after year -- translating into more disposable income on average -- Kids have more and more spending power available on average each year.
-l
Well sure, but once you've got enough tunnels poked for everything you need in a moderately sized organization, you may as well have installed a VPN in the first place. I agree with you that most small orgs don't really need VPNs, especially if they just need one service. However, as the number of internal services you need to access remotely increases, a VPN begins to make more and more sense.
It makes less sense if you replicate browse traffic over the VPN from 1000 workstations. hehehehe
-l
Indeed, the point here is that "everything having a routable address" != "everything is insecure". By default, IPv6 DSL/Cable routers won't let traffic inbound unless the user specifies, but you gain the benefits of having a routable address, such as VPN being plug-n-play instead of plug-n-configure-a-bunch-of-annoying-crap.
People tend to confuse the firewalling features of routers with NAT.
-l
Well... it hasn't decreased, though there was a cool study published in Nature a couple years ago that concluded that the world population will probably top out at about 10 billion depending on various factors. This is due to the "adverse" effects of affluence on population growth. Africa is an enormous factor. How Earth's population grows depends a great deal on how African war, poverty, and AIDS turn out.
-l
Just don't try to set them up on 500 different VPN clients! :) That's where admins will be happier with IPv6.
-l
Of course, the FORWARD rule will be followed with DENY ALL BUT INTERNALLY-INITIATED CONNECTIONS without explicit user override.
Cheers,
-l
I saw Wal-mart: The High Cost of Low Prices this weekend. It was pretty good. I wouldn't call it a documentary. It was more of an investigative journalism piece, like 60 Minutes likes to do, but without all the narration. It also encourages basic activism.
Stuff I learned from the movie:
Criticisms:
-l
Are you sure about that? Because when you spell them out, the database still has to verify you haven't asked for something it doesn't have. Obviously it needs the names in a SELECT *, but it doesn't need to error check them. Also, with databases that keep track of the version number of the table, I doubt they bother flushing the cache on "SELECT *" unless the schema changes. I mean, what would be the point since it knows if it's changed in advance?
I don't really know as I've never written a database or gone into optimization that far, so I'm asking you to elaborate for me, if you don't mind.
I agree with the 100 cols thing, although once you have that crap in there and you have users who are used to that model of thinking in writing their own reports, it's hard to get people to think otherwise. E.g., recently I had a bitch of a time convincing another employee that they should just use the stored proc I wrote directly rather than having us run the damn thing in a cron job every night to populate a column. But that's just one battle I won.
It's a crazy world out there and sometimes you just have to bite the bullet and add that 101st col while holding your nose!
-l
I remember playing Super Mario at Walmart when it first came out. Cool.
-l
Ditto. I mean, what was the point? I remember posting being one of the reasons why I got one. Something like not wanting to be AC or something. Been awhile.
Searching the waybackmachine presently... Unfortunately, it yields "Path Index Error" and "Failed Connection" for the two oldest caches.
I think back then I was still posting with info inline if at all.
-l
This is just my experience -- take from it what you will. I took a couple CS classes in college, but my jobs were always LAN Administrator type jobs. At one company, they needed someone to maintain a simple script on the servers. I did that. I hated the way it worked, so I made it better. And better. And even more better! (heh) After awhile, I decided I wanted to do programming instead of system administration and I've been happier since.
Above all, have fun with it,
-l
/me all about the one-liners and silliness
-l
Not to mention the Douglas Adams episodes...
-l
Point taken. Thanks.
-l
OK, I have a crazy idea. I am NOT a net admin and am largely blue skying here.
Damage: Level3 won't accept Cogent traffic.
Horrible hack: tunnel BGP traffic to Level3 customer who masquerades requests as local traffic.
Yeah, the real solution is tier 2 folks having more peerings, but as a nasty workaround is that hack feasible?
Can you tunnel BGP traffic in TCP or ssh or something?
-l
I thought the idea of Google Talk was Instant Messaging with cheesy Voice-over-Computer crap. I was thinking something more in line with Vonage or Packet8.
-l
For the time being, I guess we can just do what I do below, which is equally semantic and has just as much available style markup available through judicious use of the span tag.
10.
9.
8.
7.
.
.
.
1.
-l
Hell, I'd be happy with Google VOIP.
-l