Mmastodon TechnologySoftware first seen 2 d ago, last 1 d ago, peak #7
Developer calls out GitLab front-end for hammering its own GraphQL API
Original: By the way, dear # GitLab : I can see from my browser dev tools that my browser is indeed sending your GraphQL endpoint
A developer publicly criticized GitLab after noticing through browser dev tools that GitLab's own front-end sends a heavy volume of requests to its GraphQL endpoint, triggering 429 rate-limit errors. They argue the rate limiting is self-inflicted by GitLab's own code design and say the company should have accounted for this when building its front-end. Other developers are likely chiming in with similar experiences of GitLab's interface being slow or throttled.
Why now: Developers frequently complain about GitLab's web performance and rate-limiting behavior, so this critique resonates with users frustrated by 429 errors on the platform
Rank over time, top of the chart is #1. 8 snapshots from 2 d ago to 1 d ago.
Evidence
- By the way, dear # GitLab : I can see from my browser dev tools that my browser is indeed sending your GraphQL endpoint an awful lot of requests, and I'm sure that's why you're throwing 429s…but maybe you should've thought about that BEFORE you wrote your front-end code this… · argv_minus_one@mastodon.sdf.org · 12
API: https://socialmediatrends-api.osmike.com/v1/trends/4672334