KeellsCovid new tab generator !

[genius_EK]

ela

 

[HellooWorldd]

එල එල තව DDoS ටූල්ස් ටිකක් හදල බෙදපන් කීල්ස් එකට කෙල වෙලාම යන්න ​

මුන් මහ මී හරක් බං. ඒ මිනිස්සු මේ වේලාවේ පුළුවන් විදිහට වැඩ කරන්න හදනකොට මේ බුරුවො ඉඳගෙන ඒක තවත් අමාරු කරනවා. මේකේ ඉන්න ඔක්කොම එවුන් තප්පරෙන් refresh වෙන්න දාල run කරද්දි හරි ඉතින් site එකට.

 

[nevermindNevergiveup]

මුන් මහ මී හරක් බං. ඒ මිනිස්සු මේ වේලාවේ පුළුවන් විදිහට වැඩ කරන්න හදනකොට මේ බුරුවො ඉඳගෙන ඒක තවත් අමාරු කරනවා. මේකේ ඉන්න ඔක්කොම එවුන් තප්පරෙන් refresh වෙන්න දාල run කරද්දි හරි ඉතින් site එකට.

ඔය වගේ ඒවට මම රිප්ලයි නොකලෙත් එකයි මචං. මැනුවලි රීෆ්‍රෙෂ් කරන්න වෙනවට පොඩි විසඳුමක් විතරයි මේක

 

[Edward Kenway]

ඔය වගේ ඒවට මම රිප්ලයි නොකලෙත් එකයි මචං. මැනුවලි රීෆ්‍රෙෂ් කරන්න වෙනවට පොඩි විසඳුමක් විතරයි මේක

රිප්ලයි කරන්නේ කොහෙද උඹට ඌ කියල තියන එකවත් තේරිලා නෑනේ ​

 

[nevermindNevergiveup]

රිප්ලයි කරන්නේ කොහෙද උඹට ඌ කියල තියන එකවත් තේරිලා නෑනේ ​

bot එකකින් එකපාර requests දාගෙන දාගෙන ගිහින් server overload කරන එකට ddos කියන්නේ.

 

[Edward Kenway]

bot එකකින් එකපාර requests දාගෙන දාගෙන ගිහින් server overload කරන එකට ddos කියන්නේ.

උඹට ඌ කියන එක තේරෙන්නෙත් නෑ මං කියන එක තේරෙන්නෙත් නෑ

අව්ලක් නෑ ​

 

[Voltage]

bot එකකින් එකපාර requests දාගෙන දාගෙන ගිහින් server overload කරන එකට ddos කියන්නේ.

DDoS කරන්න bot ම ඕන කියලා කවුද කිව්වේ

AL OL results බලන කාලෙට site එකට යා ගන්න බැරි වෙන එකත් එක්තරා ආකාරයක DDoS එකක් තමයි

 

[nevermindNevergiveup]

DDoS කරන්න bot ම ඕන කියලා කවුද කිව්වේ

AL OL results බලන කාලෙට site එකට යා ගන්න බැරි වෙන එකත් එක්තරා ආකාරයක DDoS එකක් තමයි

Ddos attack ගැන බං මං කිව්වේ

 

[sithija.h]

Pattai!

 

[krizta]

DDoS කරන්න bot ම ඕන කියලා කවුද කිව්වේ

AL OL results බලන කාලෙට site එකට යා ගන්න බැරි වෙන එකත් එක්තරා ආකාරයක DDoS එකක් තමයි

BTW keells eke cloudflare anti-ddos protection dala tiyenava.

Ithin ban kohomath ekai Meyage tool eken refresh kalath ekai manual refresh kalath ekai. Man Chrome ekata Auto refresh dala balan hitiya eth set une na.

 

[ramishka]

This is a very selfish solution.

This is a time where Keels (or whatever other supermarket) is trying to scale their web operations due to unprecedented demand. They are dealing with finite hardware and software resources and understaffed teams.

In the meantime, you guys create a tool that will use up valuable server resources just to keep this bullshit solution running.

If 10 people use this tool with 25 tabs, that creates 250 sessions on Keels site (i didn't look at any code - i'm assuming it does)? So 10 people take up 25% of the allocated 1000 sessions at a given time. And how many requests would it send to the server if some idiot sets the interval to 0.1 across all tabs? This is spam. If you really think this is a fair thing to do, you must be fucked in the head.

Development teams will now have to spend resources to block shit like this off instead of focusing on scaling to serve more actual customers.

Leaving ethics aside, if you really wanted to build a website change monitor, there are better ways to do it rather than hammering their servers across x tabs. This is a shitty solution in terms of software development standards and architecture as well.

Use your programming knowledge responsibly to do some good, not to build hacky bullshit like this so you can get some street cred from random online folks.

 

[nevermindNevergiveup]

This is a very selfish solution.

This is a time where Keels (or whatever other supermarket) is trying to scale their web operations due to unprecedented demand. They are dealing with finite hardware and software resources and understaffed teams.

In the meantime, you guys create a tool that will use up valuable server resources just to keep this bullshit solution running.

If 10 people use this tool with 25 tabs, that creates 250 sessions on Keels site (i didn't look at any code - i'm assuming it does)? So 10 people take up 25% of the allocated 1000 sessions at a given time. And how many requests would it send to the server if some idiot sets the interval to 0.1 across all tabs? This is spam. If you really think this is a fair thing to do, you must be fucked in the head.

Development teams will now have to spend resources to block shit like this off instead of focusing on scaling to serve more actual customers.

Leaving ethics aside, if you really wanted to build a website change monitor, there are better ways to do it rather than hammering their servers across x tabs. This is a shitty solution in terms of software development standards and architecture as well.

Use your programming knowledge responsibly to do some good, not to build hacky bullshit like this so you can get some street cred from random online folks.

It's not something like what u are arguing about. What the tool does is helping the user with refreshing the page rather than doing it himself. Creating more tabs doesn't mean it consumes sessions. Once the page is loaded in a new tab it's just another page not a session unless the user is logged in.

 

[ramishka]

It's not something like what u are arguing about. What the tool does is helping the user with refreshing the page rather than doing it himself. Creating more tabs doesn't mean it consumes sessions. Once the page is loaded in a new tab it's just another page not a session unless the user is logged in.

Don't try to sugarcoat this with dumb arguments.

You're spoofing a legitimate user in each tab. It does not matter if it creates an actual session on the keells server or not (besides, how do you know when and how keells shows the max sessions warning dialog? Maybe it counts the logged in seesions maybe it shows based on current traffic or another metric? How do you know?).

Fact is that 10 legitimate users using your tool consume the resources of 250. Do you really think this is fair?

25 tabs (or more) are hitting the Keells server at the given intervals. If we talk about this in terms of computer security, you are distributing a tool that does an AVAILABILITY ATTACK on Keells servers.

 

[Identity]

Don't try to sugarcoat this with dumb arguments.

You're spoofing a legitimate user in each tab. It does not matter if it creates an actual session on the keells server or not (besides, how do you know when and how keells shows the max sessions warning dialog? Maybe it counts the logged in seesions maybe it shows based on current traffic or another metric? How do you know?).

Fact is that 10 legitimate users using your tool consume the resources of 250. Do you really think this is fair?

25 tabs (or more) are hitting the Keells server at the given intervals. If we talk about this in terms of computer security, you are distributing a tool that does an AVAILABILITY ATTACK on Keells servers.

Sessions are IP based, so this tool only improve chances to get a session.

 

[ramishka]

Sessions are IP based, so this tool only improve chances to get a session.

I'm not talking about the implementation of a 'Session' in Keells server. I'm talking about what this tool spoofs. In each tab, it simulates a legitimate user refreshing the page. That consumes valuable network resources on Keells end.

 

[fairleen]

good work

 

[Sub Zer0]

I'm not talking about the implementation of a 'Session' in Keells server. I'm talking about what this tool spoofs. In each tab, it simulates a legitimate user refreshing the page. That consumes valuable network resources on Keells end.

enough. Stop being dumb.

 

[Edward Kenway]

This is a very selfish solution.

This is a time where Keels (or whatever other supermarket) is trying to scale their web operations due to unprecedented demand. They are dealing with finite hardware and software resources and understaffed teams.

In the meantime, you guys create a tool that will use up valuable server resources just to keep this bullshit solution running.

If 10 people use this tool with 25 tabs, that creates 250 sessions on Keels site (i didn't look at any code - i'm assuming it does)? So 10 people take up 25% of the allocated 1000 sessions at a given time. And how many requests would it send to the server if some idiot sets the interval to 0.1 across all tabs? This is spam. If you really think this is a fair thing to do, you must be fucked in the head.

Development teams will now have to spend resources to block shit like this off instead of focusing on scaling to serve more actual customers.

Leaving ethics aside, if you really wanted to build a website change monitor, there are better ways to do it rather than hammering their servers across x tabs. This is a shitty solution in terms of software development standards and architecture as well.

Use your programming knowledge responsibly to do some good, not to build hacky bullshit like this so you can get some street cred from random online folks.

Fucking script kiddies ​