Hacker News new | comments | show | ask | jobs | submit login

My little cousin decided it and I didn't have the heart to break his...

I sympathize, but at least use a variant on it. Picking that name and logo for an HTTP request library with Ruby and Python bindings is extremely bad form given that there's an existing HTTP server project that uses that name and is associated with that logo.

Yes, I think I will be giving him some bad news today unfortunately.

How about changing it to "Unicrest", as a play on unicorn/request?

So rather than taking the opportunity to provide a lesson on project naming, you've let him think that it's a perfectly valid name. Now an entire development community is about to shoot down the project because you wanted to play the nice guy. How cruel!

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact