ISPs do need to more closely monitor mail that is sent from their subscribers computers--not the content but the destination and headers. Similarly, ISPs need to filter incoming mail as described below. I am glad to see an ISP like BigPond taking some step though I think they could more narrowly tailor their efforts.
Right now three domains owned by members of my family have been chosen by spammers as the forged source domain for their spams, which are primarily sent to AOL, MSN, Yahoo. Working with AOL's postmaster team (which took a long time to find), we have determined these messages originate all over the world from a number of machines on many dozen ISPs and universities--directly from clients on those networks, not mail servers. AOL says there isnt a thing they can do about it (apparently even thousands of spam messages aren't a lot for them and no filtration process exists to, say, block any email which purports to originate from a domain but doesn't originate from the ip address of that domains email server) and I should contact each network directly (a daunting task since no one reads postmaster emails anymore).
Meanwhile, AOL's, MSN, Yahoo, etc. postmaster account sends hundreds of rejected messages to our domains daily.
The spammers' chosen method seem to be to create a relay on these public access networks. Chose a random source domain (which remains relatively constant) and then apply a number of random email account names to create a forged source. Then send to every possible subscriber at a major ISP in small but continuous batches.
Short of requiring authenticated emails, it would still seem relatively easy to detect this spam both leaving and coming in to an ISP:
-- mail is being sent directly from a client and not relayed either through the ISPs mail server or another relay which matches the reply to domain. -- mail from the same machine continually iterates reply-to names -- if 100s of messages are being rejected, then logically 1000s must be successfully sent--which means these machines should be more than a blip on ISPs server logs. -- while messages come in waves, they continue throughout the day (and mail sent by humans is sent in small batches usually during waking hours)
What I would really like is a registry, perhaps tied to my domain registrar, wherein I can register the mail server(s) of my domain(s) and other ISPs can do a lookup for incoming mail and block email which isn't relayed through that mail server/IP address. This simple method would stop all my spam--at least until spammers find a new method.
This entire effort seems misguided. If one wanted to share one's MP3 collection for the purpose of copying, one could simply create a shared network folder.
Much more useful would be a server which creates a "virtual" AAC or MP3 collection which can then be played back in iTunes. The nicest things about iTunes are a.) its interface (including live search) and b.) its iPod compatibility. But its support for formats other than MP3/AAC/WAV--most notably FLAC, as contrasted with foobar2000 or Winamp, is sorely lacking. By contrast, foobar2000 and Winamp, have much less aesthetically pleasing interfaces and no iPod support. So, a daemon which did on the fly conversion of, say FLAC to MP3, would permit playback and transfer of your lossless audio collection in iTunes or another other device which supports ZeroConfig (such as Tivo Home Media Option). And that server daemon could be implemented as a plugin to either foobar or Winamp.
All I get is an error dialog:
The folder iTunes cannot be found or created, and is required. The default location for this folder is inside the Music folder
Nothing more.
Mono needs patron saints with their own patent portfolios (and cross-licensing arrangements with Microsoft). For example, Novell's sponsorship is better than Ximian because (I recall) that Novell has entered into several cross-licensing agreements with MS (though how current these are, I can't say).
A big plus would be IBM, Apple, and/or Intel's direct sponsorship (not just code contributions), since they also maintain large patent portfolios and cross-licensing agreements with MS.
My music collection is in FLAC. Instead of creating a redundant collection in MP3/AAC, I want to simply sync a portion of my existing files.
Why should Apple deliver FLAC support in a firmware upgrade?
1.) The competition is already there: Rio Karma and the Nueros (will) support FLAC.
2.) What better way to seller the high end models with the large hard drives: FLAC needs on average 5x more space than MP3.
3.) Unlike AAC v. OGG, there is no competing Apple lossless codec.
And this is why DVD regional encoding is evil.
Amazon.co.uk says its only available in region 2, which means I spend a lot of money to have something that can't play on my DVD player in the living room.
Meanwhile, its not available on Amazon.com. And probably never will be.... And forget about seeing it at Blockbuster/Netflix...
Maybe cable/PBS will reair the original series now
on
Blakes Seven To Return
·
· Score: 2, Interesting
I haven't seen Blake's 7 on TV in over a decade. (I even have a Tivo search for it).
Maybe the sequel miniseries will prompt someone to reair the original series. BBC America at 2am? Anyone???
I can't speak to the whether MP3.com's moves are due to high bandwidth costs, but I think that we should address the larger issue of why streamed music/radio broadcasts are still unicast, with a per user increase in bandwidth consumption.
Why isn't the world adopting multicasting? This would seem a win-win solution? Broadcasters could signifcantly reduce their bandwidth consumption while ensuring higher audio quality and reducing buffering due to server overload. ISPs could significantly reduce their IP traffic because they could proxy one stream for all their users. Users wouldn't be shut out of popular servers.
Is the hold up still the router manufacturers? Or is it server software like Shoutcast, which is still unicast based?
Aside from the constitutional issues with the DMCA, in an age of wireless LANs, I would suggest that there is increasingly an issue of whether there is probable cause for a search warrant of an access customer's premises and equipment based merely on the tying of allegedly illegal activities to an IP address allocated to that customer at the time that the activities were allegedly committed.
For example, I live in an apartment building. In addition to my own wLAN, there are five (count 'em) wLANS, three of which aren't even encrypted (and using such imaginative names as Linksys and default).
My point is that, at least in high density areas, there are plenty of wLANS on which third parties can piggyback--and such should be factored into any determination of probable cause.
AOL has petitioned the FCC to lift the restriction on advanced IM services even though it has not opened its IM network to competitors.
The FCC should deny AOL's petition so as to ensure that instant messaging systems are as interoperable as email systems. Pointing to the growth of rebadged versions of their own service (such as that provided by Apple) or the growth of competitors' services (which is primarily the result of people running multiple clients/services to keep in touch with their friends) does not justify keeping their current service closed or thwarting clients such as Trillian which attempt to unify all services with one front end.
I don't want to have to sign up for different proprietary services or use separate clients for each service just to keep in contact with my friends. Just like email, I want to have one instance, preferrably on a server run by me (so as to reduce privacy invasions), wherein any permitted individual can instant message/SMS me regardless of their client or instant messaging server.
AOL has never seriously attempted to open their service, specifically, to allow their users to contact and by contacted by any other service's user, regardless of client. They shouldn't be rewarded by the FCC now for their stalling tactics.
I don't see any reference to jigdo and downloading a full CD, particularly when I have Debian CDs lying around seems inefficient. Is there a jigdo for Knoppix given its Debian origins???
Slashdot Mirror
ISPs do need to more closely monitor mail that is sent from their subscribers computers--not the content but the destination and headers. Similarly, ISPs need to filter incoming mail as described below. I am glad to see an ISP like BigPond taking some step though I think they could more narrowly tailor their efforts.
Right now three domains owned by members of my family have been chosen by spammers as the forged source domain for their spams, which are primarily sent to AOL, MSN, Yahoo. Working with AOL's postmaster team (which took a long time to find), we have determined these messages originate all over the world from a number of machines on many dozen ISPs and universities--directly from clients on those networks, not mail servers. AOL says there isnt a thing they can do about it (apparently even thousands of spam messages aren't a lot for them and no filtration process exists to, say, block any email which purports to originate from a domain but doesn't originate from the ip address of that domains email server) and I should contact each network directly (a daunting task since no one reads postmaster emails anymore).
Meanwhile, AOL's, MSN, Yahoo, etc. postmaster account sends hundreds of rejected messages to our domains daily.
The spammers' chosen method seem to be to create a relay on these public access networks. Chose a random source domain (which remains relatively constant) and then apply a number of random email account names to create a forged source. Then send to every possible subscriber at a major ISP in small but continuous batches.
Short of requiring authenticated emails, it would still seem relatively easy to detect this spam both leaving and coming in to an ISP:
-- mail is being sent directly from a client and not relayed either through the ISPs mail server or another relay which matches the reply to domain.
-- mail from the same machine continually iterates reply-to names
-- if 100s of messages are being rejected, then logically 1000s must be successfully sent--which means these machines should be more than a blip on ISPs server logs.
-- while messages come in waves, they continue throughout the day (and mail sent by humans is sent in small batches usually during waking hours)
What I would really like is a registry, perhaps tied to my domain registrar, wherein I can register the mail server(s) of my domain(s) and other ISPs can do a lookup for incoming mail and block email which isn't relayed through that mail server/IP address. This simple method would stop all my spam--at least until spammers find a new method.
This entire effort seems misguided. If one wanted to share one's MP3 collection for the purpose of copying, one could simply create a shared network folder.
Much more useful would be a server which creates a "virtual" AAC or MP3 collection which can then be played back in iTunes. The nicest things about iTunes are a.) its interface (including live search) and b.) its iPod compatibility. But its support for formats other than MP3/AAC/WAV--most notably FLAC, as contrasted with foobar2000 or Winamp, is sorely lacking. By contrast, foobar2000 and Winamp, have much less aesthetically pleasing interfaces and no iPod support. So, a daemon which did on the fly conversion of, say FLAC to MP3, would permit playback and transfer of your lossless audio collection in iTunes or another other device which supports ZeroConfig (such as Tivo Home Media Option). And that server daemon could be implemented as a plugin to either foobar or Winamp.
All I get is an error dialog: The folder iTunes cannot be found or created, and is required. The default location for this folder is inside the Music folder Nothing more.
Mono needs patron saints with their own patent portfolios (and cross-licensing arrangements with Microsoft). For example, Novell's sponsorship is better than Ximian because (I recall) that Novell has entered into several cross-licensing agreements with MS (though how current these are, I can't say).
A big plus would be IBM, Apple, and/or Intel's direct sponsorship (not just code contributions), since they also maintain large patent portfolios and cross-licensing agreements with MS.
Then it simply becomes a matter of horse-trading.
This could be especially useful for, say, an iPod.
My music collection is in FLAC. Instead of creating a redundant collection in MP3/AAC, I want to simply sync a portion of my existing files. Why should Apple deliver FLAC support in a firmware upgrade? 1.) The competition is already there: Rio Karma and the Nueros (will) support FLAC. 2.) What better way to seller the high end models with the large hard drives: FLAC needs on average 5x more space than MP3. 3.) Unlike AAC v. OGG, there is no competing Apple lossless codec.
And this is why DVD regional encoding is evil. Amazon.co.uk says its only available in region 2, which means I spend a lot of money to have something that can't play on my DVD player in the living room. Meanwhile, its not available on Amazon.com. And probably never will be.... And forget about seeing it at Blockbuster/Netflix...
I haven't seen Blake's 7 on TV in over a decade. (I even have a Tivo search for it). Maybe the sequel miniseries will prompt someone to reair the original series. BBC America at 2am? Anyone???
I can't speak to the whether MP3.com's moves are due to high bandwidth costs, but I think that we should address the larger issue of why streamed music/radio broadcasts are still unicast, with a per user increase in bandwidth consumption. Why isn't the world adopting multicasting? This would seem a win-win solution? Broadcasters could signifcantly reduce their bandwidth consumption while ensuring higher audio quality and reducing buffering due to server overload. ISPs could significantly reduce their IP traffic because they could proxy one stream for all their users. Users wouldn't be shut out of popular servers. Is the hold up still the router manufacturers? Or is it server software like Shoutcast, which is still unicast based?
Aside from the constitutional issues with the DMCA, in an age of wireless LANs, I would suggest that there is increasingly an issue of whether there is probable cause for a search warrant of an access customer's premises and equipment based merely on the tying of allegedly illegal activities to an IP address allocated to that customer at the time that the activities were allegedly committed. For example, I live in an apartment building. In addition to my own wLAN, there are five (count 'em) wLANS, three of which aren't even encrypted (and using such imaginative names as Linksys and default). My point is that, at least in high density areas, there are plenty of wLANS on which third parties can piggyback--and such should be factored into any determination of probable cause.
AOL has petitioned the FCC to lift the restriction on advanced IM services even though it has not opened its IM network to competitors.
The FCC should deny AOL's petition so as to ensure that instant messaging systems are as interoperable as email systems. Pointing to the growth of rebadged versions of their own service (such as that provided by Apple) or the growth of competitors' services (which is primarily the result of people running multiple clients/services to keep in touch with their friends) does not justify keeping their current service closed or thwarting clients such as Trillian which attempt to unify all services with one front end.
I don't want to have to sign up for different proprietary services or use separate clients for each service just to keep in contact with my friends. Just like email, I want to have one instance, preferrably on a server run by me (so as to reduce privacy invasions), wherein any permitted individual can instant message/SMS me regardless of their client or instant messaging server.
AOL has never seriously attempted to open their service, specifically, to allow their users to contact and by contacted by any other service's user, regardless of client. They shouldn't be rewarded by the FCC now for their stalling tactics.
I don't see any reference to jigdo and downloading a full CD, particularly when I have Debian CDs lying around seems inefficient. Is there a jigdo for Knoppix given its Debian origins???