IRC is often used for community support for a product, much like Usenet. Debian used to have a really good IRC support channel, but it's since become hostile to new users.
IRC is often a great place to ask obscure questions, where if you ask on Usenet, you're often a lone voice in the world.
The idea of searchable IRC logs kindof scares me. An investigative team need only go to Google to search for discussions by someone with the nickname "l33t".
Of course, IRC logs are already out there, often made available by the denizens in charge of the channel in question. But they're not hooked up to a common database.
The speed of information dissemination is great for research and development, but that applies to both you, and people who want to learn about you.
I've mentioned several times on IRC that I have a brain disorder (Asperger's syndrome, specifically), but I may have been operating under the assumption that the information wasn't important enough to be spread around to twenty or thirty Googleable sites. To be honest, I don't care who knows, which is why I'm saying it here.
Calm down, man. It was a literary reference. In "Moonwar", the only colony on the moon was attacked because all the countries on Earth had banned nanotechnology (From unjustified paranoia), and the leaders of the planet were pissed that the moon colony was still using it.
It's a good book. Now, if I could only find a link to "Moonbase", the first book of the duo, I'd have posted that.
Ah, but you're ignoring the fringe benefits. All of the technology that we'll have to develop to get there. Sure, we invented stuff like Velcro and mylar to get to the moon the first time, but that was to support a different set of requirements. Considering that we're going there with different intentions, I suspect we're going to have to come up with new technologies.
And that's not to mention the fact that we need to do it on a smaller budget. A lot of the research is going to have to be on minimizing costs without compromising safety. Spinoffs from that process are going to have major boosting effects on the economy.
Re:Minor factual error: no "darkside" of the moon
on
The Case for the Moon
·
· Score: 1
Don't forget radio telescopes. As large as you want, without interference from Earth.
I'm sorry for him. If he at least appeared neutral, he'd be more likely to get campaign funds from Microsoft and other BSA members, who are some pretty damn big players in the funding game.
Though he might get IBM and Red Hat to support him.:)
On the bright side, it shouldn't be hard to search for, as far as OSS projects go. Especially if those projects are accessible via a web-CVS portal; Google caches those, I think.
No sysadmin appreciates being cracked. Some sysadmins appreciate the effect the threat has on keeping their admin habits safe. More sysadmins and developers appreciate the effect the threat has on the development quality of the software they use. (Topical vendor not included).
I'd rather have a bunch of virus writers out there trying to crack my system all the time, helping me keep my code more secure, then have an insecure system where a spontaneous malicious attacker can ruin it.
Existing legislation might be easy to enforce with this...they have to be within Bluetooth range of you to send you a message, and Bluetooth range, for most people, doesn't include foreign countries.
RPMs are still around, and are supported by virtually all distros (inclding those that normally run on DEBs)...Distributing drivers as RPMs is still a good option, and will reach the majority of Linux desktop users.
For those companies that still aren't sure, set up a fund (sort of like a PAC) to fund the development of a driver in-house by the manufacturer. (Closed source or not doesn't matter. What matters is that the driver is there.)
Sure, it'll overwrite your XConfig, if you tell it to. It always says "/etc/X11/XF86Config-4: This file modified by you or a script. Install package maintainter's version or retain old version?"
Don't say "yes" to every prompt you see.:)
And if it asks you to type "Yes, I know what I'm doing" character for character, be damn sure you know what you're doing.
I think it was in 2000 or 2001, the Perl packages in Unstable broke, which broke everything, including the package manager and installer. Being new to Linux then, I ran home to Potato(then stable, now obsolete, though the floppy install images are a must if you want to install on a laptop), and then went back to Woody (then testing, now stable). Now I'm happily running Sid(Unstable). Even on a 1.5Mbit/s PRI, I still have an hour minutes of updated software to download every week.
I've got a second machine coming that I'm going to use to run Stable or Testing (not sure which), and I'll just use the Unstable machine as a remote X app server.
A lot of artists have contracts with their record label that prevents them from selling their music through any other source. (Heck...most authors end up having their work owned by their distributor) The online download services almost certainly have contracts with the labels to get permission to resell their music.
Because an X replacement is a lot more trouble than it's worth. The X system is designed to be extensible, and it's worked pretty damn well, so far. It's by far the most flexible solution I've seen.
Slashdot Mirror
A powerful...female...cluster?! ...
Still way too young, though.
IRC is often used for community support for a product, much like Usenet. Debian used to have a really good IRC support channel, but it's since become hostile to new users.
IRC is often a great place to ask obscure questions, where if you ask on Usenet, you're often a lone voice in the world.
The idea of searchable IRC logs kindof scares me. An investigative team need only go to Google to search for discussions by someone with the nickname "l33t".
Of course, IRC logs are already out there, often made available by the denizens in charge of the channel in question. But they're not hooked up to a common database.
The speed of information dissemination is great for research and development, but that applies to both you, and people who want to learn about you.
I've mentioned several times on IRC that I have a brain disorder (Asperger's syndrome, specifically), but I may have been operating under the assumption that the information wasn't important enough to be spread around to twenty or thirty Googleable sites. To be honest, I don't care who knows, which is why I'm saying it here.
Would you mind putting out a writup on how you did it? Maybe even to the extent of a mini-HOWTO?
Something as simple as a package list would probably help a lot of people.
Calm down, man. It was a literary reference. In "Moonwar", the only colony on the moon was attacked because all the countries on Earth had banned nanotechnology (From unjustified paranoia), and the leaders of the planet were pissed that the moon colony was still using it.
It's a good book. Now, if I could only find a link to "Moonbase", the first book of the duo, I'd have posted that.
Here's an idea: Nanomachines.
Dual Xeon workstations don't come cheap. If they were less expensive, I'm sure the average Slashdotter would show more interest.
But I'd still rather have a dual Athlon64.
Ah, but you're ignoring the fringe benefits. All of the technology that we'll have to develop to get there. Sure, we invented stuff like Velcro and mylar to get to the moon the first time, but that was to support a different set of requirements. Considering that we're going there with different intentions, I suspect we're going to have to come up with new technologies.
And that's not to mention the fact that we need to do it on a smaller budget. A lot of the research is going to have to be on minimizing costs without compromising safety. Spinoffs from that process are going to have major boosting effects on the economy.
Don't forget radio telescopes. As large as you want, without interference from Earth.
Somehow, I don't think the Kama Sutra would have any instructions for that scenario...
It was also supposed to be a tip-of-the-hat to the Dancing Baby. :)
I'm sorry for him. If he at least appeared neutral, he'd be more likely to get campaign funds from Microsoft and other BSA members, who are some pretty damn big players in the funding game.
:)
Though he might get IBM and Red Hat to support him.
Hey, Baby. Wanna dance? (ducks)
On the bright side, it shouldn't be hard to search for, as far as OSS projects go. Especially if those projects are accessible via a web-CVS portal; Google caches those, I think.
Sure, a hat store without much variety. :)
Nothing helps us understand (and possibly predict) the future than being familiar with our past.
No sysadmin appreciates being cracked. Some sysadmins appreciate the effect the threat has on keeping their admin habits safe. More sysadmins and developers appreciate the effect the threat has on the development quality of the software they use. (Topical vendor not included).
I'd rather have a bunch of virus writers out there trying to crack my system all the time, helping me keep my code more secure, then have an insecure system where a spontaneous malicious attacker can ruin it.
That development in their business model isn't far past "wait for someone else to invent, then copy and integrate" ...
Existing legislation might be easy to enforce with this...they have to be within Bluetooth range of you to send you a message, and Bluetooth range, for most people, doesn't include foreign countries.
RPMs are still around, and are supported by virtually all distros (inclding those that normally run on DEBs)...Distributing drivers as RPMs is still a good option, and will reach the majority of Linux desktop users.
For those companies that still aren't sure, set up a fund (sort of like a PAC) to fund the development of a driver in-house by the manufacturer. (Closed source or not doesn't matter. What matters is that the driver is there.)
Sure, it'll overwrite your XConfig, if you tell it to. It always says "/etc/X11/XF86Config-4: This file modified by you or a script. Install package maintainter's version or retain old version?"
:)
Don't say "yes" to every prompt you see.
And if it asks you to type "Yes, I know what I'm doing" character for character, be damn sure you know what you're doing.
I think it was in 2000 or 2001, the Perl packages in Unstable broke, which broke everything, including the package manager and installer. Being new to Linux then, I ran home to Potato(then stable, now obsolete, though the floppy install images are a must if you want to install on a laptop), and then went back to Woody (then testing, now stable). Now I'm happily running Sid(Unstable). Even on a 1.5Mbit/s PRI, I still have an hour minutes of updated software to download every week.
I've got a second machine coming that I'm going to use to run Stable or Testing (not sure which), and I'll just use the Unstable machine as a remote X app server.
A lot of artists have contracts with their record label that prevents them from selling their music through any other source. (Heck...most authors end up having their work owned by their distributor) The online download services almost certainly have contracts with the labels to get permission to resell their music.
What are the licensing restrictions for copying code into the XFree86 codebase? BSD code is obviously fine, while GPL and LGPL code obviously is not.
What common licenses can code be copied from?
Because an X replacement is a lot more trouble than it's worth. The X system is designed to be extensible, and it's worked pretty damn well, so far. It's by far the most flexible solution I've seen.