But assuming they won't and you can't, try to put incentives in place to keep RTFM calls down.
If you get a question that you find has already been answered in the company intranet, than you should get paid $30 and that $30 comes from the other person's department.
Clearly, Napster's value to their investors is their large population of consumers. Us. And so clearly, Napster's valuation will be affected by the size of that population. Us.
So send a message to Napster that their management and investors will understand, a message that will affect their valuation by making it clear they do not own Us, and that we can move to Gnutella, or Napster++,
Napsterfree Mondays until they GPL their software.
When Bob submits a fix for BeOs, Carol submits a fix for AIX, Ted submits a fix for VxWorks, and Alice submits one for the Mac, well, how do you test it all prior to release?
Can you trust your alpha and beta testers to find enough bugs to release?
And what can you do when your outside community of testers is still small and you know they really aren't sufficient for the job?
Must your company get testers for all of these platforms?
When Paul submits a new feature for the Amiga, does that mean someone needs to provide code for Linux before you can release?
I don't think that asking people to not deep link will lead to death of the web. Why are people offended by being prevented from deep linking, but not offended by sites that require registration, or subscriptions? Look at what's happening at Slate and The Street and let the consumer decide.
That said, if you want to make your site navigatable but unlinkable, why not:
Determine which pages can be linked to from outside. Call this class O.
Determine which pages can only be linked to from inside. Call this class I.
Have every page set the cookie to their class: I or O.
If you are asked for an I page, don't return it unless the cookie says the person came from an I page. Otherwise redirect to the homepage.
Slashdot Mirror
Well they should pay you more or you should quit.
But assuming they won't and you can't, try to put incentives in place to keep RTFM calls down.
If you get a question that you find has already been answered in the company intranet, than you should get paid $30 and that $30 comes from the other person's department.
Clearly, Napster's value to their investors is their large population of consumers. Us. And so clearly, Napster's valuation will be affected by the size of that population. Us.
So send a message to Napster that their management and investors will understand, a message that will affect their valuation by making it clear they do not own Us, and that we can move to Gnutella, or Napster++,
Napsterfree Mondays until they GPL their software.
What we need now, is a colored-ribbon campaign...
When Bob submits a fix for BeOs, Carol submits a fix for AIX, Ted submits a fix for VxWorks, and Alice submits one for the Mac, well, how do you test it all prior to release?
Must your company get testers for all of these platforms?
When Paul submits a new feature for the Amiga, does that mean someone needs to provide code for Linux before you can release?
I don't think that asking people to not deep link will lead to death of the web. Why are people offended by being prevented from deep linking, but not offended by sites that require registration, or subscriptions? Look at what's happening at Slate and The Street and let the consumer decide.
That said, if you want to make your site navigatable but unlinkable, why not:
Determine which pages can be linked to from outside. Call this class O.
Determine which pages can only be linked to from inside. Call this class I.
Have every page set the cookie to their class: I or O.
If you are asked for an I page, don't return it unless the cookie says the person came from an I page. Otherwise redirect to the homepage.