Obviously the intention here was not wrong, it was the approach. No, instead of a userscript, there should have been a sticker reaction MICROSERVICE. All stickers shall be submitted through a JSON interface with a Postman public test bed, and several hundred fuzz testing iterations when pushed to prod (QA still outsourced to India).
Code:
{
"reactionUuid": "08CA88FC-6358-E2CE-3E34-D48CD8E0A98E", // "like"
"postId": 1234,
"userAccessToken": "(ACTIVE SESSION JWT)",
"isNigger": true // BACKCOMPAT: always true
}
The microservice will be built with the cutting edge node.js libraries, but we haven't enforced package locking yet so it might take a few tries to deploy. Oops! Don't worry, though, with Cloudflare® Workers™, the site will have a 99.9999999% uptime rating, with only 48.925s of latency!
Instead of that
nasty relational database stuff, all stickers will be stored in Mongo
loidDB instances, which, depending on your geographic location, will be Eventually Consistent, and after submission to our KiwiFarmsAi instance (patent pending) your "like" will be pushed through a WebSocket to the target retard (TCP fragmentation possible)! Wow!
COMING SOON: StickerOS - your tophats are only a Kubernetes instance away!