View Single Post
Old 06-13-18, 10:15 PM
  #17  
canklecat
Me duelen las nalgas
 
canklecat's Avatar
 
Join Date: Aug 2015
Location: Texas
Posts: 8,811

Bikes: Centurion Ironman, Trek 5900, Univega Via Carisma, Globe Carmel

Mentioned: 150 Post(s)
Tagged: 0 Thread(s)
Quoted: 2674 Post(s)
Liked 65 Times in 55 Posts
Photobucket only blocked images from showing inline outside of PB to conserve bandwidth. There was an easy workaround -- various browser plug-ins to bypass the PB block. Worked fine.

PB didn't delete photos or accounts or block owners from accessing their own photos after logging in to their PB accounts.

Most supposedly blocked photos could be viewed by other users by clicking on the PB notice, or right-clicking and choosing an option to open in another tab or window. They just didn't appear inline with discussion forums and other sites. Again, PB was attempting to conserve bandwidth.

Years ago it wasn't an issue when most folks uploaded low resolution JPEGs from the early digicams and phones. But millions of users who weren't tech savvy were uploading maximum resolution photos from high resolution cameras. This also happened on a photography website where I was a moderator for years. Even folks who purchased high resolution cameras didn't understand how to resize photos before uploading.

The best solution would have been for Photobucket to automatically downsize photos for free accounts. That would solve the bandwidth problem. Reserve high resolution photo storage for paying subscribers. Photobucket used to do this. So did many sites, including Flickr years ago. Made it easier for users who'd upload hundreds of 6000x4000 JPEGs, which were automatically downsized to 1000 pixels or so on the longest edge to be suitable for most online display. Consumed a lot of their own bandwidth, but not Photobucket's or the sites where the photos eventually were posted.
canklecat is online now