Just wanted to comment on the clarity and effectiveness of the home page. Love it! So many user-friendly checkboxes are ticked off. Nice look, great description, plenty of examples, advanced usage section that's very easy to take in, credits at the bottom with some backend tech used, a welcoming contact link...
All of this accomplished (landing page and documentation) in just a few scrolls of the mouse. I went from novice to expert in a minute. There was a real effort to communicate with the end-user from an (empathic) end-user perspective.
Even the parsed json page listing a default 30 images (with credits) is easy to navigate with all the pertinent information available - including urls that open in a new tab (so a user doesn't lose their place on the origin page).
You mentioned in another comment that 400 million images are served per month. Yet... it has the feel (and performance and care) of a small static site.
Exactly. It took me under 30 seconds of scanning through the page to understand most of the API. No fancy badges, abstract graphics or buzzwords, just a direct demonstration of the value. This is how product pages should be.
One minor nitpick is the use of "random" where they mean "arbitrary". :)
Also, it's still a bit unclear how caching of images would work when you append an arbitrary parameter: text implies none of the images would be cached (presumably because of cache headers or browser behaviour), but I'd prefer it if they were indeed cached by browsers as distinct images instead (iow, soft-reloading X/Y?something=foo will give you the same image).
Basically, I'd like them to figure out all the caching semantics and behaviour, and just do the right thing ;)
I'm personally partial to PlaceKitten[1] though around halloween I will sometimes switch it up with PlaceZombie[2]
This one looks nice in that you wouldn't be embarrassed if it goes live since the images are generally nice looking but part of the appear of YAPHS (Yet Another Placeholder Service) is that it is really obviously a placeholder so you catch it before it goes live.
I wear corgi t-shirts, carry a little felt corgi keyring charm, have unicorgi stickers on laptop and tech bag both, my lunch bag is printed with corgis... there's a pattern here.
I feel like this misses the entire purpose of lorem ipsum. Good layout designers don't just want letters and spaces. They want letters and spaces that approximate the whitespace ratio of writing. Your version has only very long words and very short words and nothing in between. This feels like the telephone game version where all of the original intent has been lost and all that's left is a weak simulacrum in vaguely the same symbol space.
I like it, but isn't one of the points of lorem ipsum that few people understand the meaning of any word and therefore get distracted? I just like to sneak-read yours a lot.
I recently launched http://joeschmoe.io, which is a similar API but for illustrated profile pictures. Did pretty well on product hunt and other places, so might be of interest here too :)
Are the photos scraped automatically from Unsplash or are they manually curated in some way?
I'm wondering because it looks like that website classifies photos by category (animals, architecture, fashion, food) but that information is not on your API.
I think it would be really useful to be able to get a picture of a random animal or a random landscape rather than just a random anything. But I'm not sure if that's outside of the scope of the project.
This site pre-dates the Unsplash license (and before Unsplash had their own API/website even, it started when they were still a tumblr blog), the images used on it is from back when Unsplash still licensed images under CC0.
We're on good terms with the Unsplash team, and think they're awesome.
I'm honestly surprised I haven't seen a placeholder service that serves up ads in the images. The service gets revenue, and the dev gets something that's obviously not a final product.
The service has actually been around since about 2014, currently, we serve about 400 million images a month, using some 6TB of bandwidth. It's pretty manageable since we use a CDN on top of the service, to cache already processed images.
Hoping to do a write-up of the architecture in the future, but the source and deployment setup is available at https://github.com/DMarby/picsum-photos if you're interested
According to github looks like this came first. Seems like unsplash's attempt at making this? However this service doesn't seem to have rate limiting like theirs.
Wonderful, this may be.. IS the best product website I have ever seen!
If you have not thought about it: images does not really work for place holders for charts. Maybe placeholders for pie-, bar- and line-charts etc, can be a feature to come?
There's Google Analytics on the website.
For the API/service, there's no user/usage information being stored, other than aggregated bandwidth/total requests for the entire service, by our CDN provider, BelugaCDN.
You can find the source code, as well as the deployment setup here: https://github.com/DMarby/picsum-photos
[+] [-] O1111OOO|6 years ago|reply
All of this accomplished (landing page and documentation) in just a few scrolls of the mouse. I went from novice to expert in a minute. There was a real effort to communicate with the end-user from an (empathic) end-user perspective.
Even the parsed json page listing a default 30 images (with credits) is easy to navigate with all the pertinent information available - including urls that open in a new tab (so a user doesn't lose their place on the origin page).
You mentioned in another comment that 400 million images are served per month. Yet... it has the feel (and performance and care) of a small static site.
[+] [-] hliyan|6 years ago|reply
[+] [-] dmarby|6 years ago|reply
[+] [-] yingw787|6 years ago|reply
[+] [-] necovek|6 years ago|reply
One minor nitpick is the use of "random" where they mean "arbitrary". :)
Also, it's still a bit unclear how caching of images would work when you append an arbitrary parameter: text implies none of the images would be cached (presumably because of cache headers or browser behaviour), but I'd prefer it if they were indeed cached by browsers as distinct images instead (iow, soft-reloading X/Y?something=foo will give you the same image).
Basically, I'd like them to figure out all the caching semantics and behaviour, and just do the right thing ;)
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] vectorEQ|6 years ago|reply
[+] [-] throwaway2016a|6 years ago|reply
This one looks nice in that you wouldn't be embarrassed if it goes live since the images are generally nice looking but part of the appear of YAPHS (Yet Another Placeholder Service) is that it is really obviously a placeholder so you catch it before it goes live.
[1] https://placekitten.com/ (warning: contains fluffy kittens)
[2] http://placezombie.com/ (warning: contains images of simulated violence)
[+] [-] chx|6 years ago|reply
I wear corgi t-shirts, carry a little felt corgi keyring charm, have unicorgi stickers on laptop and tech bag both, my lunch bag is printed with corgis... there's a pattern here.
[+] [-] theon144|6 years ago|reply
[+] [-] droptablemain|6 years ago|reply
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] ndusan-hn|6 years ago|reply
[+] [-] neilpanchal|6 years ago|reply
http://neil.panchal.io/articles/quantum-lorem-ipsum/
https://github.com/neilpanchal/quantum-lorem-ipsum
Edit: Created a Github repo
[+] [-] ebg13|6 years ago|reply
[+] [-] kevsim|6 years ago|reply
[+] [-] tapland|6 years ago|reply
[+] [-] firmgently|6 years ago|reply
[+] [-] verall|6 years ago|reply
I feel like after reading just a few words my eyes glaze over, but its still English. Even if I jump around, its all proper grammar nonsense.
Thank you!
[+] [-] orblivion|6 years ago|reply
[+] [-] wrycoder|6 years ago|reply
[+] [-] andrei_says_|6 years ago|reply
[+] [-] nkg|6 years ago|reply
[+] [-] fxfan|6 years ago|reply
[+] [-] berbec|6 years ago|reply
This one is genius.
[+] [-] olalonde|6 years ago|reply
[+] [-] kumarm|6 years ago|reply
Anyone used belugacdn before? Care to share your experience?
[+] [-] busymom0|6 years ago|reply
https://www.custompcguide.net/keycdn-vs-bunnycdn-vs-belugacd...
[+] [-] PetahNZ|6 years ago|reply
[+] [-] jypepin|6 years ago|reply
[+] [-] marc_abonce|6 years ago|reply
I think it would be really useful to be able to get a picture of a random animal or a random landscape rather than just a random anything. But I'm not sure if that's outside of the scope of the project.
[+] [-] memco|6 years ago|reply
[+] [-] dmarby|6 years ago|reply
[+] [-] pvorb|6 years ago|reply
Citing from https://unsplash.com/license:
> This license does not include the right to compile photos from Unsplash to replicate a similar or competing service.
I'd argue this is exactly the type of "similar or competing service" that is meant by this sentence.
Edit: Did Unsplash give their consent?
[+] [-] dmarby|6 years ago|reply
We're on good terms with the Unsplash team, and think they're awesome.
[+] [-] wtracy|6 years ago|reply
[+] [-] jbkkd|6 years ago|reply
[+] [-] an4rchy|6 years ago|reply
This seems like a bandwidth heavy service. I am curious to hear how you are thinking about managing/scaling this.
[+] [-] dmarby|6 years ago|reply
Hoping to do a write-up of the architecture in the future, but the source and deployment setup is available at https://github.com/DMarby/picsum-photos if you're interested
[+] [-] n_u_l_l|6 years ago|reply
[1]. https://source.unsplash.com/
[+] [-] graphememes|6 years ago|reply
[+] [-] dosshell|6 years ago|reply
If you have not thought about it: images does not really work for place holders for charts. Maybe placeholders for pie-, bar- and line-charts etc, can be a feature to come?
[+] [-] ndusan-hn|6 years ago|reply
[+] [-] gloflo|6 years ago|reply
[+] [-] dmarby|6 years ago|reply
[+] [-] anbop|6 years ago|reply
[+] [-] codesections|6 years ago|reply
I eventually settled on Pixabay, but if Lorem Picsum has added more images recently, I might need to give it another look.
[+] [-] blackbrokkoli|6 years ago|reply
You can literally use https://source.unsplash.com/random/800x600 (with or w/o the dimension) and get the same result, one level less abstract.
Meanwhile, filter() in CSS provides both greyscale and blur with way more power.
I like your homepage - but what does this add to my workflow?
[+] [-] yaleman|6 years ago|reply
[+] [-] 40four|6 years ago|reply
This one might win the contest on beat name though. I feel like it's a "Doh!! Why didn't I think of that!" moment.
Really cool, great work!