Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I’d prefer not to let the bad actors dictate browser design.
“Let’s get rid of images since companies can use images to spoof browserchrome elements.”
“Let’s get rid of text since scammers can pretend to be sending messages from the computer’s operating system.”
“Let’s get rid of email since phishing exists.”
Nah. We can do some stuff (like the aforementioned forked history) to ameliorate the problem, and if it’s well-known enough, companies won’t find it necessary anymore. Heck, browsers like Firefox would probably even let you select Canonical Back as the default Back Button behavior, and then you can have the web the way you want it (like people who disable Javascript).
I’m frustrated that removing bad functionality is being treated as a slippery slope with obviously bad and impossible jokes as the examples chosen.
I see a bad feature being abused, and I don’t see the removal of that bad feature as a dangerous path to getting rid of email. I don’t ascribe the same weight that you seem to towards precedent in this matter.
I’ve been working in full stack for long enough to know that history manipulation is as much a part of the modern web as images and email. I’m not trying to be flippant, that’s just the state of the modern web. Single-page apps are here, and that’s a good thing. They’re being used badly, and that’s endemic to all features. So no, history manipulation is not “bad functionality,” though I admit it’s not fully baked in its current implementation.
I accept that it’s how things are, I just personally feel as though the only way this feature could ever work as it does now is with the implementation it has now, and that the convenience of single page webapps that use history manipulation is not worth the insane annoyance of helping my grandma get out of websites that tell her that she has been hacked by the FBI.
I don’t think I’m disputing your facts, I was responding to the scenario you presented which was, essentially, “what about email”. I would say it’s fair that my opinion on a canonical browser history is solid and unlikely to change, though.
I can handle life without the legitimate use case if it means no more clickjacking bs from companies that should know better
I’d prefer not to let the bad actors dictate browser design.
“Let’s get rid of images since companies can use images to spoof browserchrome elements.”
“Let’s get rid of text since scammers can pretend to be sending messages from the computer’s operating system.”
“Let’s get rid of email since phishing exists.”
Nah. We can do some stuff (like the aforementioned forked history) to ameliorate the problem, and if it’s well-known enough, companies won’t find it necessary anymore. Heck, browsers like Firefox would probably even let you select Canonical Back as the default Back Button behavior, and then you can have the web the way you want it (like people who disable Javascript).
i do that, and i found that a TON of microsoft & bank/work websites just refuse to do anything without it. i love the modern internet /s
Yeah, I get it. But I fear that ship has sailed long ago.
I’m frustrated that removing bad functionality is being treated as a slippery slope with obviously bad and impossible jokes as the examples chosen.
I see a bad feature being abused, and I don’t see the removal of that bad feature as a dangerous path to getting rid of email. I don’t ascribe the same weight that you seem to towards precedent in this matter.
I’ve been working in full stack for long enough to know that history manipulation is as much a part of the modern web as images and email. I’m not trying to be flippant, that’s just the state of the modern web. Single-page apps are here, and that’s a good thing. They’re being used badly, and that’s endemic to all features. So no, history manipulation is not “bad functionality,” though I admit it’s not fully baked in its current implementation.
I accept that it’s how things are, I just personally feel as though the only way this feature could ever work as it does now is with the implementation it has now, and that the convenience of single page webapps that use history manipulation is not worth the insane annoyance of helping my grandma get out of websites that tell her that she has been hacked by the FBI.
Yeah, I get it, but like…the same could be said for emails in a world where phishing exists.
I don’t think that email and browser history are similar enough to make a meaningful comparison, honestly.
Maybe someone could say that, but I am not.
I see a specific instance of a specific bad feature being specifically abused. I don’t care to entertain whatabouts.
It’s not a whatabout, but since you have your mind made up, by all means don’t let me get in your way with facts.
I don’t think I’m disputing your facts, I was responding to the scenario you presented which was, essentially, “what about email”. I would say it’s fair that my opinion on a canonical browser history is solid and unlikely to change, though.