Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

1.4K

So, I don't know about the rest of you, but it would seem to me that poal is beginning to hit a limit, whether that is DDOS, or just the influx of new users, I have no clue, even though I might have my suspicions.

I would suggest that Poal gives the option to have a refresh limit on the browser, as I find it slightly of annoying that when I try to up-vote, or click on a link sometimes, it automatically updates where the page right where I was trying to click.

Now, I understand the obvious want of the page to auto-magically refresh, but if I do not need it, then why the fuck give it to me, as I am going to refresh by source of habit?

I don't know, am I nucking futs?

So, I don't know about the rest of you, but it would seem to me that poal is beginning to hit a limit, whether that is DDOS, or just the influx of new users, I have no clue, even though I might have my suspicions. I would suggest that Poal gives the option to have a refresh limit on the browser, as I find it slightly of annoying that when I try to up-vote, or click on a link sometimes, it automatically updates where the page right where I was trying to click. Now, I understand the obvious want of the page to auto-magically refresh, but if I do not need it, then why the fuck give it to me, as I am going to refresh by source of habit? I don't know, am I nucking futs?

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (17).
[–] [deleted] • 0 pt

You're making assumptions that you have no basis to make. First off a single "Content" class would be a horrible design move. But whatever, howabout you simply keep the speculation to a minimum and simply request a feature (or lack thereof) to be implemented or not implemented (or modified). Lol, you even link to a medium.com browser caching article, haha that's cute.

[–] • 0 pt

Let deez yoofs write the code nigga!

[–] • 0 pt

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.

[–] [deleted] • 0 pt

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.

[–] • 0 pt

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.