If you had RTFA, you would know that this is not a Single Signon. It is a Set Of Single Signons. You can have as many identities as you want. The difference is that without something like this, you are forced to have one identity per site, or one Passport ID. With an openID implementation, you can have any number of accounts as fit your needs. One potentially useful scheme is to have one signon for blogs and news sites, and then individual identities for each bank/etc.
You are confusing Authentication with Authorisation. Authentication is proving that You Are Who You Say You Are, i.e. the purpose of systems like OpenID. Your cookies/etc would be involved with Authorisation instead, deciding what that person is allowed to do on your site.
Of course, if a central signon system doesn't work for you, then don't use it.
Agreed; in a true free market, there is no such thing as copyright, and the content producers would be fully responsible for copy-protecting their own work, without any laws to back them up. At which point, consumers would quickly flock to the non-crippled products, as they are a better value for the paid price. (all theoretically, of course).
so? OSX has a very nice graphics architecture with lots of potential. X11 is old and crufty, and these sorts of effects require large portions of code to be rewritten. If it can suddently render a genie effect efficiently, imagine how quick it'll be to render more mundane windows!
a CMS manages content. It's basically a framework that takes care of the boring repetive details of writing a content-driven website; these include getting data from other pages, getting/saving properties/attributes of web 'objects', and slapping templates on everything. In general, they are used so that non-techies can upload content, so the techies can spend more time on useful hacking.
From what I can tell, Bricolage is fairly similar to Zope.
Some people consider the exercise and protection of their rights to be more important than increasing stockholder payouts. Never mind that he's a *canadian* professor (and thus it's not coming out of US pockets), attending a professional conference on exactly this topic.
There's not much to discuss. If they have most of the marketshare due to having a good product, it's not a monopoly, it's just a very successful product. Monopolies are only bad when they are illegally maintained.
Re:It's as if icons peaked 2-4 years ago
on
A History of Icons
·
· Score: 1
Decent(recent?) apps tend to have tooltips that pop up when you point at the icons. It makes it considerably less painful to use such GUIs. Tooltips should really be required by all interface guidelines. As a bonus, if the programmer has to think of a nice short tooltip, they might manage to think of a better icon while they're at it.
Re:It's as if icons peaked 2-4 years ago
on
A History of Icons
·
· Score: 1
Really? Hmm.
[Help | Kopete handbook] (or hit F1)...
Table of Contents 1. Introduction 2. Getting Started 3. Using Kopete 4. Configuring Kopete...
I'm not sure what apps you're using , but my KDE apps certainly have excellent documentation available through the help menu. I actually use it once in a while, as opposed to windows apps where I know there will be nothing useful and don't even bother trying.
Why don't you get right on that and submit your proposal as an RFC instead of just whining. We already *know* it's flawed. Unlike yourself, IBM and others are actually trying to do something about it.
If I get a machine calling me, I hang up right away. IF they really want to talk to me, they can pay a real person to do so. It's still a hassle to answer in the first place, of course./me looks into the status of canada's do-not-call-list...
Again, that's what the nice, standard Filesystem Hierarchy is for. All of the major distros support it to some extent and are moving closer to supporting it fully all the time.
I agree; that was some of the worst FUD I've ever read, and it doesn't even deserve a response. It sounds like a six year old repeating some things he heard from the big boys; at least MS hires professionals to say this sort of thing.
regedit32 winipcfg cmd.com outlook (so, it lets me look at things?) access (*What* does it?) excel (it's good at something, but what?) powerpoint NTFS FAT32 IIS
And that's just the ones made by microsoft, that I can think of off the top of my head. You can spend millions to come up with a shitty non-descriptive name, or you can spend that money making a good product.
FOSS *is* catching on, as companies that use the better products beat out those that purchase software based on the name.
Let's try that again:
"Guns don't kill people, people kill people, and monkeys do too (if they have a gun)." --Eddie Izzard
Give a monkey an unloaded gun, and no one is going to get shot. Same goes for people, even if they consciously pull the trigger. Take russian roulette; the person doesn't *know* there's a bullet in the chamber, they still pull the trigger. But without a bullet, nobody dies. While a bullet on its own won't kill, it is the only truly necessary object involved in a shooting.
I think the reason no one ever refutes your idea is because it is complete bunk; OSS will *never* have one unified anything; not a window manager, not an email client, not an IDE, not an API. OSS develops to standards, not to monopolies. So long as they mostly agree on how things should work, we can have many disparate apps working together happily.
That's why there is the Filesystem Hierarchy Standard, which is being followed by most bug distros: http://www.debian.org/doc/packaging-manuals/fhs/
On my debian system, if I want to find documentation for J Random Package, I look in the standard place. If I want the config files, I know where to look. What good is cross-distro consistency if everything within the distro is randomly distributed? (was the apache config file under/usr/local/www or/usr/local/etc/apache or/var/www/etc or...)
Slashdot Mirror
If you read his comment carefully, he said that weeds are legal, with no mention of drugs.
Though he's still technically wrong, as there are fines for having Scentless Chamomile growing in your ditch if you're a farmer.
Just another useless fact that I know instead of anything marketable.
If you had RTFA, you would know that this is not a
Single Signon. It is a Set Of Single Signons. You can have as many identities as you want. The difference is that without something like this, you are forced to have one identity per site, or one Passport ID. With an openID implementation, you can have any number of accounts as fit your needs. One potentially useful scheme is to have one signon for blogs and news sites, and then individual identities for each bank/etc.
You are confusing Authentication with Authorisation. Authentication is proving that You Are Who You Say You Are, i.e. the purpose of systems like OpenID. Your cookies/etc would be involved with Authorisation instead, deciding what that person is allowed to do on your site.
Of course, if a central signon system doesn't work for you, then don't use it.
The arctic ocean, of course! Everyone knows that canada is over the north pole with those commie bastards! (mods: this is a joke)
Agreed; in a true free market, there is no such thing as copyright, and the content producers would be fully responsible for copy-protecting their own work, without any laws to back them up. At which point, consumers would quickly flock to the non-crippled products, as they are a better value for the paid price. (all theoretically, of course).
so? OSX has a very nice graphics architecture with lots of potential. X11 is old and crufty, and these sorts of effects require large portions of code to be rewritten. If it can suddently render a genie effect efficiently, imagine how quick it'll be to render more mundane windows!
a CMS manages content. It's basically a framework that takes care of the boring repetive details of writing a content-driven website; these include getting data from other pages, getting/saving properties/attributes of web 'objects', and slapping templates on everything. In general, they are used so that non-techies can upload content, so the techies can spend more time on useful hacking.
From what I can tell, Bricolage is fairly similar to Zope.
Some people consider the exercise and protection of their rights to be more important than increasing stockholder payouts. Never mind that he's a *canadian* professor (and thus it's not coming out of US pockets), attending a professional conference on exactly this topic.
There's not much to discuss. If they have most of the marketshare due to having a good product, it's not a monopoly, it's just a very successful product. Monopolies are only bad when they are illegally maintained.
Decent(recent?) apps tend to have tooltips that pop up when you point at the icons. It makes it considerably less painful to use such GUIs. Tooltips should really be required by all interface guidelines. As a bonus, if the programmer has to think of a nice short tooltip, they might manage to think of a better icon while they're at it.
Really? Hmm.
...
...
[Help | Kopete handbook] (or hit F1)
Table of Contents
1. Introduction
2. Getting Started
3. Using Kopete
4. Configuring Kopete
I'm not sure what apps you're using , but my KDE apps certainly have excellent documentation available through the help menu. I actually use it once in a while, as opposed to windows apps where I know there will be nothing useful and don't even bother trying.
Why don't you get right on that and submit your proposal as an RFC instead of just whining. We already *know* it's flawed. Unlike yourself, IBM and others are actually trying to do something about it.
If I get a machine calling me, I hang up right away. IF they really want to talk to me, they can pay a real person to do so. It's still a hassle to answer in the first place, of course. /me looks into the status of canada's do-not-call-list...
Again, that's what the nice, standard Filesystem Hierarchy is for. All of the major distros support it to some extent and are moving closer to supporting it fully all the time.
"... into different languages..."
And Unix is all greek to me!
I agree; that was some of the worst FUD I've ever read, and it doesn't even deserve a response. It sounds like a six year old repeating some things he heard from the big boys; at least MS hires professionals to say this sort of thing.
Or you can use binary drivers from ATI and have actual hardware acceleration (I'm using a 9600SE).
I think they would notice when they have to keep restarting every half hour because they all died YASD. At which point so would the DM.
Ten minutes with a big enough hammer and you've got gravel. Problem solved.
Point of order: organ donors give their permission before they die.
Shitty names are not limited to OSS:
regedit32
winipcfg
cmd.com
outlook (so, it lets me look at things?)
access (*What* does it?)
excel (it's good at something, but what?)
powerpoint
NTFS
FAT32
IIS
And that's just the ones made by microsoft, that I can think of off the top of my head. You can spend millions to come up with a shitty non-descriptive name, or you can spend that money making a good product.
FOSS *is* catching on, as companies that use the better products beat out those that purchase software based on the name.
Let's try that again: "Guns don't kill people, people kill people, and monkeys do too (if they have a gun)." --Eddie Izzard Give a monkey an unloaded gun, and no one is going to get shot. Same goes for people, even if they consciously pull the trigger. Take russian roulette; the person doesn't *know* there's a bullet in the chamber, they still pull the trigger. But without a bullet, nobody dies. While a bullet on its own won't kill, it is the only truly necessary object involved in a shooting.
Exactly; they get the gun, but it's illegal for them to *use* it without separate permits.
In the US, you can buy bullets at the corner store. Guns don't kill people; bullets do. Which would you rather be closely monitored?
I think the reason no one ever refutes your idea is because it is complete bunk; OSS will *never* have one unified anything; not a window manager, not an email client, not an IDE, not an API. OSS develops to standards, not to monopolies. So long as they mostly agree on how things should work, we can have many disparate apps working together happily.
That's why there is the Filesystem Hierarchy Standard, which is being followed by most bug distros: http://www.debian.org/doc/packaging-manuals/fhs/ On my debian system, if I want to find documentation for J Random Package, I look in the standard place. If I want the config files, I know where to look. What good is cross-distro consistency if everything within the distro is randomly distributed? (was the apache config file under /usr/local/www or /usr/local/etc/apache or /var/www/etc or...)