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

©2026 Poal.co

733

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).
[–] • 0 pt

Ok, so you are using nodeJs which is dropping "content" off to a reddis server, which is somewhat irrelevant to what I am talking about.

I haven't looked at the code, but I would hope that a member of the "content" class would be properly contextualized, such as post, comment, upvote, etc, where in theory you could div it out to each class to have its own respective cache-control?

The easiest way would be to look at how you could look at using the html5 way of what you are allowing the browser to pull, first off: https://medium.com/@codebyamir/a-web-developers-guide-to-browser-caching-cc41f3b73e7c

I mean, this is old school, but what the fuck, you guys aren't telling the browser how to behave?

I mean, it should be possible to allow certain items to be cached by the browser, and other items not so much.

[–] [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.