You know what’s funny, there’s sometimes a bug I’m encountering when I log in where it briefly logs me in as someone else (or at least sort of looks like it) before it redirects me to my own account.
Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.
It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.
You know what’s funny, there’s sometimes a bug I’m encountering when I log in where it briefly logs me in as someone else (or at least sort of looks like it) before it redirects me to my own account.
Here is me briefly logged in as you, /u/ThisIsJohnny. Not even making that up, that’s an actual screenshot from earlier today.
Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.
Yeah they didn’t think to dewraggle the niche log scramblers, so now they’re too loose for the parametric variables, those dummies.
It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.
I wonder if anyone has been me
I have been you, SwallowsDick
Holy shit! It there a never tell me the odds community here? This fits like a glove
Did you report this (on GitHub possibly)? That seems to be a fairly important bug for the devs to get their head around.
Here’s Johnny!