|
Is it not true though that GDPR doesn't apply to cookie tokens unless they're used for tracking/behavioural analysis?
Remember-me's, Csrf tokens, and session tokens that are required only for the purpose of enabling a website to operate don't require any special permission.
|
|
|
|
|
WE may understand that, but do (l)users, lawyers, and marketing artists?
And if the site decides to start using tracking cookies later, they are already covered.
|
|
|
|
|
WE - perhaps not, users - even if they do they can feign ignorance and claim they don't in order to have something to moan about, lawyers - if they know their business they will, marketing artists - as for lawyers.
If a site requires tracking cookies further down the line then adding both those and acquiring the users permission should be part and parcel of the same implementation. Besides, as it seems this thread has already established, plonking more complication on the UI than is needed is annoying at the basic level and as is the case with GDPR prompts, misleading if it isn't necessary.
Anyway, it doesn't affect me. I already wrote to my MP and told her that I want as many cookies as I can get.
|
|
|
|
|
The problem is the developers.
For example: we don't need so much javascript-sh*t. It doesn't add any value to hide stuff and wait until the user figures out that they need to do a special mouse dance to see it. Just because you can do it doesn't mean that you should.
KISS!
"Life - Not all parts included, assembly required"
- allan mccombs
modified 11-May-20 18:48pm.
|
|
|
|
|
|
 Thank you, Sander. I expected it even a bit earlier.
|
|
|
|
|
That's the advice of a salesmanager
|
|
|
|
|
No one has mentioned the unbearable numbers of ads that load with what seems like every site.
Nor the videos that start w/o you asking them to.
Faster browser may help too. AS soon as the MS Chrome Edge came out, I tried it. It was so much faster than IE that I switched after a few days of confirming I had no issues with it.
|
|
|
|
|
Auto starting videos are evil.
|
|
|
|
|
From my perspective this is driven by Google.
There is huge pressure to have your sites load fast. Not fast on a desktop, but fast on a mobile device with dodgy 3G connectivity. That's how w're all being judged in Google's Page Rank algorithm (plus the content, of course). Google's gone as far as to say that slow sites will get highlighted as being slow in search results.
So if you have a site that requires customisation for each user then you can' just make a static site. You either invest in massive hardware, rewrite everything in the fastest framework you can, a spend huge on hosting providers, or you create sites that are basically static content with JavaScript that loads and fills in the blanks post load.
Your Time-To-First-Byte, Time-To-First-Meaningful-Paint and all the other metrics then look really good to Google. You can still then customise the page where needed. The losers are then the developers who have to go through these hoops and the users dealing with the Frankensites.
We're having exactly this debate at CodeProject right now. Hosting is not cheap. Hardware is not cheap. Developer time is silly stupid expensive. Yet you have to do what it takes to work around Google's arbitrary rules.
It's particularly frustrating that we, a developer site predominantly used (and most useful) as a desktop site for devs currently at their desktop with their IDEs open, are judged on how fast we load on a $100 Android device in rural Saskatchewan.
cheers
Chris Maunder
|
|
|
|
|
Very interesting, I was not aware of this.
Though, I am wondering if Google is not missing the point there : what they want is happy users by having fast-loading sites - in the end, is is not what they get, but for different reasons. Is there also a Time-To-Last-Byte ?
|
|
|
|
|
There's First Meaningful Interaction, but thankfully they don't have First Meaningful Content. They could be waiting a long time for that.
cheers
Chris Maunder
|
|
|
|
|
We have huge data requirements - we have one table that's got 500k records with over 600 columns. And yes, that's the way it's stored. It's obscene, and that's just one table.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Wow.
I know you have nothing to do with this, but as a user, I wouldn't be happy if I was presented with such a beast and I had to try to find the needle in that haystack. It would make a lot more sense to ask for some filtering criteria first, then produce some sensible results.
Obviously I'm not telling you anything you don't already know, and I'm sure you've already had endless discussions on this with The Power That Be.
|
|
|
|
|
A rewrite is in the planning stages. We're going to completely redesign the back-end.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
IMHO, it's the 'outside' resources (mostly ads with pics/vids) that cause slow loading. There is no way I would give a customer the kind of experience I get when viewing some of the Insider linked content. I'd like to read the article, but am required to wait 10-20 secs until the scroll works. I'm not running an adblocker yet but have been considering it for awhile now. That said, CP has done it right...the unobtrusive ads here don't bother me and don't seem to slow down load time on any device. 
As for the cookie bit, I don't have notifications on any of the dozens of websites I'm responsible for. If I'm breaking a law, I don't care.
"Go forth into the source" - Neal Morse
|
|
|
|
|
If I'm breaking a law, I don't care.
You will when you spend a few months in jail or you are fined $K or you lose your job. Your view is unethical and self-serving. Read the EU guidelines.
Gus Gustafson
|
|
|
|
|
The is a rendering engine problem, and is caused by the "fluid" nature of layout.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Rage wrote: do not tell me to buy faster internet
I'll suggest you think about using a content blocker, instead... I have Ghostery installed on most of the browsers I use & for a sample website, it cuts down the amount of stuff downloaded from 15MB to 3MB and the page load time from around 15 seconds to 4 - although the page keeps downloading new ads after the initial 15 seconds...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
I run piHole DNS servers at home (Raspberry pi 3B+'s running a purpose-built raspian distribution).
They filter out ad sites for all devices connected to my network, so I don't have to configure machines to block the sites.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Don't forget, part of it is loading, and part is rendering.
We use DevExpress tools where I work. They generate such complex html to do their jobs that it's harder for the browser to render the page.
In those cases, there's not a lot the developer can control (except to try to find toolsets that run better).
So, we do what we can to generate the page a quickly as possible--run fewer, more efficient queries and code, mostly, but also things like caching commonly used data and elements.
|
|
|
|
|
Buy a faster computer.
|
|
|
|
|
So much for all the new technologies making things more efficient... 
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Rage wrote: design elements are jumping around while the page is being loaded
[...]
click on a link without it having jumped around three times and you end up clicking on something else
This explains why I've clicked on ads 3 times or so since I've started using the internet in the early 90s.
To this day, I still otherwise would not have clicked on a single ad, ever. If I'm looking for something specific, I search for it, I don't click ads. Which is why I keep saying targeted advertising is wasted on me and I want nothing to do with it. If everybody took that approach, there would be no point in any of the tracking and profile-building that's taking place nowadays...and the world would be a very different place.
|
|
|
|
|
The norm is to use an insane amount of .js libraries to bootstrap front-end development, while simultaneously creating a nearly untestable attack-surface.
But why?
Profit margins.
Eventually, something build on top of WASM will position itself as easy _and_ secure, and .js can burn in a pit of snakes.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
