this post was submitted on 26 May 2024
1158 points (91.4% liked)

Technology

59599 readers
3107 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Also, interesting comment I found on HackerNews (HN):

This post was definitely demoted by HN. It stayed in the first position for less than 5 minutes and, as it quickly gathered upvotes, it jumped straight into 24th and quickly fell off the first page as it got 200 or so more points in less than an hour.

I'm 80% confident HN tried to hide this link. It's the fastest downhill I've noticed on here, and I've been lurking and commenting for longer than 10 years.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 46 points 6 months ago (3 children)

I’m 100% on the side of CF.

100%?

We scheduled a call with their “Business Development” department. Turns out the meeting was with their Sales team,

...

So we scheduled another call, now with their "Trust and Safety" team. But it turns out, we were actually talking to Sales again.

This is the part that's ridiculous to me. If CloudFlare thinks they're violating TOS that's fine. If they're willing to let them continue with their business as-is as long as they pay more? That's fine. But, scheduling calls with one group and it turns out it's actually CloudFlare's sales team on the phone, that's ridiculous.

[–] [email protected] 23 points 6 months ago

Well, the way he describes it does sound messed up, but if the only solution CF is willing to accept is for them to bring their own IPs and that is only available with an enterprise plan, what kind of conversation were they expecting? And like I said in another thread, enshitification at CF affected their customer service the most. We went from being able to to speak directly to devs, to people who actually understood the problem, to first tier support that didn't understand shit to 0 tier support that barely understands English.

[–] SquiffSquiff 18 points 6 months ago (1 children)

It seems that you've misunderstood what the issue is here from cloudflare's perspective. The customer was using cloudflare IP addresses, which is causing a knock-on effect for the rest of cloudflare's customers and putting cloudflare as a business themselves at risk. The alternative was for the customer to use their own IP addresses as cloudflare advised . I'm not sure what you think 'Business development' teams do but I certainly wouldn't be expecting engineering advice from them.

[–] [email protected] 1 points 5 months ago

The customer was using cloudflare IP addresses, which is causing a knock-on effect for the rest of cloudflare’s customers and putting cloudflare as a business themselves at risk.

Right, so sales should not be involved in any way.

The alternative was for the customer to use their own IP addresses as cloudflare advised .

Again, sales should not have been involved in any way.

I’m not sure what you think ‘Business development’ teams do but I certainly wouldn’t be expecting engineering advice from them.

They are at least not identical to sales. They work with sales, but there's at least some engineering component of the job. In this case if you were told you were meeting with the business development team, you'd expect that there would be talk about an engineering solution to the problem. Not just paying cloudflare more money.

[–] [email protected] 13 points 6 months ago* (last edited 6 months ago)

These articles are always embellished, so I would take it with a grain of salt.