I'm envisaging scraping colours and fonts from the target domain to recreate a text-only logo.
There are parts of any expertise that are formulaic, and by using the word "parts" I'm being generous to humankind.
Should systems/ops folks be 'offended' that PaaS are becoming the default choice for new projects?
If you DO think they should be offended, then I think you're flat wrong. Being offended by commoditisation is like being angry at entropy, or enraged by gravity.
If you DON'T think they should be offended; why not? Does their job not require thought, or creativity? I'd answer that one carefully if I were you ;)
2) If it isn't I can rapidly prototype my basic ideas and take them to a designer. This is excellent and I'd embrace this as a designer.
The product is still in alpha, but it's amazing how many similarities we came to with the URL scheme design. For example, image embedding:
https://img.ogol.io/<domain.com> example: https://img.ogol.io/ogol.io
we also support downloading
https://dl.ogol.io/<domain.com> example: https://dl.ogol.io/ogol.io
Each logo also has it's own page to make working with the asset outside of an API easy.
https://ogol.io/ogol.io/nn0ymd
Our approach requires companies to confirm their domains and associate a vector logo with the domain. Your strategy obviously provides a lot of logos right out of the gates. Logos are such a pain to deal with, it's great to see the problem being attacked from a few different angles.
0. Change at one place, make it work everywhere. (consistent branding across the wild web).
1. Upload your company logo here with us.
2. Multiple versions.
3. Multiple sizes.
4. Control and Connect various sizes, versions with your various social accounts, newsletters, anything.
5. IFTTT support.
6. Get it printed on swag and merchandise.
7. More...?
Better idea:
1. Take sheet of paper
2. Write down where you use your logo
I wouldn't pay for something like that either. I was suggesting it be offered for free, like gravtaar.
The question is: how much?
Nothing about this API requires handing over more than the bare minimum of information (which domains you want logos for). How could they be expected to implement it without that information?
For this service, if it can find an image, it's at least an image the site owner wanted to be used to represent it.
<meta property="og:image" content="//nebula.wsimg.com/7cdaeb9fbb87f3450dc65108e6d6af87?AccessKeyId=6E4E9B5CC8D37F66F76C&disposition=0&alloworigin=1">
This is pretty sweet. Nice job! Is there a post where you talk about the tech behind this API? I've been working on a simple API that finds domain names from company names that I use on projects where I use business intelligence APIs like Clearbit and FullContact.
https://logo.clearbit.com/spacex.com https://twitter.com/spacex
Maybe other fallbacks, too?
When I saw the tagline "Business Intelligence APIs" at the top of the posted link, I totally thought Clearbit's line of business was something completely different-- more along the lines of data warehousing, analytics and reporting.
Or at least, I feel that would be the case.
<meta property="og:image" content="http://www.exxon.com/assets/imgs/en-us/energy-live-here-facebook.jpg">https://github.com/c0dr/LogoParser
It worked okay for like 40% of the sites, and for the rest of the sites we used Python and scikit-learn to detect the logo from the page (threw all images of the page in the script and it returned if it was a logo or not). And this actually worked quite good, irrc over 90% of the test cases worked.
https://github.com/tomsrocket/image-classification
But yeah, using Twitter as a source might also be a good idea.
You can also pass us the following optional query parameters.
Parameter Default Description
size 128 integer Image size: Length of longest side, in pixels
format "png" string File format, either "png" or "jpg"
greyscale (not passed) boolean If this parameter is passed, image will be desaturatedAny thoughts anyone?
http://www.cs.indiana.edu/pub/faces/picons/
If you've ever noticed the little logos on Gmane posts, they come from Picons and favicons.
https://logo.clearbit.com/h5mag.com from... <img class="logo" src="/img/h5mag-logo.svg" alt="logo H5mag">
Google does something similar for extracting favicons for any domain, such as https://plus.google.com/_/favicon?domain=github.com
https://logo.clearbit.com/alexa.com?size=512
Ideally all your logos should be in vector and rendered to any size (or at least powers of 2 for easier caching).
I made a little hubot script for this: https://www.npmjs.com/package/hubot-logo
Use it like this: hubot logo stripe.com
1. Open-source solutions like KONG (https://github.com/mashape/kong) or similar?
2. Built in house?
3. Commercial services such as Apigee, Mashery?
There's maybe some value in the logo owner being able to get information on who's using their logo (service not yet provided).
From the logo-consumer standpoint, it's pretty cool, though, it would be difficult to know if the logo is current enough.
I tried different logos, and I find a few issues:
https://logo.clearbit.com/mcdonalds.com?size=256
Mcdonalds US logo background should be red (http://www.aboutmcdonalds.com/mcd/newsroom/image_and_video_l... )
https://logo.clearbit.com/bk.com?size=256
The quality of that one is bad. Wikipedia's one is a .svg : https://en.wikipedia.org/wiki/File:Burger_King_Logo.svg
As for the McDonalds logo, I suspect the turquoise is because that's the current background colour of mcdonalds.com
