Enemigo wrote:It's not at all asking for trouble. The Photobucket issue is completely on Photobucket and its users. No sites were harmed from an operational standpoint.
I also prefer to be able to disable photos from the hosting site, rather than having them directly uploaded to the site server where they are VERY hard to ever delete. Sure you can make the argument that your photos are still under someone else's control on Google or Photobucket or wherever, which is true. But if you have a problem photo, you can delete it, it change the address on it and instantly pull it from every where you linked it all at once. I like that option.
ETA: That's my opinion on the issue anyway.
My opinions here, respectfully:
The site owner should not cede control of any content to the mercy of a third party. Yes, the Photobucket fiasco was "on Photobucket". My point exactly. Don't give them (or others) that power. Didn't "harm any sites from an operational standpoint"? That's debatable. Disabling photos rendered some posts completely useless.
And that this could happen over and over without so much as a warning makes it even more worrisome.
It's ultimately up to the site operator, and I respect the choices made. However, what's not debatable -- allowing third-party photo hosting comes with risks as well as the supposed benefits. This site (long before VS came along) took the risk, and got burned.
The sites I operate were not affected in any significant way by the Photobucket fiasco.
And as long as you can edit a post, you should be able to delete images you uploaded, unless the admins have disallowed that.
Jack