Hacker News new | ask | show | jobs
by camus2 4501 days ago
Google Music , Google play logo , a project ready from a DMCA takedown ... dont be stupid, remove all the google trademark stuff or your project wont live long in github.
4 comments

I think you have the DMCA confused with trademark law. It may indeed get taken down for legal reasons, but I don't see how the DMCA comes into it.
The image files of the Google logo are copyrighted.
I can understand how this might be legally contentious, but the only thing it could be reported for is the name, I would think? The Google Play logo there is not me embedding it into the app, since it's displaying the webpage itself. Correct me if I'm wrong?
You want to avoid making it look like it's actually "endorsed" by Google, or a product of Google's, despite interop with one of Google's products. The name can be an issue here, so you might want to come up with something spiffier and original, and point out that it works with Google's service elsewhere.
Are they really? I thought logos were squarely in the domain of trademarks.
IANAL, but here's my take: anything men make is copyrighted. Getting rid of that is difficult or even impossible (depending on originating country and one's interpretation of the law)

Nothing physical can be trademarked. It's the idea of some features in a particular field that forms a trademark (in this case, the right-pointing triangle, the phrase "Google Play" in the 'app store' field) you break a trademark as soon as 'the typical consumer' might be confused who he is talking to.

So, the particular logo likely is copyrighted, and the idea behind it trademarked. If you redraw the logo (using some artistic expression; a 1:1 copy won't do), you are free from copyright claims, but may still be breaking trademark law.

It seems like he may be making a play to get this acquired by Google so that they can offer a desktop app. That's why the branding. I can't think of a better way to get Google's attention than to blatantly violate their trademarks - though it might be the legal department, not M&A, that reaches out to him :-)
Google wouldn't need to acquire the project if they wanted a desktop app. It's just a client ... nothing Google engineers couldn't handle.
Right - an embedded webview with some window dressing. But it seems like they don't want to handle it, as they've made clear. So why not shell out a few bucks for one that's already made?
because the first thing they'd do with it is throw away and rewrite it on the Google tech stack.

But this person might land a job at Google, like the Sparrow folks... http://sparrowmailapp.com/

This is seriously just a stylesheet: https://raw.github.com/kbhomes/google-music-mac/master/googl...

That's not an insult, it's supremely awesome that this is even possible and that this dev made it happen. I'm using it now. But there are a few of these types of things for Google Music, there's a similar Chromebook app.

Because they would need to support it. Plus all the other reasons why they don't have a native desktop client now. Like the strategic goal to establish Chrome as an app platform.
Can someone point me to some relevant information on this kind of problems? Like unofficial clients and their legality and pitfalls.
Plus, its ugly with the lego.
Oops, logo.