In addition to Flickr, follow some of the many popular options:
-
Imgur : An extremely popular service ( Wikipedia article ) to host photos. Exposes a REST API with JSONP and XML support. The API is free for non-commercial use and upload of up to 1250 photos per day (see boundaries ); you also have business plans between $ 25 and $ 500 a month. Requires registration and authentication (OAuth 2.0).
-
Uploads.im : Free and limitless Russian services (in addition to restricting the maximum image size to 10 MB). In addition to popular formats for web images, it supports PSDs and PDFs. Has API REST with support for JSON (P), XML, TEXT, or Redirection formats (in the latter after a
POST
the API redirects to the viewer). No registration or authentication required.
-
ImageShack : Commercial service for uploading images and videos (the free service has recently been discontinued, but a trial of 30 days is still available). Entries range from $ 2 to $ 100. Exposes REST API with support for JSON and XML formats. Requires registration, obtaining key for access and authentication OAuth 2.0.
-
Cloudinary : Image management service in the cloud. It has a free plan (limits: 500 MB of space, 50,000 images and 1 GB of band / month) and commercial plans priced between US $ 39 and $ 219. It uses Amazon S3 and provides CDN, automatic backup services, image manipulation services, effects, watermark face detection, creation of sprites , etc. It has a REST API with key-based authentication, as well as multi-platform libraries (including PHP ).
-
Picasa Web - Google service for hosting photos and videos based on feeds . It's free as per Picasa Web / Google+ limits (1GB of storage, with photos smaller than that 2048x204 and / or videos shorter than 15 minutes do not consume space for Google+ users). Extra space can also be purchased ( 100 GB for $ 4.99 ) and the service easily scales to storage TBs for applications with this need . In addition to direct access through the feeds protocol, there are libraries for various platforms, including PHP (currently only for version 1.0 of the API). Authentication options via OAuth 2.0, OAuth 1.0 AuthSub or "installed" (login / password).
Another option besides deploying a mechanism to store and retrieve profile images at hand is to use Gravatar . Gravatar allows the user to associate an identity (including photos) with his or her email address. This way your application becomes a simple consumer of the user profile image ( see PHP code example ).
The same can be done with Social login . Sites like Facebook , Twitter a> and Google+ exposes authentication mechanisms and access to the user profile. Libraries such as HybridAuth and Janrain allow users of your authenticate with popular providers (as well as anyone else who supports OpenID ) and expose a common API so your application can easily consume user information (including the profile picture) without you having to worry about the implementation details of each provider.
In short, there are many options for what you want, but the first exercise to be done (before we talk about code) is to better understand what your real requirements are, and from these, choose the best solution for your application .