Cyprus-Forum.com

[kurupetos]

[Get Real!]

GR, there are extensions such as this: https://chrome.google.com/webstore/deta ... ijmfeeejhc which can give Chrome (and other Chromium browsers) this feature. I haven't tried them, because I rarely see those messages.

Thanks for the link Sotos... so I *do* have some competition in this department after all... not that the idiot Paphitis would have a clue. I’m surprised the Google store allowed this with a name like “Cookie Fucker”... I burst out laughing upon reading that!

From the author…

“This is the only extension that does not contain huge databases with tons of rules specific for each website. Instead of that the light yet very intelligent algorithm does quick analysis of a webpage and automatically removes all annoying cookie notifications.”

Same as my method... I have to take a look at his source code. I wonder which of the two has the best technique and the best success rate.

You probably used to see them all them time with your browser because you had cookies disabled, but for a normal user those things are not a huge problem because your choice is stored in the cookie and you you don't get the prompt constantly for the same site.

No, I only have 3rd party cookies disabled, and so should everybody else.

[yialousa1971]

Paphitis stop clowning around.

[Get Real!]

OK, the source code is right here Sotos...

https://github.com/siffash/cookie-fucke ... tScript.js

I had a good look at it and I very much doubt it's as effective as mine because he is making a lot of mistakes and bad choices such as:

* He removes elements from the page but I only hide them and sink them to the bottom of the page. Some pages are "smart" enough to know when they lose a part of them and may react to it, plus you don't want to affect element positioning by deleting things.

* He has countless global variables declared and that's amateurish... it should be a self-contained single function with local variables only.

* He handles foreign language sites foolishly... with an array of constant interpretations for "cookie" like "piškotke" for Polish which is stupid because everyone uses the English word "cookies".

example: https://www.mixanitouxronou.gr/

* He foolishly checks for (document.readyState === 'complete') but that comes just before the onload event! In fact I even wait 2-3 seconds after onload before operating on a page to catch late script injections.

* His conditions of what constitutes a cookie/privacy banner are flawed... he expects them to be at specific locations and dimensions on the screen which is wrong. A banner could be tiny and not as wide as viewport-width etc.

Anyway, I would love to take his script for a spin but it's so badly structured that I can't use it without wasting too much of my time.



Some thoughts follow on such algorithms... which is how I designed mine:
-------------------------------------------------------------------------------------------

To design a clever cookie/privacy banner removing algorithm you’ve got to think better by asking yourself…

What is the most important aspect of such a banner? The answer to that of course is the acceptance button!

Without a way for the user to give consent then it’s all for nothing!

Therefore… we must concentrate on the “acceptance mechanism” to find these special banners and not the container that holds them.

Once you have found a “acceptance mechanism” then it's a simple case of looping backwards to find the main parent which you'll make invisible... not the children.

[Paphitis]

GR, there are extensions such as this: https://chrome.google.com/webstore/deta ... ijmfeeejhc which can give Chrome (and other Chromium browsers) this feature. I haven't tried them, because I rarely see those messages.

Thanks for the link Sotos... so I *do* have some competition in this department after all... not that the idiot Paphitis would have a clue. I’m surprised the Google store allowed this with a name like “Cookie Fucker”... I burst out laughing upon reading that!

From the author…

“This is the only extension that does not contain huge databases with tons of rules specific for each website. Instead of that the light yet very intelligent algorithm does quick analysis of a webpage and automatically removes all annoying cookie notifications.”

Same as my method... I have to take a look at his source code. I wonder which of the two has the best technique and the best success rate.

You probably used to see them all them time with your browser because you had cookies disabled, but for a normal user those things are not a huge problem because your choice is stored in the cookie and you you don't get the prompt constantly for the same site.

No, I only have 3rd party cookies disabled, and so should everybody else.

Oh you have some competition alright. I mean sorry, that would imply that you are competition for them. And sorry to report the fact that they don't even know you exist.

Mozilla blocks cookies from the outset if you configure it to do that, but you also risk breaking many web pages.

https://support.mozilla.org/en-US/kb/bl ... ng+cookies

Additionally, there are dozens of extensions which block adds for any Chromium browser. The exception here is Opera which has everything already inbuilt.

I don't use any Chrome or Chromium other than Opera.

You can also add extensions to block every script, every add and all cookies as well. And you can disable Google Tracking by not logging in. Problem with that is you can't log in to YouTube. I follow certain contributors so logging in is important to me. But if for instance you use Duck Duck Go, the only activity they can track is what you are watching on YouTube. it doesn't bother me at all.

In the end, I get zero adds, no banners and I can block cookies at a time and place I CHOOSE.

I have a fully functioning web experience and can also access Google services whenever I need to. I don't get any of the banners you use to get, not a single add, even in YouTube videos, and I control what Google sees and doesn't see because I am in total control over my own activity.

[Get Real!]

Paphitis, the only kind of cookies you seem to understand are the ones mommy used to stuff in your mouth whenever you had a tantrum...

[Sotos]

I had a good look at it and I very much doubt it's as effective as mine

There are several such plugins, that was just one example. I can't judge which one is better, but the fact that his code is open source is definitely an advantage.

The question is: Can you make a plugin that has the same functionality? If you can, then it is much better to have it as an optional plugin for those that need this functionality, rather than bloat the browser. I think your time would be better spend if you were writing extensions if you care about other people using what you code. If you just want to make one browser that fits your own needs then fine, but that would be your own personal browser not something that would be appropriate for most others.

[Paphitis]

Spot on Sotos!

One day this imbecile is gonna get it. The others are user configurable, whereas he is applying a one size fits all.

No thanks!

[Get Real!]

I had a good look at it and I very much doubt it's as effective as mine

There are several such plugins, that was just one example. I can't judge which one is better, but the fact that his code is open source is definitely an advantage.

The question is: Can you make a plugin that has the same functionality? If you can, then it is much better to have it as an optional plugin for those that need this functionality, rather than bloat the browser. I think your time would be better spend if you were writing extensions if you care about other people using what you code. If you just want to make one browser that fits your own needs then fine, but that would be your own personal browser not something that would be appropriate for most others.

Everything in my browser is user selectable/configurable including the cookie banner detecting/removing option.

There’s no bloat whatsoever if you know how to code in an optimized and well structured way, and I’ve had many decades of experience in that department.

Bloat occurs from declaring too many global variables, from heavy and/or incorrect use of event handlers, from timers like setInterval() that are left to roam in memory and using up machine cycles, etc.

Bloat is all the crappy Chrome extensions like the one we looked at... if it’s anything to go by.

No bloat my friend... just coding excellence, as the trusty Windows Taskmanager reveals:

bloat.png

[Pyrpolizer]

Just a question GR:
I assume you use your Classic browser to log in here. Does it remember your nick and password or you have to enter it every time?