• 0 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle




  • Federated systems are one option for this. On one of my sites, the only way people can leave comments is with ActivityPub. They must have a (probably pseudonymous) account on a server to use that, and I hope that most servers have moderation I find acceptable. I can block those that do not.

    More sophisticated options for sharing reputation between servers would help here. If, for example five servers I trust block another server as a source of harassment, I’d like to block it as well, automatically.




  • My (self-hosted) Mastodon server seems unable to view profiles on Threads. As far as I can tell, there’s nobody to talk to about that.

    I don’t have high hopes about Meta having good intentions here, but I am eager to see platforms that would have previously been walled gardens open up to the federated model. I do think we have some work to do on the open source side to manage the potential massive increase in exposure once Threads users can follow users of other software.

    Of course you can pick a server that blocks Threads if you just don’t want to deal with that.










  • It’s true I’m assuming the author is being honest about what Cloudflare sent them and not leaving out a message where they made the situation abundantly clear. That’s definitely possible, and we probably won’t find out because big companies don’t usually give public responses to this sort of thing.

    name any other large provider that would behave differently

    I can’t, and this makes me inclined to believe it’s a mistake to rely on any of them without a failover plan. Of course that’s effectively impossible for some situations, like mobile apps requiring app store access. That seems like a situation that calls for antitrust enforcement.


  • Maybe I haven’t been clear enough.

    I have no objection to Cloudflare or any other service provider dropping a risky or unprofitable customer. That’s normal and fair in business.

    What I don’t like is their apparent poor communication and failure to provide a clear (and reasonably distant) deadline so that the author’s company could find a solution that avoided downtime. Were I on that company’s board, I’d likely be pretty unhappy with the author for not having a contingency plan prepared in advance, but as a third-party observer my main takeaway is that if I rely on Cloudflare and they suddenly decide they don’t like something I’m doing, I’m screwed.



  • I did a quick search through Cloudflare’s TOS and did not find anything about gambling. What was the TOS violation here?

    What I’m seeing is Cloudflare communicating very poorly about what actions the customer would need to take to keep their site operating, why, and what the timeline would be. “We’ve determined operating your casino website on Cloudflare IP addresses is an unacceptable risk to our other customers and we require that you upgrade to an Enterprise plan within two weeks or your service will be terminated” is clear, concise, and I believe entirely fair. What they did here makes me think they’re an unreliable and unpredictable service provider.