Intresting, I am working on another list of more advance rate limiting algorithms. I will add GCRA there.

Sorry about that that is my blogging platform Hashnode. It was lesser of four evils:

- Medium which paywalls the article and forces you to sign up just to read.

- Substack has same problem, it's great for funneling people to your paid newsletter but there is a sign up banner as soon the page loads.

- Build your own and miss out on the social aspect and there's no proof if the numbers are real.

hashnode is good. i support you, keep trucking.

Does CGNAT do rate limiting? If so then is there some documentation I can lookup.

I'm pretty sure GP means: all those users have egress from a finite number of IPv4 and thus if rate limiting is done by IP those behind the NAT are going to have a real bad time. It's true of all NAT setups, but the affected audience size for GCNAT could be outrageous

Yup, thank you.

- I like bullet points, they are easy to read.

- "Working" I wanted to keep things consistent.

- Content getting cut was a limitation of iframe. Most blogging platform don't allows you to embed another page. This was best I could do given the limitation.

- I do use AI to bounce ideas, but a lot of effort went into getting the apps working as intended.

Why "Working?" It's unclear what that means.

Is it supposed to say, "How it works"?

Now that you have mentioned it should have been working principle or algorithm. It made sense in my head. English isn't my first language sorry about that.

It was Shadcn, Tailwind.

Yes, I usually prompt (Claude, GPT and Deepseek),on my rough vision, and take ideas from all of them. They never quite get it right on their own. But for a code that's deploy and forget, AI generated code is good enough.

you're 80% there, especially with functionality, but it needs some polishing