The biggest benefit of PostgreSQL 8.0.0 is that for the first time it will run natively on Microsoft Windows servers
Honk if you think being able to run on Winders is the most important feature in this, the best relational DB around. I tend to think that not being able to run on Winduhs is a feature. It prevents PHBs from getting silly ideas like "Windows is a viable platform."
I'd just like to say that it's about the best card you could want. Out of the three cards I tried, it was the only one that worked just by plugging it into my laptop (which runs Mandrake). It also consistantly picks up networks that others' cards can't. I imagine it works reasonably well under winduhs to, but I've never tried.
My only complaint is the lack of an external antenna jack. Still, I think M$, like many other vendors, switched to the non Linux-supported TI chipset. So nuts to them.
I ran a headless Windoze box for specific tasks first using VNC then Terminal Services. It works rather well and it's nice to have Winduhs in proper chains.
it's not the end of the world. I spent a long period looking for tech world while trying to keep things together with independent consulting work.
Last week I found myself being paid to fly (actually pilot the plane) across the state to deliver a machine and make a service call for my new employer. I've always wanted to fly and thanks to being laid off I'm being taught how and being paid in the process.
Take heart. The economy may be sucking, tech work being imported from India, but there's always options.
What does.NET offer to web applications that couldn't be achieved in a more portable way in PHP or another FOSS web language? I ask because I don't know.
I'd stay far away from MS dev tools because a) their IDEs try to keep the programmer as far away from what's actually going on as possible; and b) their "embrace and extend" approach gives me the shivers.
Yeah, but you've gotta pick heuristics at some point. It's a pretty safe assumption (for now) that the vast majority of e-mail addresses will be represented all lower-csae (just look around). The anti-spam noise is normally all-caps so that it's easy to spot.
> I can think of two big reasons. The first is that deobfuscation is > harder than it looks. It's not just a matter of applying the reveral > -- you also need to recognize which reversal to supply > (dubyaNOSPAMwhitehouseNONEgov, dubya at whitehouse dot gov, > dubyaFSCKSPAM@whitehouse.gov....)
My ten lines (8 actually) work against both those schemes by first replacing occurrences of " at " and " dot " with their respective punctuation, deleting all of the capitol letters (optionally with embeded numbers) and then look for proper addresses. While this script would miss tonnes of addresses it would still harvest millions which are posted using the current obscuration techniques.
I've had success with Wikis in organizing office proceedures, documentation, logs, etc. They take just a little more lernin' than a simple "post your message here" arrangement, but they reward you with the ability to create flexible and extensible structures quickly. I use TWiki because it has a flexible calendar plugin. There are several open-source Wiki's available.
Most modern Wiki software (TWiki included) has revision control so no matter what they do they can't break it. The hard part is getting the luddites to adopt it. If that gets tough you can set up a sensible structure yourself and use TWiki's comment plugin to make it easy on them.
I once implemented a web interface that used XML-RPC to communicate with a search engine back-end. Each request lived in a state machine on the server. When the server received a request it would start processing and if it took more than a few seconds it would return an object with a status report and a request ID. The client would send a browser meta-refresh that would check on the status of the request every few seconds until it was done or returned an error.
If you're looking for something closer to real-time (a way for the server to initiate contact with the client) check out the BEEP protocol.
From the BEEP web page:
BEEP is a turbocharger for Internet applications that offers advanced features such as:
a standard application layer that supports dynamic, pluggable application "profiles" (protocols)
peer-to-peer, client-server, or server-to-server capabilities
multiple channels over a single authenticated session
support for arbitrary MIME payloads, including XML
I used to be involved in this stuff. Here are a few useful links.
The Environmental Working Group These are some seriously dedicated guys who do environmental research and advocacy. They also maintain several interesting projects, including:
The Chemical Industry Archives - I used to work with these documents. They're a massive collection of the chemical industry's own documents which describe how little they care about you.
The link seems to be broken so here's another one. I haven't found one with a decent screenshot.
I remember this game. It was about running all over a post-apocolyptic city, picking up and dropping off fares with a time limit, mowing down other pedestrians, jumping the taxi over things, and purchasing weapons.
I can. I clearly remember mediating a transaction using a communications medium WELL BEFORE this patent was filed. I purchased a plastic soldier with a parachute attached to it's head at a Toys-R-Us. I mediated the transaction using a communications medium known to the technically minded as "English." It's a shame I didn't retain the documentation. Guess I'll have to let AT&T keep the patent.
Check out Pebble Linux which has mesh support as well as secure login. It is developed by the NYC wireless guys and was featured in the Linux Journal (Sep. 2003 Issue).
Don't forget about passphrases. It's a know-something/have-something system. I can't speak for kernel contributers but my cert/key passphrases are generally made up of random letters and punctuation.
The whole process of understanding and creating GPG/SSL certs [hopefully] induces one to put some thought into their passphrase.
I should also hope that those kernel gurus are bright enough to pick decent passphrases between bouts of floating meditation.
An interesting idea but I think it's unlikely because it's not like selling stock. You can get on and sell a palette of misc. goods you bought (or whatever) over a period of time, thus building a good rep.
In kernel development there's nobody sitting around with a pile of good code they submit every Wednesday at half past four. Code contributions come from people who a) have an itch; and b) know how to scratch. There's also the fact that in order to be accepted by the powers that be, their itch has to be common and their scratching has to be of sufficient quality.
I also imagine even Linus and Alan's patches are seen by several people, if not before, then soon after, commission.
Look. If this means I can't have any more of Homer's patented, space-age, out-of-this-world Moon Waffles (a bag of caramels, waffle batter and liquid smoke cooked on a waffle iron and then wrapped around a stick of butter), then I'm not interested.
Slashdot Mirror
As with anything related to toxicology, the dose is the poison.
The biggest benefit of PostgreSQL 8.0.0 is that for the first time it will run natively on Microsoft Windows servers
Honk if you think being able to run on Winders is the most important feature in this, the best relational DB around. I tend to think that not being able to run on Winduhs is a feature. It prevents PHBs from getting silly ideas like "Windows is a viable platform."
I covered this story some time ago.
I'd just like to say that it's about the best card you could want. Out of the three cards I tried, it was the only one that worked just by plugging it into my laptop (which runs Mandrake). It also consistantly picks up networks that others' cards can't. I imagine it works reasonably well under winduhs to, but I've never tried.
My only complaint is the lack of an external antenna jack. Still, I think M$, like many other vendors, switched to the non Linux-supported TI chipset. So nuts to them.
I ran a headless Windoze box for specific tasks first using VNC then Terminal Services. It works rather well and it's nice to have Winduhs in proper chains.
it's not the end of the world. I spent a long period looking for tech world while trying to keep things together with independent consulting work.
Last week I found myself being paid to fly (actually pilot the plane) across the state to deliver a machine and make a service call for my new employer. I've always wanted to fly and thanks to being laid off I'm being taught how and being paid in the process.
Take heart. The economy may be sucking, tech work being imported from India, but there's always options.
What does .NET offer to web applications that couldn't be achieved in a more portable way in PHP or another FOSS web language? I ask because I don't know.
I'd stay far away from MS dev tools because a) their IDEs try to keep the programmer as far away from what's actually going on as possible; and b) their "embrace and extend" approach gives me the shivers.
...welcome our big blue overlords!
Yeah, I figure they'd be a bit smarter about it but I didn't want to take the time. They could probably get rid of it all together.
Yeah, but you've gotta pick heuristics at some point. It's a pretty safe assumption (for now) that the vast majority of e-mail addresses will be represented all lower-csae (just look around). The anti-spam noise is normally all-caps so that it's easy to spot.
It would be a good consipracy theory if I hadn't been the one to post both the story _and_ the code. Check the by-line. :)
> I can think of two big reasons. The first is that deobfuscation is
/usr/bin/perl /\@/ig; /\./ig;
> harder than it looks. It's not just a matter of applying the reveral
> -- you also need to recognize which reversal to supply
> (dubyaNOSPAMwhitehouseNONEgov, dubya at whitehouse dot gov,
> dubyaFSCKSPAM@whitehouse.gov....)
My ten lines (8 actually) work against both those schemes by first replacing occurrences of " at " and " dot " with their respective punctuation, deleting all of the capitol letters (optionally with embeded numbers) and then look for proper addresses. While this script would miss tonnes of addresses it would still harvest millions which are posted using the current obscuration techniques.
#!
while() {
s/ at
s/ dot
s/[A-Z]+[0-9]*[A-Z]*//g;
while(/([a-z0-9]+\@[a-z0-9.]+\.(com|org|net))/gi) { print("$1\n"); }
}
Here it is in nine:
A real Perl hacker could probly do it in three, in the shape of a camel.
Most modern Wiki software (TWiki included) has revision control so no matter what they do they can't break it. The hard part is getting the luddites to adopt it. If that gets tough you can set up a sensible structure yourself and use TWiki's comment plugin to make it easy on them.
If you're looking for something closer to real-time (a way for the server to initiate contact with the client) check out the BEEP protocol.
From the BEEP web page:
BEEP is a turbocharger for Internet applications that offers advanced features such as:
It's easily capable of representing objects, platform independent, encryptable (via SSL), compressable (via gzip [and probably SSL as well]), and textual.
The advantages of being textual in your protocols is well laid out in Eric Raymond's book The Art of Unix Programming. He even treats it as a case study.
The Environmental Working Group
These are some seriously dedicated guys who do environmental research and advocacy. They also maintain several interesting projects, including:
Bill Moyers - Trade Secrets
Bill Moyers did a great film about the problem.
A Google Search For Philip Landrigan
Dr. Philip Landrigan has done extensive work on body burdens in children and has written a number of books.
...hiding your secrets in an image? Just write them in Perl!
I remember this game. It was about running all over a post-apocolyptic city, picking up and dropping off fares with a time limit, mowing down other pedestrians, jumping the taxi over things, and purchasing weapons.
I can. I clearly remember mediating a transaction using a communications medium WELL BEFORE this patent was filed. I purchased a plastic soldier with a parachute attached to it's head at a Toys-R-Us. I mediated the transaction using a communications medium known to the technically minded as "English." It's a shame I didn't retain the documentation. Guess I'll have to let AT&T keep the patent.
Check out Pebble Linux which has mesh support as well as secure login. It is developed by the NYC wireless guys and was featured in the Linux Journal (Sep. 2003 Issue).
Don't forget about passphrases. It's a know-something/have-something system. I can't speak for kernel contributers but my cert/key passphrases are generally made up of random letters and punctuation.
The whole process of understanding and creating GPG/SSL certs [hopefully] induces one to put some thought into their passphrase.
I should also hope that those kernel gurus are bright enough to pick decent passphrases between bouts of floating meditation.
An interesting idea but I think it's unlikely because it's not like selling stock. You can get on and sell a palette of misc. goods you bought (or whatever) over a period of time, thus building a good rep.
In kernel development there's nobody sitting around with a pile of good code they submit every Wednesday at half past four. Code contributions come from people who a) have an itch; and b) know how to scratch. There's also the fact that in order to be accepted by the powers that be, their itch has to be common and their scratching has to be of sufficient quality.
I also imagine even Linus and Alan's patches are seen by several people, if not before, then soon after, commission.
Look. If this means I can't have any more of Homer's patented, space-age, out-of-this-world Moon Waffles (a bag of caramels, waffle batter and liquid smoke cooked on a waffle iron and then wrapped around a stick of butter), then I'm not interested.
I intend to file for a business practice patent covering filing fraudulent method patents as a revenue source. Who's with me?