Live data from Hacker News

Purge site data when site identified via old tracking cookies

bugzilla.mozilla.org

131–135 of 135 posts

Re: Purge site data when site identified via old tracking cookies

#131
post #43

Earlier quoted context omitted.

Perhaps create a new and separate Web, that's designed from the ground up to take into account the lessons of the past 25 years, and provide a more mellow experience? It would be an eternal niche, but it might be a nice, cozy little niche.

Most site interactivity could be handled with forms (though some form inputs need improvement) or some sort of conditional view state (for menus and HN's collapse comment feature). For anything more complex I think the "click to enable" model that flash and applets eventually followed is compatible with anything that actually deserves custom code.

I’ve given this a lot of thought over the years and I think html needs slightly more functionality to completely obviate JS. The hardest impact of no JS is dynamic input forms, and I remember when ajax first became a thing and forms that didn’t lose their content on an input error became commonplace. There was never a good reason for them to lose their input, of course, as that’s just lazy coding.

But when writing JS-free front ends for my web apps, the ugliest UX is trying to fill out a form that requires either filling out n identical sections (eg a fieldset for each student you want to add) or selecting an item from a drop-down w/ the option of adding to it if the desired option doesn’t exist.

Error validation is now clean and easy with modern MVC frameworks that take as input the same structure of data they used to generate the page in the first place, so it is easy to rebuild the page exactly as it was but also include an error message. There is no jarring user experience when the page is submitted and reloaded with the error shown inline. But having to navigate to a separate page to add an entity then refresh the form to fill out the data selecting the newly added entity sucks.

HTML needs some sort of functionality that would enable a) dynamic non-Turing-complete remote resource backing of form input values, b) allowing a form input to return post submission to a dom element rather than a document (E.g. imagine an input to “add location” to a drop down; submitting that field would return the new content of the select option elements to replace the existing). A JS powered example is intercooler JS.

More generally, a content response type that says “patch the existing DOM with the following” would preserve pretty much all the good parts of Web 2.0 without the crap that came with it; keeping in mind that submissions could only happen when a user explicitly requested them.

Re: Purge site data when site identified via old tracking cookies

#132

Earlier quoted context omitted.

I do approximately the same in macOS: /Applications/Firefox.app/Contents/MacOS/firefox" --no-remote --profile "$(mktemp -d)

Isn't it what the "private browsing" option of Firefox does?

Mostly, yes. The bonus is you don't use your normal settings + extensions. Which also means ALL websites work, regardless of privacy related settings that might break some websites. So it's a handy alternative.

Re: Purge site data when site identified via old tracking cookies

#133
post #40

Earlier quoted context omitted.

I'm not 3xblah, obviously, but I deal with those sites by not using them.

I wish that was a choice for me. Often I have to interact with websites for services such as phone accounts, banks or taxes where I don’t have the reasonable option of choosing to not use the site.

Oh, that sucks. I'm lucky -- I can do all those things without having to bring the internet into the equation.

Re: Purge site data when site identified via old tracking cookies

#134

Earlier quoted context omitted.

I wish that was a choice for me. Often I have to interact with websites for services such as phone accounts, banks or taxes where I don’t have the reasonable option of choosing to not use the site.

Oh, that sucks. I'm lucky -- I can do all those things without having to bring the internet into the equation.

I could make a phone call, but I don't see how that is making my life better.

Re: Purge site data when site identified via old tracking cookies

#135

Earlier quoted context omitted.

> Because after you hover on something, it can be an indication of intent. Yes, that's (one of the many reasons) why javascript needs to die. > Just loading an image when the webpage loads doesn't give you any insight into what the user 'interacted' with. That's what I said: regardless of whether the browser, when loading a page, does or does not include hidden images in what it fetches, that cannot possibly tell you…

> > > Because after you hover on something, it can be an indication of intent. > Yes, that's (one of the many reasons) why javascript needs to die. You're missing the point. CSS allows you to load tracking pixels on hover, so you can do that without Javascript.

I was going to say "no it doesn't, that's blatantly stupid, you load things during page load, that's why it's called page load" but on further research, Firefox apparently does do that now. I hate everything and I'm once again glad I stopped updating years ago.[0]

0: I decline to treat the unintentional flaws of [Firefox] as more important than the intentional ones.[1]

1: https://www.gnu.org/philosophy/upgrade-windows.html

Post reply on HN