• 2 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: October 2nd, 2023

help-circle








  • Thank you for the detailed response. It’s disheartening to consider the traffic is coming from ‘real’ browsers/IPs, but that actually makes a lot of sense.

    I’m coming at this from the angle of AI bots ingesting a website over and over to obsessively look for new content.

    My understanding is there are two reasons to try blocking this: to protect bandwidth from aggressive crawling, or to protect the page contents from AI ingestion. I think the former is doable, and the latter is an unwinnable task. My personal reason is because I’m an AI curmudgeon, I’d rather spend CPU resources blocking bots than serving any content to them.






  • It’s an agree as in I don’t really feel like arguing with another user here. I don’t buy the point about metadata when Signal, a centralized service like Discord (why are we talking about Discord?), may be able to scrape it too. Or the point about anonymity when Signal is far from the right tool for that purpose too, see above “spams your contact list.”

    For reliability, I’m not concerned with how much RAM Signal’s servers have. What I should have highlighted is that Signal can nuke your communications on accident / on purpose / under coercion. And it’s proven because they’ve already done it before. Mitigate that by having a backup system set up? That necessarily doubles your surface area for breaks in privacy or whatever a given user is worried about. So starting with Signal in the first place doesn’t make sense to me.