To clarify: (1) Your scenario = don't trademark, use open source license. (2) What Mozilla does = trademark, use proprietary license. (3) What Mark thinks should be done (afaiu) = trademark, use open source license.
I don't know a good way to reduce the impact in scenario (1) through legal means, but if you are worried about this, why not choose scenario (3)?
That makes so much sense. I thought you might be pulling the e-mails out of the applications manually, and having coded and used a system for processing submissions (to an online fiction magazine), I was wondering how the hell you could stand to do that for 500+ applications. Glad to hear you're keeping yourself sane ;-)
The thing that struck me as really useful was the way you could use the slides to get an overview of and jump around inside a presentation. For me, that looks like a killer feature that could make me want to watch presentation videos through your viewer.
Except that the thumbnails of the slides are just too small to actually read. To make them useful for me for scanning the presentation without watching it all, I believe they would have to be big enough that the text is legible.
I've had the same reaction as boris when reading the original quote. But what he was talking about was the case where someone turns them down because of the valuation. And I can see Paul's point there, actually.
On the other hand, my understanding is that they've been hard at work since their original announcement, figuring out how their program is going to work legally and organizationally. Being willing to set themselves a tight schedule when necessary and being able to meet it might not be such a bad thing for a startup investor. :-)
I suppose I took PB's post more broadly than it was intended, then. If he was only talking about solving hard problems that don't benefit the user proportionally, I see that there's no contradiction [and have a clear answer to the question of when to follow which advice ;-)].
That made a lot of sense to me. But on the other hand, pg's "How to Make Wealth" makes a good argument for precisely the opposite view:
"Use difficulty as a guide not just in selecting the overall aim of your company, but also at decision points along the way. At Viaweb one of our rules of thumb was run upstairs. Suppose you are a little, nimble guy being chased by a big, fat, bully. You open a door and find yourself in a staircase. Do you go up or down? I say up. The bully can probably run downstairs as fast as you can. Going upstairs his bulk will be more of a disadvantage. Running upstairs is hard for you but even harder for him. What this meant in practice was that we deliberately sought hard problems. If there were two features we could add to our software, both equally valuable in proportion to their difficulty, we'd always take the harder one."
Of course, no piece of general advice is right in all cases. But what should you look for, in a given situation, to know whether it's better to seek out the hard problems or better to avoid them?
"The survey did not ask where the respondents obtained the content, ignoring the reality that many were possibly downloading television shows from Bittorrent or similar services."
To me, it sound like a good idea not to ask that, if you want honest responses.
Who are you? Metalab has an extensive website, but who's behind YEurope? You know that the funding is only a small part of what YC provides -- you won't be able to live up to pg, rtm et al, which is expected, but right now you don't say anything about yourself, so why should a prospective applicant value your connections and advice?
And: One of the things YC does is that it sets up a company for you. YEurope is in Austria. Austria is a country where it's expensive to incorporate (pg has written about how that is one problem for startups in Europe [1]). What are you going to do about that?
What I'd like to see is companies hiring lawyers who spend their surplus time blogging. Being involved in the community should prevent them from being as seriously out of tune as this, and if they spend some of their time explaining tech law to the unenlightened (like me), that'll reflect back on the company.
Your point is that news.yc and other social news sites are actually more useful when more people use them, right? I agree with that. But IMHO, that's missing the point of the article.
Music doesn't objectively get better just because more people listen to it; and yet, the authors' research appears to show that people's opinions of music is hugely influenced by what other people like. Recall their main result: They had one group of users who they didn't show any information about how often a song was downloaded, and then eight independent groups who were shown the download count of each song inside that group. "The song 'Lockdown,' by 52metro, for example, ranked 26th out of 48 in [the group not shown download counts]; yet it was the No. 1 song in one social-influence world, and 40th in another. Overall, a song in the Top 5 in [the group not shown counts] had only a 50 percent chance of finishing in the Top 5 of success." Their conclusion is that the reason why predicting the success of media products is shaky is that what's a success is hugely influenced by an unpredictable feedback process.
Thus, my question: Can we assume that Google's success is due in a large part not to anything that Google did, but to the (random) feedback process of people liking Google because they see other people liking Google?
Of course, one could argue that this is simply the truism that one needs luck as well as talent to succeed. But I come away from reading the article with the feeling that I've learned something that goes deeper than that, and I'm trying to figure out how to apply it to the tech world.
Hey, death threats aren't funny, and being afraid of a death threat is something very different from being afraid that taking a stance might hurt your bottom line.
Well, I haven't read everything on their site, so I don't understand all the details and I may have misconceptions, but my understanding is this: In the physical world, to prove that you have a driver's license or a valid credit card or that you are over 13 years old, you need to show a credential that also gives away additional information about you. In their system, the government or bank can issue a cryptographic credential to the user which tells the service provider only the information they actually need to know, and does this through a zero-knowledge proof, so that the provider can't link multiple uses of the same credential to the same user.
The "incomprehensible marketing speak" line was aimed at the non-research IBM web pages I've seen, btw, not at Ars Technica :-) ("Delivers a rich, relevant customer and partner experience by extending a common set of business services across every point of interaction" and such.)
Looks like it's an IBM Research project, which is nice because it means they give you actual technical information rather than burying you in incomprehensible marketing speak.
I don't know a good way to reduce the impact in scenario (1) through legal means, but if you are worried about this, why not choose scenario (3)?