this post was submitted on 08 Nov 2023
43 points (95.7% liked)
Hacker News
4123 readers
2 users here now
This community serves to share top posts on Hacker News with the wider fediverse.
Rules
0. Keep it legal
- Keep it civil and SFW
- Keep it safe for members of marginalised groups
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Here’s where their claim is bullshite.
If it’s a “small percentage” that’s affected, why waste the effort to block it?
They’re planning on charging a monthly fee, and I they’re lying about the small percentage.
I think they want to see how many people will convert to their app.
I thought I read from the article, 0.2% of their users were responsible for 50% of the API calls. Most likely due to how things were integrating or polling?
Or because their app sucks and 99.8% of people set it up and never use it.
If it were a polling issue, they could have worked with 3rd party integrations and asked for mitigations or changes to the services. The changes shouldn’t be that hard, they’re known problems with documented solutions.
This is the same as “network neutrality is bad because a small number of users use a lot”
Hell, they could have set up a “free tier” that had a limited number of requests.
Or the best answer, they could have made an “all local network” api that allowed them to skip out on data costs entirely for people that don’t want to use their app.
Why did they skip out on any of the solutions available that allowed users to continue to integrate?
💰