Live data from Hacker News

Every Fucking Website (2020)

lxe.github.io

111–120 of 529 posts

Re: Every Fucking Website (2020)

#111
post #72

Yea but do you guys remember when we actually needed pop up blockers to avoid having a site spawn like 10 new windows behind the current one, and tabs didn’t really exist yet, and the popups had adult content and sometimes they autoplayed sound/video? Like, internet explorer 6 era? Sometimes I miss those days

You knew you done goofed when the adult site you opened on your family computer was opening new windows faster than you could close them...

Re: Every Fucking Website (2020)

#113
post #51
post #46

Earlier quoted context omitted.

Not web devs per se, I’d be hard pressed to find a serious web dev who wanted to “forcefully sodomize users”. Thats a management thing

"No." If every webdev who would say no can be trivially replaced by webdevs who won't say no, then yes, it is webdevs.

You don't really need a web dev to add a cookie banner these days, but you probably still want one to build the actual site (unless it's simple enough to be fully site-as-a-service, in which case there is really no webdev at all).

Be it the EU for regulating disclosure and consent requirements, users for being "lazy" and usually just accepting all, or the webdev for not staking their livelihood on denying the banner - I'm sure they'll all get blamed before someone sees the ones actually demanding it be done can be the problem.

Re: Every Fucking Website (2020)

#114
post #95

Should load much slower. Also, where is the unrelated autoplaying video that will unmute if you actually click it, that follows your scrolling and only becomes smaller when you dismiss it? Plus, it should probably have text that cuts off letting you know you can have access for just $10/month. Plus, isn't this website undissmissably "better in the app" after a few minutes of attempting to use it on a phone? Where's t…

> Plus, isn't this website undissmissably "better in the app" after a few minutes of attempting to use it on a phone? Where's that at?

This is the most annoying thing on the internet. There’s a site I’d like to use, but “try the app” takes up the entire page (and appears to be impossible to dismiss?). Actually, is there a way to permanently request the desktop site for all future visits to a domain on iOS? There is no reason to visit this full-page app advertisement.

Re: Every Fucking Website (2020)

#116
post #46
post #30

Earlier quoted context omitted.

The EU said "you have to ask for permission before forcefully sodomizing your users", and webdevs thought "let's ask for permission" rather than "let's not forcefully sodomize our users". Of course, the law could have said "don't forcefully sodomize users", but it seems the west is still under the impression that some people will do the right thing, just because, sometimes. ( maybe 20 years ago they would have, just…

Not web devs per se, I’d be hard pressed to find a serious web dev who wanted to “forcefully sodomize users”. Thats a management thing

Many of them can't help themselves.

I used to have long conversations with frontend developers that "no, when I log on I don't want to be forced through a look-at-the-new-feature-we-made" sequences. And then they went ahead and did it anyway. And usually whatever flag they tried to set to make sure you only saw it once would malfunction, so next time you'd get to click through it all over again.

(If you want to tell users about new features, show a unread flag on a notification icon and make it a one-click affair to make it go away. Don't get in users' face with stuff they don't want)

Re: Every Fucking Website (2020)

#118
We've got the stupid chat bubble at the bottom.

We didn't want it, it's like a megabyte of JavaScript. It's some third party service corporate forced on us.

I have to imagine a lot of websites are in the same boat, where they're just add crap they don't want to add by higher ups.

Re: Every Fucking Website (2020)

#119
post #18

The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.

it's an example of malicious compliance by some, and herd mentality by others. I had a discussion with my CFO about removing the cookie banner from our website (because we don't set any tracking cookies, and cookies for things like login are exempted) and he said "yeah, but it makes the site seem less legitimate.

>it's an example of malicious compliance

So how would you do ePrivacy Directive compliance/risk avoidance in a non-obnoxious way?

Post reply on HN