99% of the posts that aren't forced to have one because they don't reply to anything just keep the "Re:" subject line that Slashdot fills in for them. Using them as a rhetorical device to split one part of your post from the rest is basically their main function.
There is even a school of thought that the command line is easier for new computer users. It's very hard to judge what life is like for a new computer user when you (and most other people around you) are already experienced with Windows.
Re:I predict "R" apps will be susceptible to pirac
on
R In a Nutshell
·
· Score: 1
I mean, how can they resist?
"R" is resistance, so R apps should be able to resist just fine.
Well, to be fair, the statements about Windows and Fedora weren't really criticism, they were jokes playing to the common meme of Windows being insecure and the far less common meme of Fedora being insecure (that's why the Fedora joke got modded troll until someone came along and yelled at the mods).
On some login systems, the computer will check password characters one at a time, and kick back a "login failed" message as soon as it spots a bad character in the password.
Why the hell are they checking against the password in plaintext, and not some kind of hash?
50,000 applications vs 250,000 applications doesn't really matter. In both cases, it's enough to cover basically everything you'll need, and many applications are redundant copies of each other. Apple's 250k is in fact worse because Apple's policies prevent certain kinds of applications from being made at all. Android has multiple music players for it, the iPhone has just the one Apple makes. Android has applications with political and/or sexual content, the iPhone has practically none.
And, oh, BTW, HERE's what your precious "Freedom ton install any software you want" vs. "all apps have to be approved and bought from an Apple App Store" REALLY buys you. That is not a theory, it is fact.
Something about temporary safety over essential liberty and deserving neither comes to mind...
TRUE "Liberty" would mean that I could hunt you down and kill you for not agreeing with me.
What part of "you can do whatever you want as long as you don't infringe on anyone else's right to do the same" don't you understand?
And Slashdot. With the slashing and dotting, it sounds like an MMORPG. Well, with the achievements system and the karma system and the friends/foes system, Slashdot basically is an MMORPG.
Sometimes I think the whole draconian copyright thing is a trick by the EFF to get people to develop darknets which will then also be used for human rights purposes by third world dissidents. It has to be - there's just no way anyone can actually be this stupid.
The term MMO doesn't just mean that it's multiplayer and there are lots of players, it also implies that there's a persistent world and players spend all their time in it. You can have that kind of game with as little as a few hundred players.
There are about 30 million teenagers (using the strict definition of 13-19 here) in the US. They also have a disproportionately loud voice because they're more likely to have internet access and lots of spare time. Teenagers are a very powerful social force indeed, and they should not be underestimated.
There is strong corporate backing behind open source software. For example, about 75% of Linux is written by corporations. The same arguments they use (basically, if we put stuff out there, we can benefit from others building on it and publishing their improvements) should also apply to hardware.
Looks like it's getting a slashdotting, so here you go:
Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!
Introduction
Open Source Hardware (OSHW) is a term for tangible artifacts -- machines, devices, or other physical things -- whose design has been released to the public in such a way that anyone can make, modify, distribute, and use those things. This definition is intended to help provide guidelines for the development and evaluation of licenses for Open Source Hardware.
It is important to note that hardware is different from software in that physical resources must always be committed for the creation of physical goods. Accordingly, persons or companies producing items ("products") under an OSHW license have an obligation not to imply that such products are manufactured, sold, warrantied, or otherwise sanctioned by the original designer and also not to make use of any trademarks owned by the original designer.
The distribution terms of Open Source Hardware must comply with the following criteria:
1. Documentation
The hardware must be released with documentation including design files, and must allow modification and distribution of the design files. Where documentation is not furnished with the physical product, there must be a well-publicized means of obtaining this documentation for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The documentation must include design files in the preferred form for which a hardware developer would modify the design. Deliberately obfuscated design files are not allowed. Intermediate forms analogous to compiled computer code -- such as printer-ready copper artwork from a CAD program -- are not allowed as substitutes.
2. Necessary Software
If the hardware requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the documentation requirement must also include at least one of the following: The necessary software, released under an OSI-approved open source license, or other sufficient documentation such that it could reasonably be considered straightforward to write open source software that allows the device to operate properly and fulfill its essential functions.
3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original hardware. The license must allow for the manufacture, sale, distribution, and use of products created from the design files or derivatives of the design files.
4. Free redistribution
The license shall not restrict any party from selling or giving away the project documentation as a component of an aggregate distribution containing designs from several different sources. The license shall not require a royalty or other fee for such sale. The license shall not require any royalty or fee related to the sale of derived works.
5. Attribution
The license may require derived works to provide attribution to the original designer when distributing design files, manufactured products, and/or derivatives thereof. The license may also require derived works to carry a different name or version number from the original design.
6. No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.
7. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used in nuclear research.
8. Distribution of License
The rights attached to the hardware must apply to all to whom the product or documentation is redistributed without the need for execution of an additional license by those parties.
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
OSHW definition, Section 7:
7. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used in nuclear research.
The OSHW definition is a straight copy of the OSS one with a necessary s/program/hardware/g but for some reason the example was changed to refer to nuclear research. Is there any reason behind making this kind of deliberate change, or am I reading between the lines too much?
Slashdot Mirror
So you want people taking out a newspaper-sized map and trying to find where they are while driving?
Having a GPS tell people where to go is safer than the alternatives.
99% of the posts that aren't forced to have one because they don't reply to anything just keep the "Re:" subject line that Slashdot fills in for them. Using them as a rhetorical device to split one part of your post from the rest is basically their main function.
Sting operation?
Yet another potential source of useful intelligence shut down.
There is even a school of thought that the command line is easier for new computer users. It's very hard to judge what life is like for a new computer user when you (and most other people around you) are already experienced with Windows.
I mean, how can they resist?
"R" is resistance, so R apps should be able to resist just fine.
I've put splinters in. Without anesthetic, because I am a warrior.
Normal games but where you have to keep the laptop charged with pedal power.
One Ring LAN to rule them all and in the darkness bind them?
Well, to be fair, the statements about Windows and Fedora weren't really criticism, they were jokes playing to the common meme of Windows being insecure and the far less common meme of Fedora being insecure (that's why the Fedora joke got modded troll until someone came along and yelled at the mods).
Motorola doesn't have much of a monopoly to leverage.
Oh quit w(h)ining already.
On some login systems, the computer will check password characters one at a time, and kick back a "login failed" message as soon as it spots a bad character in the password.
Why the hell are they checking against the password in plaintext, and not some kind of hash?
50,000 applications vs 250,000 applications doesn't really matter. In both cases, it's enough to cover basically everything you'll need, and many applications are redundant copies of each other. Apple's 250k is in fact worse because Apple's policies prevent certain kinds of applications from being made at all. Android has multiple music players for it, the iPhone has just the one Apple makes. Android has applications with political and/or sexual content, the iPhone has practically none.
And, oh, BTW, HERE's what your precious "Freedom ton install any software you want" vs. "all apps have to be approved and bought from an Apple App Store" REALLY buys you. That is not a theory, it is fact.
Something about temporary safety over essential liberty and deserving neither comes to mind...
TRUE "Liberty" would mean that I could hunt you down and kill you for not agreeing with me.
What part of "you can do whatever you want as long as you don't infringe on anyone else's right to do the same" don't you understand?
And Slashdot. With the slashing and dotting, it sounds like an MMORPG. Well, with the achievements system and the karma system and the friends/foes system, Slashdot basically is an MMORPG.
Sometimes I think the whole draconian copyright thing is a trick by the EFF to get people to develop darknets which will then also be used for human rights purposes by third world dissidents. It has to be - there's just no way anyone can actually be this stupid.
Correct, it's "squid0". Now shut up and be glad it's not "Robert'); DROP TABLE Students;--".
Why did you waste time putting something in the comment box? Your sig would have made a perfectly good and insightful post here by itself.
The term MMO doesn't just mean that it's multiplayer and there are lots of players, it also implies that there's a persistent world and players spend all their time in it. You can have that kind of game with as little as a few hundred players.
There are about 30 million teenagers (using the strict definition of 13-19 here) in the US. They also have a disproportionately loud voice because they're more likely to have internet access and lots of spare time. Teenagers are a very powerful social force indeed, and they should not be underestimated.
There is strong corporate backing behind open source software. For example, about 75% of Linux is written by corporations. The same arguments they use (basically, if we put stuff out there, we can benefit from others building on it and publishing their improvements) should also apply to hardware.
Looks like it's getting a slashdotting, so here you go:
Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!
Introduction
Open Source Hardware (OSHW) is a term for tangible artifacts -- machines, devices, or other physical things -- whose design has been released to the public in such a way that anyone can make, modify, distribute, and use those things. This definition is intended to help provide guidelines for the development and evaluation of licenses for Open Source Hardware.
It is important to note that hardware is different from software in that physical resources must always be committed for the creation of physical goods. Accordingly, persons or companies producing items ("products") under an OSHW license have an obligation not to imply that such products are manufactured, sold, warrantied, or otherwise sanctioned by the original designer and also not to make use of any trademarks owned by the original designer.
The distribution terms of Open Source Hardware must comply with the following criteria:
1. Documentation
The hardware must be released with documentation including design files, and must allow modification and distribution of the design files. Where documentation is not furnished with the physical product, there must be a well-publicized means of obtaining this documentation for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The documentation must include design files in the preferred form for which a hardware developer would modify the design. Deliberately obfuscated design files are not allowed. Intermediate forms analogous to compiled computer code -- such as printer-ready copper artwork from a CAD program -- are not allowed as substitutes.
2. Necessary Software
If the hardware requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the documentation requirement must also include at least one of the following: The necessary software, released under an OSI-approved open source license, or other sufficient documentation such that it could reasonably be considered straightforward to write open source software that allows the device to operate properly and fulfill its essential functions.
3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original hardware. The license must allow for the manufacture, sale, distribution, and use of products created from the design files or derivatives of the design files.
4. Free redistribution
The license shall not restrict any party from selling or giving away the project documentation as a component of an aggregate distribution containing designs from several different sources. The license shall not require a royalty or other fee for such sale. The license shall not require any royalty or fee related to the sale of derived works.
5. Attribution
The license may require derived works to provide attribution to the original designer when distributing design files, manufactured products, and/or derivatives thereof. The license may also require derived works to carry a different name or version number from the original design.
6. No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.
7. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used in nuclear research.
8. Distribution of License
The rights attached to the hardware must apply to all to whom the product or documentation is redistributed without the need for execution of an additional license by those parties.
OSS definition, Section 6:
6. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
OSHW definition, Section 7:
7. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used in nuclear research.
The OSHW definition is a straight copy of the OSS one with a necessary s/program/hardware/g but for some reason the example was changed to refer to nuclear research. Is there any reason behind making this kind of deliberate change, or am I reading between the lines too much?
And if the loan shark had lasers?
I was a dork, but no one dared fuck with me
I'm confused. Is this good or bad?