Autopron has a nice filtering capacity, that you can use to see what you want to see. Just click on the 'search' link on the top of the page, near the color scheme chooser. For example, setting filter to "Asian" would return only links with pictures of Asian women.
Also, I've recently set up a moderation system so other people can post links if they want to.
If you feel a site is really nasty, you can email it, and I may delete it if I agree. However, there are people out there who do go for that stuff sometimes, and I want at least some of them to enjoy the site as well.
Finally, read the descriptions, you don't have to click each link.
If anyone out there thinks that the Chinese couldn't have done this on their own, that only Americans can build routers... Well, the seriously need to reevaluate their assumptions.
China could have done this without outside help, China should have free speech. They don't. Not building firewalls for them isn't going to open their society.
Since Mao died, the living standards of the average Chinese person has skyrocketed. Deng Xiao Peng created a lot of reforms, economically (saying "It's not bad, to be rich"), and even in terms of free speech and political expression. After Tiananmen they clamped back down. I don't really know if you can blame them either, if you just lived through the cultural revolution, you would probably be very afraid as well. Mid-century China was a veritable case study in how 'harmless' politics and mass youth movements can cause huge problems.
Maybe Tiananmen was do soon, and the students really blew it. They should have stuck with Op-Ed pages, and built support that way, protesting only set them back, a lot. China today doesn't allow anywhere near the political expression that existed in the 1980s.
But that said, people who's lives are getting better and better every year are not going to really want to revolt.
And keep in mind that democracy and freedom of speech is an exception in all of human history. Maybe someday, but don't think it will happen anytime soon. Happy citizens don't revolt.
I doubt you would be able to get many people onboard for your "blackhole the chinese".
Yeh, spam is annoying, and I take mesures to keep my address out of the hands of spiders. But getting a couple ping packets isn't going to make me keep my selection of fine pornographic links from chinese citizens. (if they arn't blocked already, I doubt the CCP really cares about a 1k impression/day site run from a dorm room:P)
Do these things work with digital cable? Most of the coolest stuff on HBO, Showtime, MTV2 is really only available with digital cable. Would these things work with that?
part of it is machine readablity. You can parse the second a lot easier if you already have an XML parser. That lets you do things like let installs of software modify the config of other things to include them (this would be great with Apache). As well as GUI things. How would a gui know to associate that comment with that option.
Also, you probably wouldn't just use <option/> tags, thats' just bad/lazy XML. Probably more like this
<logon>
&<!- this options specifies a script to run for every user -->
<scriptForAllUsers file="U.bat">
</logon>
Then in your DTD or Shema you would define what it does. programicaly, so that the comment would show up in a GUI as well.
Anyway, humans can read anything a computer can, with practice, including binary. It's just a question of how long it takes them to learn. XML does not take that much time.
Actually, you wouldn't need two separate XML files. XML already has the capacity to 'describe' itself via DTDs, as well as XML schemas.
Basically they let you write a description of what your XML document contains (indeed, you need those if you want to have a "valid" XML doc). A standard XML Schema could be developed for "Linux Config", and developers could derive from that any special config options they would need.
You could also use XLST to convert from "app space" where all the tags are descriptive to the domain of the problem (<TCPport port="80"/> to <inetd:setport port="80" service="apache"> people could edit it in either form and have the changes roll back between the two. That way you could have a GUI for apache and inetd and make changes in either and automatically have it propagate all over the system, check for conflicts, etc.
I wanted to use Linux as a server, as it seemed to be the 'thing to do', as well as the fact that run all that cool server code that was only available for Linux, as well as get experience running a Linux box.
Having a Linux box has allowed me to have a mail/DNS server with a very high uptime, as well as a (non-porn:P) scoop site.
I'm not saying it wasn't fun, but it's not something I want to go through all the time... that's why autopr0n.com uses tomcat on windows with an M$ access file rather then on Linux with Postgresql or MySQL or something. That would probably be a better solution (and eventually I'll migrate, or at least move up to a pirated copy of SQLServer:P), but it's just a lot less of a hassle to set those things up on windows.
Please, that's the bigest lie in all of this. The idea that what you are doing in Unix is "hard." It's not. Once you learn the config files, getting things set up takes just a few seconds. I can ad a new domain to my DNS server in just a minute or two (just copy a file and modify as needed). I can set up a new share in Samba's web-based config quickly and secure it via IP range or windows username (I would assume it would take just a copy/paste/modify in the config files as well).
I didn't have much trouble handling the apache config either for adding Tomcat on windows or scoop on linux either. (in the case of scoop, all I had to do was copy a pre-genererated text file into my apache conf file).
It's not hard, it just takes time to learn all these damn config formats.
A standard system for editing would go a long way to making things easier. People could spend time learning about how things really work rather then how lazy the author of the software was in writing their config parsers.
XML+some schemas for common things would really help. In the case of Scoop I mentioned, I wouldn't have even had to do the useless and idiotic step of copying data one from one file to another manualy... it could be done by Make via a standard XML parsing API, or perhaps a standard config library.
You expect the open source community to use Java!? It's plain C all the way! (just look at Genome... hell, there are some guys (dotGNU IIRC) who want to implement.net in plain C!)
Ok, so that's not entirely true. Some OSS people like java (Freenet, Apache Jakarta). But I seriously doubt that anything Java based would ever make much inroads in the free Unix world. (Maybe Solaris could make some headway, though:P).
And there's a few good reasons why it shouldn't. Java is a little top-heavy, and it's not platform-neutral, it's its own platform... and connecting it to other technology via the JNI is a pain in the ass. I tried JavaBeans once, on a windows box at work. It was a nightmare. I ended up using TCP/IP for interprocess communications. (then again, TCP/IP might not be a bad choice for a central config server, you could do things like remote config. hrm)
Anyway, I think XML plus some schemas might go a long way to doing what we want, without requiring everyone to link in a JVM.
Hardware, for the most part, can be automaticaly configured. In fact, I've never once had an issue with hardware configuration in linux (except for tonight, ironicaly. cdrecord can't find the burner I put back in the system, even though it worked before)
The problem is software config once you've already got the machine setup. Programs generaly have diffrent formats for their configuration. even windows 3.1 was better then this with their.INI files. geez.
Sure, installing software is easy. Unpack and compile. We are talking about configuring software.
Like getting sendmail to rout and forward mail, apache to serve up web pages you want, BIND to bind names to IP address, etc.
These tasks arn't "hard" or anything, but they do require a lot of reading on the part of a Newbie. In the windows world (don't know much about OSX) Most of that stuff can be done via am intuitive GUI.
Flame me if you want, but I'd greatly prefer a system that didn't require me to learn diffrent config file formats for each service I want to have running... or deal with a hodgepoge of 'easy config' program hacks.
A simple, standard configuration system is definetly the way to go.
That link isn't particularly helpfull. I hope you don't expect me the dig around on that site for hours to find the answer.
Perhaps you could give me a more precice link.
The only thing I could find was:
But good looks are only the beginning. At the foundation of Mac OS X lies an industrial-strength, UNIX-based core operating system--called Darwin--that delivers unprecedented stability and performance. Darwin provides Mac OS X with powerful, advanced features such as protected memory, preemptive multitasking, advanced memory management, and...
Etc. Didn't say anything about what it was 'based' on.
Who hasn't though this? Unix/Linux config is a mess. Diffrent files in diffrent folders with diffrent formats. Sure it's all plain text, but who has time to learn diffretn config formats/languages for each program they want to use?
As for hard to do? I don't see why that would be the case. Just a little bit of XML and viola.
There are a lot of things in the Unix world that are hard or time consuming to do just because they can be. sendmail.cf. hello!?
I mention autopr0n in my sig, but the majority of my posts here do not talk about it. If you want to see for your self, just go here and read the last 25 commenst I've made.
De Viron's team found that earthlings can expect the length of an average day to increase by 11 millionths of a second per decade, corresponding to an overall increase of about one ten-thousandth of a second by the close of the century.
OH MY GOD!!!! A HUNDRED MILLIONTHS OF A SECOND!! WE'RE ALL GONNA DIE!
This seems more like 'hey, look at this' then 'hey we have to do something!' I don't really think a few hundred thousanths of a second could screw anything up.
And those that say the earth would get hotter... we would also have longer nights as well.
Autopron has a nice filtering capacity, that you can use to see what you want to see. Just click on the 'search' link on the top of the page, near the color scheme chooser. For example, setting filter to "Asian" would return only links with pictures of Asian women.
Also, I've recently set up a moderation system so other people can post links if they want to.
If you feel a site is really nasty, you can email it, and I may delete it if I agree. However, there are people out there who do go for that stuff sometimes, and I want at least some of them to enjoy the site as well.
Finally, read the descriptions, you don't have to click each link.
If anyone out there thinks that the Chinese couldn't have done this on their own, that only Americans can build routers... Well, the seriously need to reevaluate their assumptions.
China could have done this without outside help, China should have free speech. They don't. Not building firewalls for them isn't going to open their society.
Since Mao died, the living standards of the average Chinese person has skyrocketed. Deng Xiao Peng created a lot of reforms, economically (saying "It's not bad, to be rich"), and even in terms of free speech and political expression. After Tiananmen they clamped back down. I don't really know if you can blame them either, if you just lived through the cultural revolution, you would probably be very afraid as well. Mid-century China was a veritable case study in how 'harmless' politics and mass youth movements can cause huge problems.
Maybe Tiananmen was do soon, and the students really blew it. They should have stuck with Op-Ed pages, and built support that way, protesting only set them back, a lot. China today doesn't allow anywhere near the political expression that existed in the 1980s.
But that said, people who's lives are getting better and better every year are not going to really want to revolt.
And keep in mind that democracy and freedom of speech is an exception in all of human history. Maybe someday, but don't think it will happen anytime soon. Happy citizens don't revolt.
I doubt you would be able to get many people onboard for your "blackhole the chinese".
:P)
Yeh, spam is annoying, and I take mesures to keep my address out of the hands of spiders. But getting a couple ping packets isn't going to make me keep my selection of fine pornographic links from chinese citizens. (if they arn't blocked already, I doubt the CCP really cares about a 1k impression/day site run from a dorm room
Do these things work with digital cable? Most of the coolest stuff on HBO, Showtime, MTV2 is really only available with digital cable. Would these things work with that?
Its just so wrong for that scgmille to copy so blatently from that poorscgmile guy. er. wait...
This was also posted to another scoop site, kuro5hin :)
For those of you who care, Ian Clark also commented on the story himself(1 2 3 4 5)
part of it is machine readablity. You can parse the second a lot easier if you already have an XML parser. That lets you do things like let installs of software modify the config of other things to include them (this would be great with Apache). As well as GUI things. How would a gui know to associate that comment with that option.
/> tags, thats' just bad/lazy XML. Probably more like this
Also, you probably wouldn't just use <option
<logon>
&<!- this options specifies a script to run for every user -->
<scriptForAllUsers file="U.bat">
</logon>
Then in your DTD or Shema you would define what it does. programicaly, so that the comment would show up in a GUI as well.
type this at your command line for me real quick:
/etc/sendmail.cf | more
cat
You call that human readable? Hah!
Anyway, humans can read anything a computer can, with practice, including binary. It's just a question of how long it takes them to learn. XML does not take that much time.
Actually, you wouldn't need two separate XML files. XML already has the capacity to 'describe' itself via DTDs, as well as XML schemas.
/> to <inetd:setport port="80" service="apache"> people could edit it in either form and have the changes roll back between the two. That way you could have a GUI for apache and inetd and make changes in either and automatically have it propagate all over the system, check for conflicts, etc.
Basically they let you write a description of what your XML document contains (indeed, you need those if you want to have a "valid" XML doc). A standard XML Schema could be developed for "Linux Config", and developers could derive from that any special config options they would need.
You could also use XLST to convert from "app space" where all the tags are descriptive to the domain of the problem (<TCPport port="80"
If you go to sendmail.com you'll see they sell a 'pro' version with a nice GUI. I'm pretty sure they keep the text config complex for a reason :P
I wanted to use Linux as a server, as it seemed to be the 'thing to do', as well as the fact that run all that cool server code that was only available for Linux, as well as get experience running a Linux box.
:P) scoop site.
:P), but it's just a lot less of a hassle to set those things up on windows.
Having a Linux box has allowed me to have a mail/DNS server with a very high uptime, as well as a (non-porn
I'm not saying it wasn't fun, but it's not something I want to go through all the time... that's why autopr0n.com uses tomcat on windows with an M$ access file rather then on Linux with Postgresql or MySQL or something. That would probably be a better solution (and eventually I'll migrate, or at least move up to a pirated copy of SQLServer
Please, that's the bigest lie in all of this. The idea that what you are doing in Unix is "hard." It's not. Once you learn the config files, getting things set up takes just a few seconds. I can ad a new domain to my DNS server in just a minute or two (just copy a file and modify as needed). I can set up a new share in Samba's web-based config quickly and secure it via IP range or windows username (I would assume it would take just a copy/paste/modify in the config files as well).
I didn't have much trouble handling the apache config either for adding Tomcat on windows or scoop on linux either. (in the case of scoop, all I had to do was copy a pre-genererated text file into my apache conf file).
It's not hard, it just takes time to learn all these damn config formats.
A standard system for editing would go a long way to making things easier. People could spend time learning about how things really work rather then how lazy the author of the software was in writing their config parsers.
XML+some schemas for common things would really help. In the case of Scoop I mentioned, I wouldn't have even had to do the useless and idiotic step of copying data one from one file to another manualy... it could be done by Make via a standard XML parsing API, or perhaps a standard config library.
You expect the open source community to use Java!? It's plain C all the way! (just look at Genome... hell, there are some guys (dotGNU IIRC) who want to implement .net in plain C!)
:P).
Ok, so that's not entirely true. Some OSS people like java (Freenet, Apache Jakarta). But I seriously doubt that anything Java based would ever make much inroads in the free Unix world. (Maybe Solaris could make some headway, though
And there's a few good reasons why it shouldn't. Java is a little top-heavy, and it's not platform-neutral, it's its own platform... and connecting it to other technology via the JNI is a pain in the ass. I tried JavaBeans once, on a windows box at work. It was a nightmare. I ended up using TCP/IP for interprocess communications. (then again, TCP/IP might not be a bad choice for a central config server, you could do things like remote config. hrm)
Anyway, I think XML plus some schemas might go a long way to doing what we want, without requiring everyone to link in a JVM.
Hardware, for the most part, can be automaticaly configured. In fact, I've never once had an issue with hardware configuration in linux (except for tonight, ironicaly. cdrecord can't find the burner I put back in the system, even though it worked before)
.INI files. geez.
The problem is software config once you've already got the machine setup. Programs generaly have diffrent formats for their configuration. even windows 3.1 was better then this with their
Sure, installing software is easy. Unpack and compile. We are talking about configuring software.
Like getting sendmail to rout and forward mail, apache to serve up web pages you want, BIND to bind names to IP address, etc.
These tasks arn't "hard" or anything, but they do require a lot of reading on the part of a Newbie. In the windows world (don't know much about OSX) Most of that stuff can be done via am intuitive GUI.
Flame me if you want, but I'd greatly prefer a system that didn't require me to learn diffrent config file formats for each service I want to have running... or deal with a hodgepoge of 'easy config' program hacks.
A simple, standard configuration system is definetly the way to go.
That link isn't particularly helpfull. I hope you don't expect me the dig around on that site for hours to find the answer.
Perhaps you could give me a more precice link.
The only thing I could find was: But good looks are only the beginning. At the foundation of Mac OS X lies an industrial-strength, UNIX-based core operating system--called Darwin--that delivers unprecedented stability and performance. Darwin provides Mac OS X with powerful, advanced features such as protected memory, preemptive multitasking, advanced memory management, and...
Etc. Didn't say anything about what it was 'based' on.
Who hasn't though this? Unix/Linux config is a mess. Diffrent files in diffrent folders with diffrent formats. Sure it's all plain text, but who has time to learn diffretn config formats/languages for each program they want to use?
As for hard to do? I don't see why that would be the case. Just a little bit of XML and viola.
There are a lot of things in the Unix world that are hard or time consuming to do just because they can be. sendmail.cf. hello!?
Its based on NeXT. With a NetBSD compatablity layer.
I mention autopr0n in my sig, but the majority of my posts here do not talk about it. If you want to see for your self, just go here and read the last 25 commenst I've made.
But you could do it by running an audio signal through main coil.
have you?
I think the key in picking colours for any website is that they have have a difference of at least X in brightness
The key to picking colors for a website is LOOKING AT THEM
You have no idea what you're talking about. The amount of CO2 going into the air is known... the affect on the weather is what's in question.
All life did not die.
De Viron's team found that earthlings can expect the length of an average day to increase by 11 millionths of a second per decade, corresponding to an overall increase of about one ten-thousandth of a second by the close of the century.
OH MY GOD!!!! A HUNDRED MILLIONTHS OF A SECOND!! WE'RE ALL GONNA DIE!
This seems more like 'hey, look at this' then 'hey we have to do something!' I don't really think a few hundred thousanths of a second could screw anything up.
And those that say the earth would get hotter... we would also have longer nights as well.