The Linux default is about 58 million inodes per TB. How many did you have?
I think we've talked about this before. But, whatever service I'm using, I have a higher limit. Either way, for now the service is viable for our needs, and therefore, I don't need to change it. In the future, I have the possibility to improve this aspect.
A sub-domain may work: whateversite.talkimg.com. If you can enforce it so each image only loads on a certain site, they'll have to respect it.
The issue is not having a subdomain, the issue is that I will have two administration areas. In turn, I had to manually create locks on each domain, so this management really required itself. Because, hotlinking is not always efficient. Basically, it would be like creating two websites, even if the same hosting is used.
It would be nice if you can separate images per domain. I'm currently storing 30 GB of image backups. I like keeping a backup for Bitcointalk, but if other domains upload a lot of images, it's a waste of my disk space.
Going back a little.
I believe you automatically save the backup zip files. But, would you have the ability to check between the image links posted, and the images that are in the backup?
You can basically copy paste this ann there. I think it is worth the effort.
You will also have to teleport so you can post images
He can ask someone who is already active there to open an unofficial topic referencing this thread.
I don't know what to expect from it, but it requires very little effort.
I have no problem putting a topic there. I just don't want to give support there - I don't have time to deal with two support topics (it doesn't even make sense).
I'll think about it.
___
Note for users: the service continues to have hotlinks configured to only work on bitcointalk. Use in other locations may not be guaranteed over time.