Yet, you make assumptions.
I understand how nodeJS has a push/ pull dichotomy, and understand how you can classify what you send to a reddis server, so check your own bias, and fuck off faggot.
" First off a single "Content" class would be a horrible design move."
where in theory you could div it out to each class to have its own respective cache-control
You obviously have no idea of classes and sub-classes, and the idea of re-usability.
The fact that they are not telling the browser how to handle each part of content is what I see as an immediate issue.
I have a perfect idea of classes and sub-classes. My thesis in grad school was about creating an updated programming methodology that combined OOP concepts with functional programming. Reusability is a very, very small tenet of OOP when you dive deep enough.
True, and not necessarily true.
I am not going to debate some fucking (((phjd))) about oop, nor was the post even about that. I deal with enough of you fucking retards on a regular basis. It's funny, you fuckers all use the same tactics. Just take a l00kie loo at Dr. Jill Biden, "teacher extraordinaire"?
How about, let's just dive into the simple fucking protocols of HTML5, which are clearly pointed out in that quite simplistic medium article you mention.
So, some of that can be solved by doing some changes to the front-end by simple browser cache control, which in theory would also make it easier to identify bad actors via the fingerprinting that they are already using.
(post is archived)