In Santa Rosa, just north of San Francisco, we have wide area 802.11 from a company called BroadLink. They partner with ISP's, just providing the ~1Mbit wireless connection.
It isn't mobile like Ricochet, no checking email on BART or a bus, but for the DSL and Cable less I think it's a good replacement. Service is great, though at $200 its a little pricey to setup when compared to Earthlink's DSL setup charges.
You should never have to think about what
way to do something, there should always be one, and only one, obvious way. Offering multiple ways of doing
the same thing makes the user think about the interface instead of the actual work that should be done. At the
very least this slows down the process of making the interface habitual.
I wholeheartedly disagree. I like to have multiple ways to do things. I try them all and figure out the one that suits me best, then make it a habit.
Someone else's idea of "the most natural way to do x" often times isn't mine. I guess that's why I always set custom keys in games, use emacs, and think PERL is fun to hack around with.
If we should tax internet (catalog and phone orders too) and how we should tax the internet are two distinct questions.
Ignoring if, why are so many people arguing that the HOW of it is impossible. We shouldn't have to worry about the 7000 different tax jurisdictions; collect sales tax according to the retailers jurisdiction.
ie I'm in CA I buy RAM from a company in NJ. I pay NJ's x% sales tax and the great state of NJ gets its revenue.
'Main St.' companies are happy - online retailers don't have an unfair tax advantage.
States and local municipalities are happy - they get money
I don't really care, I'd get taxed if I bought it localy
Why would it need to get more complicated than that?
This guy spent a couple of kilobytes using valuation judgments to justify the failure to put adequate security in his network specification.
Who defines adequate? WEP is adequate for me most of the time. I'm not worried about someone hiding in the bushes trying to hijack my plaintext/. password. You want it, take it, for that much effort. When I access my bank account I'll do it over an SSL connection though, because in that case WEP isn't adequate.
Precisely because the 802.11 group doesn't know what kind of data will be sent over the air they leave the responsibility of real encryption to the user. Putting better security as part of the standard would make it more difficult (read more expensive) to implement. That means it would have less of a chance of catching on. Unfortunately it isn't usually the best technology that wins out, but the best price.
Already it's pretty damn expensive when you figure $299 for an access point, and $125 per station card.
I dunno, maybe some of the people that have black helicopters following them ought to form a company, join the 802.11 working group, submit an addendum, and make a high security 802.11 product.
I'd be curious to know if anybody reading this believes there's much difference between these two exhausted ideologies, or that the country will be substantially
altered if one rather than the other prevails.
In the current election: Missile Defense Systems
If GW gets the seat in the Oval Office we are gambling with a new arms race.
This is something that would affect us twenty years down the road even if politics as we now know it are dead.
I'd rate Object Pascal as my favorite language to write code in. Along with features already mentioned I like that it's clear to read, and compiles faster than C++. Wirth designed the original Pascal grammer so it would be easy to parse -> faster to compile (actually I think he mostly wanted it to be easier to write a compiler for).
Object Pascal, the language of Delphi/Kylix, isn't the pascal your High School teacher learned in 1978. Check out "Real Programmers Use Pascal" for a quick synopsis of what Object Pascal has to offer.
I'm glad to see that I'm not the only one who thinks this would not be the end of the world. I think this would be a great way to keep in touch with my Mom.
Beyond that there could be some real benefits to bringing the masses closer to computer technology and legitimizing email in the eyes of the law.
Sure there are potential privacy concerns, but if the black helicopters circle you that closely don't sign up for it.
I think USPS does a decent job geting my mail to me on time and privately - I'll wait to see how their implementation turns out before I decry it as the end of privacy.
I'm surprised no one else gots'ta seen dese filters elsewhere. Right On! Abo ut 4 years ago ah' saw de JIBE'd version uh de GPL and could't stop laughin'.
From some link off de same page ya' could git de source. What it is, Mama! Dough not 'esplicitly stated ah' always assumed it wuz public domain and free t'copy; I've neva' seen any dojigger, copyright, o' license in de source. What it is, M ama!
I used t'gots' some version uh it runnin' around, but kin't find it right now. As ah' recall it compiled fine unda' AIX and Solaris, but poo'ly unda' Red Hat and DOS (Bo'land CPB 4.0 afta' runnin' it dru de lex on AIX)
I dun did some quick search and found a link t'de same source ah' o'iginally had. So, if ya' plum wanna JIBE some little yo'self o' start an jimmey source version u h de serva' dat should be some baaaad start.
or for the jive impaired...
I'm surprised no one else has seen these filters elsewhere! About 4 years ago I saw the jive'd version of the GPL and could't stop laughing.
From a link off the same page you could get the source. Though not explicitly stated I always assumed it was public domain and free to copy; I've never seen any name, copyright, or license in the source.
I used to have a version of it running around, but can't find it right now. As I recall it compiled fine under AIX and Solaris, but poorly under Red Hat and DOS (Borland CPB 4.0 after running it thru the lex on AIX)
I did a quick search and found a link to the same source I originally had. So, if you just want to jive a little yourself or start an open source version of the server that should be a good start.
The irony in the FSF owning copyrights has always left a funny taste in my mouth and I am inclined to agree with catseye_95051's comment.
I wanted a more precise definition of Public Domain, and the part that grabbed me was "Public domain means no copyright -- no exclusive rights."
Why should we give exclusive rights to a singular organization when the real idea is to share it with everyone?
I don't think giving the FSF copyrights is the only way that they can protect free software. I think I'd like to see them as a watchdog for public domain software
Slashdot Mirror
It isn't mobile like Ricochet, no checking email on BART or a bus, but for the DSL and Cable less I think it's a good replacement. Service is great, though at $200 its a little pricey to setup when compared to Earthlink's DSL setup charges.
I wholeheartedly disagree. I like to have multiple ways to do things. I try them all and figure out the one that suits me best, then make it a habit.
Someone else's idea of "the most natural way to do x" often times isn't mine. I guess that's why I always set custom keys in games, use emacs, and think PERL is fun to hack around with.
Ignoring if, why are so many people arguing that the HOW of it is impossible. We shouldn't have to worry about the 7000 different tax jurisdictions; collect sales tax according to the retailers jurisdiction.
ie I'm in CA I buy RAM from a company in NJ. I pay NJ's x% sales tax and the great state of NJ gets its revenue.
'Main St.' companies are happy - online retailers don't have an unfair tax advantage.
States and local municipalities are happy - they get money
I don't really care, I'd get taxed if I bought it localy
Why would it need to get more complicated than that?
Other likely job categories for a computer engineer:
Who defines adequate? WEP is adequate for me most of the time. I'm not worried about someone hiding in the bushes trying to hijack my plaintext /. password. You want it, take it, for that much effort. When I access my bank account I'll do it over an SSL connection though, because in that case WEP isn't adequate.
Precisely because the 802.11 group doesn't know what kind of data will be sent over the air they leave the responsibility of real encryption to the user. Putting better security as part of the standard would make it more difficult (read more expensive) to implement. That means it would have less of a chance of catching on. Unfortunately it isn't usually the best technology that wins out, but the best price.
Already it's pretty damn expensive when you figure $299 for an access point, and $125 per station card.
I dunno, maybe some of the people that have black helicopters following them ought to form a company, join the 802.11 working group, submit an addendum, and make a high security 802.11 product.
- RiBread
In the current election:
Missile Defense Systems
If GW gets the seat in the Oval Office we are gambling with a new arms race.
This is something that would affect us twenty years down the road even if politics as we now know it are dead.
I'd rate Object Pascal as my favorite language to write code in. Along with features already mentioned I like that it's clear to read, and compiles faster than C++. Wirth designed the original Pascal grammer so it would be easy to parse -> faster to compile (actually I think he mostly wanted it to be easier to write a compiler for).
Object Pascal, the language of Delphi/Kylix, isn't the pascal your High School teacher learned in 1978. Check out "Real Programmers Use Pascal" for a quick synopsis of what Object Pascal has to offer.
Beyond that there could be some real benefits to bringing the masses closer to computer technology and legitimizing email in the eyes of the law.
Sure there are potential privacy concerns, but if the black helicopters circle you that closely don't sign up for it.
I think USPS does a decent job geting my mail to me on time and privately - I'll wait to see how their implementation turns out before I decry it as the end of privacy.
From some link off de same page ya' could git de source. What it is, Mama! Dough not 'esplicitly stated ah' always assumed it wuz public domain and free t'copy; I've neva' seen any dojigger, copyright, o' license in de source. What it is, M ama!
I used t'gots' some version uh it runnin' around, but kin't find it right now. As ah' recall it compiled fine unda' AIX and Solaris, but poo'ly unda' Red Hat and DOS (Bo'land CPB 4.0 afta' runnin' it dru de lex on AIX)
I dun did some quick search and found a link t'de same source ah' o'iginally had. So, if ya' plum wanna JIBE some little yo'self o' start an jimmey source version u h de serva' dat should be some baaaad start.
or for the jive impaired ...
I'm surprised no one else has seen these filters elsewhere! About 4 years ago I saw the jive'd version of the GPL and could't stop laughing.
From a link off the same page you could get the source. Though not explicitly stated I always assumed it was public domain and free to copy; I've never seen any name, copyright, or license in the source.
I used to have a version of it running around, but can't find it right now. As I recall it compiled fine under AIX and Solaris, but poorly under Red Hat and DOS (Borland CPB 4.0 after running it thru the lex on AIX)
I did a quick search and found a link to the same source I originally had. So, if you just want to jive a little yourself or start an open source version of the server that should be a good start.
I wanted a more precise definition of Public Domain, and the part that grabbed me was "Public domain means no copyright -- no exclusive rights."
Why should we give exclusive rights to a singular organization when the real idea is to share it with everyone?
I don't think giving the FSF copyrights is the only way that they can protect free software. I think I'd like to see them as a watchdog for public domain software