But if this is done at the ISP level it IS a company collecting data about children. I'd assume that they couldn't do this without the parents concent, and with parents allready not taking an active interest in what their kids are doing online, the whole idea goes up in a poof of smoke. Bush's plan isn't much better.
Let's give these canidates a reality check. Force them to use a viraty of filtering systems for their day to day tasks. Let's do this durrning the campain season so it hits them when it hurts. If the filtering system prevents them from working efficiently, they might change their view. If not, we tried. Better yet, change the filtering system on a weekly basis. They are at the whim of the administrator. The Administrator must be, of course, and overworked IT person who really have better things to do than go through the web logs.
Having this administrator being a represintive of the company providing the filtering software will also not do.
I'm not in favor of this filtering thing. (Actually, it's not a bad idea for computers in the childrens area of the libiary.), but adults shouldn't be able to use public equipment to gain access to material that will never be available in any public libiary.
My compromise idea is something on the lines of: train the libiary staff on how to add sites to the allow list. (Make a nice web interface for squid or something.) Whenever the users hits a site that was blocked, a page explaining the procedure will be displayed. They will then either fill out the request form or go to the libiary staff. The libiary staff will review the site and user their own judgment on the spot.
At the end of a given time period, the modifications to the list will be reviewed by a board of voulenteers. Sites can again be added or removed. After the meeting, the results will be posted for public review. At any time a voting user can go to the public libiary and request access to every site on the list, and give their vote on any listed site. These public votes will again be reviewd.
And so the process continues, each filtering site shares it's list and every voter has a a say.
Wow, I should write my congressman. Maybe I can get a grant or something!
"Also, keep in mind that applications written to "target" a freeware GUI such as Gnome, KDT, Enlightenment, or one of the others floating around out there, likely will not work with the industry standard CDE, on which DeXtop is based."
So basically, they tell you that all the up to date, brand spanking new, award winning (ok...and mozzila too...) free software on available for linux won't work when you use their product?
Sounds like a shoe in for Best Acid Trip at LWCE 2000, with great potential for a repeat award. I wonder if the marketing guys at their boot knew why everyone was pointing and laughing at them.
Idealy, who is your target audience? The computer novice who want to do web browsing and play you don't know jack games on their TV? The guru who wants to play the latest and greatet 3D drivil? The geek who says "hey neat, it runs linux! I wonder what I can do to void the waranty today?" All of the above maybe?
How will developers respond? Will they embrace the platform or ignore it in favor of the PSX2. What software can we expect to be available the the platform is released?
Interesting situation. AT&T bought up MediaOne. MediaOne wanted to get brodband every where it could, but local telcos didn't want to lay fiber. MediaOne decided to screw waiting for the telcos to get off their lazy asses ( US West is now Quest! ) and lay the fiber themselves. First they fired up digital calbe, shortly followed by two-way cable, taking a big dent out of US West (is now Quest!)'s DSL market.
MediaOne planned on offering telephone serverice over their newly laid fiber as well, and since AT&T bought them, I'm sure that hasn't changed.
Now the really interesting part. Internet access. MediaOne and TimeWarner both offer the same service, Road Runner. I belive this service is a MediaOne spawn, so I'm sure AT&T isn't incredibly happy having to share with TimeWarner, but I like Time Warner's flavor of Road Runner, as I have yet to hit a limit of dynamic IP's I can pull.
That's a breif and under-informed summery of the Minneapolis/St. Paul metro...
Simple enough. task-packages are just empty packages. No content at all. All a task package is is a debian package that depends on a bunch of related packages, and suggest others.
That way, you can type apt-get install task-gnome task-samba task-c-dev etc, and apt will download and install that selection of packages.
When using dselect with task-packages, I've found it best to select the task packages (+) to bring up the depends selection, then set the task package to purge (_), but keep the packages that the task package depended on. You may want to keep the task package installed so if something is added to that task, you're next apt-get upgrade will grab that package as well. On the otherhand, if you don't want something that's in a task-package, dselect will complain because the task-package depends on that package.
It's not a big deal with stable, since the only task packages that will be updated are those from helix and other non-offical packages.
Looks like TDYC allready has it packed up and ready for apt. The apt source is:
deb ftp://kde.tdyc.com/pub/kde/debian unstable kde2
Do an apt-get update, then apt-get install task-kde and you're ready to go.
Enjoy. I've been running the kooldown release awile now, so far I like it. Startup is a bit slower than GNOME though. Wonder if that's changed in the latest version...
*Sometimes* makefiles have a make uninstall option. But that is a slight flaw in the nature of package managment, if there isn't an actual package, things could get messy.
I personally use stow to manage software that isn't part of the distribution. When compiling, --prefix=/usr/local/stow/package-name then build as normal. When it's done, cd to/usr/local/stow and type stow package-name, and stow creates symlinks in/usr/local. Slick. To remove, stow -D package-name, rm -rf/usr/local/stop/package-name
AOL has a "monopoly" on the instant messaging market. In other words, they can and will stifle future development of IM products BECAUSE they dominate.
I don't know that they have a monopoly. If they do, they're not trying to use said monopoly to stifle competition in the IM market. There's ICQ, MSN, Yahoo, Excite, Jabber, Everybody, well, the list goes on. AOL wasn't even the first on the scene. Yes you could IM another AOL user before AIM, but ICQ beat AIM to the internet crowd. Really, AOL should make a big stink about it. AIM is just an internet enabled version of the IM protocol they developed. No one has rights to all their hard work. AOL is nice enough to let the Open Source community use the service they built from the ground up.
I'd be very dissapointed if they did block out 3rd party clients, but it wouldn't be the end of the world. If all esle fails, there is IRC. So please, don't go around saying AOL has a Monopoly when they really don't. They are the "number one" online service provider, and they bundle their IM software in their package. No wonder they have most of the market share. But I still don't see any evidence of abuse of monopoly power. Remember, it isn't the monopoly itself that illeagal, it's the use of the monopoly to stifle competition.
Slashdot Mirror
But if this is done at the ISP level it IS a company collecting data about children. I'd assume that they couldn't do this without the parents concent, and with parents allready not taking an active interest in what their kids are doing online, the whole idea goes up in a poof of smoke. Bush's plan isn't much better.
Let's give these canidates a reality check. Force them to use a viraty of filtering systems for their day to day tasks. Let's do this durrning the campain season so it hits them when it hurts. If the filtering system prevents them from working efficiently, they might change their view. If not, we tried. Better yet, change the filtering system on a weekly basis. They are at the whim of the administrator. The Administrator must be, of course, and overworked IT person who really have better things to do than go through the web logs.
Having this administrator being a represintive of the company providing the filtering software will also not do.
I'm not in favor of this filtering thing. (Actually, it's not a bad idea for computers in the childrens area of the libiary.), but adults shouldn't be able to use public equipment to gain access to material that will never be available in any public libiary.
My compromise idea is something on the lines of: train the libiary staff on how to add sites to the allow list. (Make a nice web interface for squid or something.) Whenever the users hits a site that was blocked, a page explaining the procedure will be displayed. They will then either fill out the request form or go to the libiary staff. The libiary staff will review the site and user their own judgment on the spot.
At the end of a given time period, the modifications to the list will be reviewed by a board of voulenteers. Sites can again be added or removed. After the meeting, the results will be posted for public review. At any time a voting user can go to the public libiary and request access to every site on the list, and give their vote on any listed site. These public votes will again be reviewd.
And so the process continues, each filtering site shares it's list and every voter has a a say.
Wow, I should write my congressman. Maybe I can get a grant or something!
An anchor inside and anchor, good one.
Who Invented the what?
Maybe they can drop Mir in the Outback and Australia will forget about SkyLab. =)
"Also, keep in mind that applications written to "target" a freeware GUI such as Gnome, KDT, Enlightenment, or one of the others floating around out there, likely will not work with the industry standard CDE, on which DeXtop is based."
So basically, they tell you that all the up to date, brand spanking new, award winning (ok...and mozzila too...) free software on available for linux won't work when you use their product?
Sounds like a shoe in for Best Acid Trip at LWCE 2000, with great potential for a repeat award. I wonder if the marketing guys at their boot knew why everyone was pointing and laughing at them.
Idealy, who is your target audience? The computer novice who want to do web browsing and play you don't know jack games on their TV? The guru who wants to play the latest and greatet 3D drivil? The geek who says "hey neat, it runs linux! I wonder what I can do to void the waranty today?" All of the above maybe?
;)
How will developers respond? Will they embrace the platform or ignore it in favor of the PSX2. What software can we expect to be available the the platform is released?
And will it have an ethernet port darnit?
Interesting situation. AT&T bought up MediaOne. MediaOne wanted to get brodband every where it could, but local telcos didn't want to lay fiber. MediaOne decided to screw waiting for the telcos to get off their lazy asses ( US West is now Quest! ) and lay the fiber themselves. First they fired up digital calbe, shortly followed by two-way cable, taking a big dent out of US West (is now Quest!)'s DSL market.
MediaOne planned on offering telephone serverice over their newly laid fiber as well, and since AT&T bought them, I'm sure that hasn't changed.
Now the really interesting part. Internet access. MediaOne and TimeWarner both offer the same service, Road Runner. I belive this service is a MediaOne spawn, so I'm sure AT&T isn't incredibly happy having to share with TimeWarner, but I like Time Warner's flavor of Road Runner, as I have yet to hit a limit of dynamic IP's I can pull.
That's a breif and under-informed summery of the Minneapolis/St. Paul metro...
Simple enough. task-packages are just empty packages. No content at all. All a task package is is a debian package that depends on a bunch of related packages, and suggest others.
That way, you can type apt-get install task-gnome task-samba task-c-dev etc, and apt will download and install that selection of packages.
When using dselect with task-packages, I've found it best to select the task packages (+) to bring up the depends selection, then set the task package to purge (_), but keep the packages that the task package depended on. You may want to keep the task package installed so if something is added to that task, you're next apt-get upgrade will grab that package as well. On the otherhand, if you don't want something that's in a task-package, dselect will complain because the task-package depends on that package.
It's not a big deal with stable, since the only task packages that will be updated are those from helix and other non-offical packages.
Looks like TDYC allready has it packed up and ready for apt. The apt source is:
deb ftp://kde.tdyc.com/pub/kde/debian unstable kde2
Do an apt-get update, then apt-get install task-kde and you're ready to go.
Enjoy. I've been running the kooldown release awile now, so far I like it. Startup is a bit slower than GNOME though. Wonder if that's changed in the latest version...
*Sometimes* makefiles have a make uninstall option. But that is a slight flaw in the nature of package managment, if there isn't an actual package, things could get messy.
/usr/local/stow and type stow package-name, and stow creates symlinks in /usr/local. Slick. To remove, stow -D package-name, rm -rf /usr/local/stop/package-name
I personally use stow to manage software that isn't part of the distribution. When compiling, --prefix=/usr/local/stow/package-name then build as normal. When it's done, cd to
AOL has a "monopoly" on the instant messaging market. In other words, they can and will stifle future development of IM products BECAUSE they dominate.
I don't know that they have a monopoly. If they do, they're not trying to use said monopoly to stifle competition in the IM market. There's ICQ, MSN, Yahoo, Excite, Jabber, Everybody, well, the list goes on. AOL wasn't even the first on the scene. Yes you could IM another AOL user before AIM, but ICQ beat AIM to the internet crowd. Really, AOL should make a big stink about it. AIM is just an internet enabled version of the IM protocol they developed. No one has rights to all their hard work. AOL is nice enough to let the Open Source community use the service they built from the ground up.
I'd be very dissapointed if they did block out 3rd party clients, but it wouldn't be the end of the world. If all esle fails, there is IRC. So please, don't go around saying AOL has a Monopoly when they really don't. They are the "number one" online service provider, and they bundle their IM software in their package. No wonder they have most of the market share. But I still don't see any evidence of abuse of monopoly power. Remember, it isn't the monopoly itself that illeagal, it's the use of the monopoly to stifle competition.
...if we can find a transmitter that isn't charred beyond all recongition, just like our cosmonaut riding up on your missle...errr...rocket."