I'm too big of a nerd to let the RSS feeds, open APIs, etc go. :)
Alas, Flickr wouldn't even be alive if we hadn't increased the price ($$) and value (features) of Pro relative to things like intrusive ads on free accounts, etc. The very reason it's alive is because we have intrusive ads on free accounts, but no ads on Pro accounts, including for viewers. I don't expect that to change anytime soon.
We have some great plans to further increase Pro's value, but we disagree that Pro is too expensive. Relative to our peers, it's a bargain for unlimited storage, advertising free, etc etc.
Love to bounce future ideas off of you, and thanks for the article!
We have a lot of mobile usage and the app works fine, so I'd love to know more about what you're experiencing with it. Can you contact our Support Heroes so we can assist? https://www.flickrhelp.com/
You make a fair point about the age verification thing. I'll look into it. It's probably based on a legal requirement that we have to deal with, even if the solution is silly. Sorry about that.
We rely on self- and community-moderation. As long as content is flagged appropriately, we allow and embrace content that's often banned on other platforms, such as artistic nudes.
Thanks for the feedback and feature request. I don't hear this request often for Flickr, but it's a core and beloved feature on our other platform, SmugMug, which you might want to check out if you haven't.
Yes. Flickr was losing a ton of money (>$50M/year) when we bought it, and it's now cash flow positive and profitable. Not by a lot, alas, but the difference between $1 and $0 or less is the difference between life and death. Flickr is alive!
As I think the article captured pretty well, we could make a lot more money if we went the algorithmic-privacy-violating route, but we don't want to. So we aren't.
Since we never raised a round of funding, as long as the bills are getting paid, we can do what we want - build a company for the long-term based on a great photography community. So that's what we're doing. :)
Just finished reading. Glad they captured what we're doing - photography & community - and what we're not - algorithmic feeds & privacy violations.
We have lots of work to do, and I think most of the criticisms are fair and on our road map. Small team, working hard, listening to customers. Like we've been doing for 24 years. (We're bootstrapped and privately owned, never taken VC).
She was known as being _extremely talented_ at software development, particularly her knowledge of low level hardware and how to optimize around constraints.
This looks super interesting for single-AZ systems (which are useful, and have their place).
But I can't find anything to support the use case for highly available (multi-AZ), scalable, production infrastructure. Specifically, a unified and consistent cache across geos (AZs in the AWS case, since this seems to be targeted at S3).
Without it, you're increasing costs somewhere in your organization - cross-AZ networking costs, increased cache sizes in each AZ to be available, increased compute and cache coherency costs across AZs to ensure the caches are always in sync, etc etc.
Any insight from the authors on how they handle these issue on their production systems at scale?