I read the two specific links. Both seem to say basically, "we messed up and exported a stupid API (documented or undocumented), and we're too stupid to just break things." I as a user (which is who should count more for Microsoft than developers) would rather find out when/before I upgrade to the latest/greatest Windows release that certain programs I have installed won't work because the developers were/are wankers and used unsupported/undocumented APIs. Especially since the alternative is the 'OS' becoming such a morass of insecure, poorly designed APIs that the whole thing is a house of cards.
All variants of "Make it computationally expensive to send e-mail!" prevent all mass mailings of all kinds... not just spam.
But SPAM is unique as a mass mail in that there is no pre-existing relationship between the correspondents. For mailing lists, with SPF subscribers can authenticate that the email actually came from the mailing list (sent from the domain at least, and the domain owner can control the envelope and From: with SMTP-AUTH).
The main problem with mailing lists is that since they do 'mulitply' mail, a spammer could subscribe, and send a SPAM as a subscriber which gets forwarded to all the subscribers (who would likely do limited SPAM filtering on mail from lists to which they were subscribed). On the other hand, lists can do extensive checks on mails coming into the list; require high-value hash-cash, challenge-response, or distributed moderation of messages with a high 'spamminess' based on filters.
SPF is incredibly broken because it allows ISPs to control who sends mail from where.
We should be resisting SPF and all other similar proposals and backing public keys in DNS.
Wrong. SPF allows Domain Owners to control who sends email claiming to be from the domain they own!
My ISP has nothing to do with my domains. As far as I am concerned, they are just a pipe. And yes, if you want to send email claiming to be a member/representitive of my domain, I want some control over it.
Really? A lot of election fund raising laws hinge on First Amendment protections. If I can raise money to take over the governement of the United States and install a whole new congress and president, why can't I raise money for other causes I believe in?
Note, I haven't investigated the charges, and the article is light on details, but the person being charged denies the raising of funds, and the article goes on to say:
Hussayen is accused of moderating an Arabic-language e-mail group that posted instructions on how to train at a terrorist camp and issued an "urgent appeal" to Muslims in the military last February to provide information for use in selecting terror targets.
So, if I moderate on Slashdot, and someone posts such an 'urgent appeal' does that make me liable? I suppose I'd moderate such a post as 'offtopic' anyway, but maybe it should be 'flamebate'? Does that make me a terrorist?
Also, another reply to this post compares this free speach to shouting 'fire' in a crowded theater. Huh? How is an website an 'automatic stimulus to panic'?
Way too many people are willing to broden the Government's powers and tighten the protections given by the constitiution. I think we've got a responsibility to ensure those protections are kept as broad as possible.
I really don't like the inflexibility of the drawer model. A drawer is nicely associated with it's window, but always takes up the screen space whether the window is 'key' or not. I much perfer the the 'panel' approach of NeXTStep. In NeXTStep, you'd have one or a few panels per application, they could hide (or not depending on implementation) when the application wasn't 'front'. The content of the panel would change to track the 'key' window. and the panel could be moved where ever you'd like on the workspace. Given a multi monitor setup, that flexibility can be very very useful.
For me and my wife at least, was the remake of "The Thin Red Line."
All the star cameos kept giving me hope that there'd be a single character I might grow to care about. I kept hoping that it would somehow redeem itself in the end.
But I was denied and it's still my worst movie ever!
Are you suggesting this in concert with SPF? If not, then spammers would just forge the mail as being from a valid address. What you describe sounds sort of like a challenge-response system (http://tmda.net), but more automated. The trouble with that is the same trouble with VRFY. That is, it can be used to determine whether an address is valid or not for future spam attacks. That's called RCPT harvesting.
My brother runs thille.com using sendmail and he didn't disable VRFY. Nearly all the accounts on there got harvested and we started getting tons of spam. I run thille.org (on qmail) and haven't had that trouble. Since robert@thille.com forwards to my mail server, I just setup TMDA on the address it forwards to.
I've also had trouble with being 'joe-jobbed', where someone sent spam, and forged the 'From:' (and probably the envelope as well) as from me. I got lots of bounces, but luckily no hate mail. SPF would help with that.
The Original Post did qualify that statement with (almost). NetBSD does use fstab and XF86Config would need to be tuned for different video cards. I run two NetBSD systems without X (qube2's as servers), so that wouldn't be a concern for me. The fstabs between any two boxes depends less on the processor/NetBSD version than on the size of the disk and the partition layout. The key with NetBSD is that the configuration differences apply only to the limited area being configured. fstab would need to be changed to deal with differences betwen filesystems on two systems, not CPUs. Using the same Linux distro on two different architectures may give the same sort of 'constancy', but typically you can't get one linux distro that runs on all the architectures supported by some linux distro.
Well, not really. Had dinner with a friend at apple and he's like, "hey, you want any hardware?" And I said, "sure, how about an iPod?" "Oh, not an iPod, we can't make those fast enough."
There's a reason that I've got a lock on the 9mm in my nightstand. Looking for the key, struggling with the lock, etc. gives you time to think that you maybe don't want to put a bullet in the neighbor's dog that's been barking for the last 6 hours...
I just can't watch live TV anymore. If something I want to watch 'right now' is on, at the first comercial break where I'm caught up, I pause it and go channel surfing on the other tuner. On the older tivo (stand alone) I'd go watch a 30min sitcom in 15-20 minutes, and then come back and be able to skip all the commercials and end up catching up at the end of the hour. We spent the thanksgiving long weekend with some friends who we gave a tivo as a present a year or more ago. My friend Dave leaves it on during the commercials. It drove me crazy. At the very least, I pause it, then jump to 'real time', then pause again, or jump back as necessary until the break is over. He'd try muting when I complained, but everyone in the room would sit there and watch the muted commercials. Probably the evolutionary wiring for watching out for preditors.
The extra R&D to put a different monitor size on an iMac is minimal. It's more about shipping and recieving, warehouse and shelf space in stores. With so many sales going online and with 'just in time' inventory those issues are less of a problem. But if someone buys a 20" imac instead of a G5 with a 20" cinema, Apple is losing profit...
Slashdot Mirror
Real programmers use some wire into the j-tag port...
However, I do like using 'svscan' (DJB) behind the init scripts. Shutdown/restart/etc is simple and logging is handled well.
Or SBC :-(
I read the two specific links. Both seem to say basically, "we messed up and exported a stupid API (documented or undocumented), and we're too stupid to just break things."
I as a user (which is who should count more for Microsoft than developers) would rather find out when/before I upgrade to the latest/greatest Windows release that certain programs I have installed won't work because the developers were/are wankers and used unsupported/undocumented APIs. Especially since the alternative is the 'OS' becoming such a morass of insecure, poorly designed APIs that the whole thing is a house of cards.
until I got laid off 40 days ago. Still, add in the insurance, vacation, etc and I can easily see $60/hour.
My NeXT Cube has 15 years OS X experience! Bought it back in 1989, running 0.8 :-)
All variants of "Make it computationally expensive to send e-mail!" prevent all mass mailings of all kinds... not just spam.
But SPAM is unique as a mass mail in that there is no pre-existing relationship between the correspondents. For mailing lists, with SPF subscribers can authenticate that the email actually came from the mailing list (sent from the domain at least, and the domain owner can control the envelope and From: with SMTP-AUTH).
The main problem with mailing lists is that since they do 'mulitply' mail, a spammer could subscribe, and send a SPAM as a subscriber which gets forwarded to all the subscribers (who would likely do limited SPAM filtering on mail from lists to which they were subscribed). On the other hand, lists can do extensive checks on mails coming into the list; require high-value hash-cash, challenge-response, or distributed moderation of messages with a high 'spamminess' based on filters.
Wrong. SPF allows Domain Owners to control who sends email claiming to be from the domain they own!
My ISP has nothing to do with my domains. As far as I am concerned, they are just a pipe. And yes, if you want to send email claiming to be a member/representitive of my domain, I want some control over it.
I just gave my nephews my old Radioshack 110-300 baud terminal with the built-in acoustic coupler and a printer (no video).
:-)
Not sure how old it was, but it's long past it's useful life
I really don't like the inflexibility of the drawer model. A drawer is nicely associated with it's window, but always takes up the screen space whether the window is 'key' or not. I much perfer the the 'panel' approach of NeXTStep. In NeXTStep, you'd have one or a few panels per application, they could hide (or not depending on implementation) when the application wasn't 'front'. The content of the panel would change to track the 'key' window. and the panel could be moved where ever you'd like on the workspace. Given a multi monitor setup, that flexibility can be very very useful.
Yeah, that one. Do you mean wicked good or wicked bad? :-)
For me and my wife at least, was the remake of "The Thin Red Line."
All the star cameos kept giving me hope that there'd be a single character I might grow to care about. I kept hoping that it would somehow redeem itself in the end.
But I was denied and it's still my worst movie ever!
(But I haven't seen Gigli)
Are you suggesting this in concert with SPF? If not, then spammers would just forge the mail as being from a valid address.
What you describe sounds sort of like a challenge-response system (http://tmda.net), but more automated. The trouble with that is the same trouble with VRFY. That is, it can be used to determine whether an address is valid or not for future spam attacks. That's called RCPT harvesting.
My brother runs thille.com using sendmail and he didn't disable VRFY. Nearly all the accounts on there got harvested and we started getting tons of spam. I run thille.org (on qmail) and haven't had that trouble.
Since robert@thille.com forwards to my mail server, I just setup TMDA on the address it forwards to.
I've also had trouble with being 'joe-jobbed', where someone sent spam, and forged the 'From:' (and probably the envelope as well) as from me. I got lots of bounces, but luckily no hate mail. SPF would help with that.
The Original Post did qualify that statement with (almost). NetBSD does use fstab and XF86Config would need to be tuned for different video cards. I run two NetBSD systems without X (qube2's as servers), so that wouldn't be a concern for me. The fstabs between any two boxes depends less on the processor/NetBSD version than on the size of the disk and the partition layout.
The key with NetBSD is that the configuration differences apply only to the limited area being configured. fstab would need to be changed to deal with differences betwen filesystems on two systems, not CPUs.
Using the same Linux distro on two different architectures may give the same sort of 'constancy', but typically you can't get one linux distro that runs on all the architectures supported by some linux distro.
And throw your mouse away!
Well, not really. Had dinner with a friend at apple and he's like, "hey, you want any hardware?" And I said, "sure, how about an iPod?" "Oh, not an iPod, we can't make those fast enough."
Well, maybe I'll get a 15" powerbook instead.
I'm pretty sure that cross compiles is supported for the base-OS, but not for pkgsrc.
At least, that was the case the last time I checked (since compiling a bunch of stuff on my Qube2 instead of my Athlon was way way slower).
There's a reason that I've got a lock on the 9mm in my nightstand. Looking for the key, struggling with the lock, etc. gives you time to think that you maybe don't want to put a bullet in the neighbor's dog that's been barking for the last 6 hours...
I just can't watch live TV anymore. If something I want to watch 'right now' is on, at the first comercial break where I'm caught up, I pause it and go channel surfing on the other tuner. On the older tivo (stand alone) I'd go watch a 30min sitcom in 15-20 minutes, and then come back and be able to skip all the commercials and end up catching up at the end of the hour.
We spent the thanksgiving long weekend with some friends who we gave a tivo as a present a year or more ago. My friend Dave leaves it on during the commercials. It drove me crazy. At the very least, I pause it, then jump to 'real time', then pause again, or jump back as necessary until the break is over.
He'd try muting when I complained, but everyone in the room would sit there and watch the muted commercials.
Probably the evolutionary wiring for watching out for preditors.
NetBSD's pkgsrc works on solaris.
Time to slashdot Cliff Stoll :-)
http://www.kleinbottle.com/
Instead of SMTP, I'll use OFMIP to send 'messages' instead of emails...
the power to destroy.
The extra R&D to put a different monitor size on an iMac is minimal. It's more about shipping and recieving, warehouse and shelf space in stores. With so many sales going online and with 'just in time' inventory those issues are less of a problem. But if someone buys a 20" imac instead of a G5 with a 20" cinema, Apple is losing profit...