Quote from: LoyceV on Today at 06:15:13 PM

Quote from: theymos on Today at 06:09:53 PM

- If joker_josue merely promises that no logs are kept, then I think that that is sufficient for now, and I will exempt TalkImg from the proxy, once TalkImg is working again.

Joker_joshue just posted IP-addresses (used in the DDOS). His webhost may not even allow him to not keep logs.

These IPs were obtained through Cloudflare data. I had never used Cloudflare for talkimg.com before, this is the first time and so I had access to this data.

Now, it is true that many host servers do this logging, even temporarily. But, to access them, you will need to do a deeper investigation. I don't even have time to scratch my itch, let alone scrape IPs... I have more to do in life.

Quote from: theymos on Today at 03:38:45 PM

If the attack is still going on in a few days, I'll consider measures like these:
- If there are any image hosts run by trustworthy companies where the privacy policy says that they don't keep logs, these could be exempted from the proxy. If you know of any, let me know.
- Maybe bitcointalk.org could pay TalkImg a monthly fee for a contractual guarantee that they won't keep logs. TalkImg could then be exempted from the proxy, and furthermore they would have more resources to function well.
- Bitcointalk.org could add support for uploading images directly.

First of all, I thank you for your trust, but as I say in the OP, I do not record any information. The only thing that is recorded in the database is the IP of the person who uploaded the image for spam control or upload cascade purposes..

Therefore, I am available to work to improve and follow the standards requested by Bitcointalk.