Quote from: joker_josue on November 06, 2024, 08:07:35 PM

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.

For the record: I wasn't blaming you. I too use default Apache logs on my server, and I too only look at it when there's severe abuse going on.

Quote from: bitmover on November 06, 2024, 08:17:54 PM

I think cloudflare will store some user data anyway, right? Like ip of people who sent files. ?

This comes to mind:

Quote from: theymos on November 29, 2017, 11:35:34 PM

What I meant is that Cloudflare can see your unencrypted password when you log in. It's still encrypted from the real server to Cloudflare and from Cloudflare to you. So it's not blatantly insecure except in that Cloudflare is very probably an NSA honeypot, and it's not like the NSA is going to steal your password in order to scam people on bitcointalk.org or anything.

Since the forum uses Cloudflare already, that doesn't add any new risks.

Quote from: dkbit98 on November 06, 2024, 10:01:06 PM

Quote

Sorry, you have been blocked
You are unable to access talkimg.com

I get the same. It's the same message Cloudflare gives on Bitcointalk when you're trying to post something Cloudflare doesn't like. Just a few weeks ago that was /etc/hosts.

Quote from: Richy_T on Today at 04:52:05 AM

Likely the forum is the main target and the attackers just saw talkimg as likely the easier target.

Take down the image hosting and image proxy, take down ChartBuddy. No ChartBuddy, no hourly price updates. This is food for conspiracies Tongue

Quote from: NotATether on Today at 06:14:04 AM

Quote from: LoyceV on November 06, 2024, 12:13:12 PM

If you can see this image, the forum's image proxy is working fine:
Image loading...

Negative, on my side.

Same here.

How is ChartBuddy doing it?

Quote from: ChartBuddy on Today at 09:01:14 AM

Explanation

It links to an IP-address instead of a domain name. Does that mean the attack is on the image proxy's DNS server?