Discussion Overview
The discussion revolves around the possibility of coding a website in such a way that its URL does not appear in the user's browsing history, particularly comparing capabilities between iOS and other platforms like Android and desktop browsers. Participants explore technical methods, security implications, and the motivations behind wanting to hide URLs.
Discussion Character
- Exploratory
- Technical explanation
- Debate/contested
Main Points Raised
- Some participants inquire whether it is possible to code a website so that its URL does not stick in the user's history, noting that this feature is claimed to exist in iOS.
- Others argue that browser settings are client-side and cannot be controlled by a website, raising concerns about security implications if such control were possible.
- There is a suggestion that JavaScript might have effects on client-side behavior, but it is generally agreed that it cannot alter browser settings or access history.
- One participant mentions a thread suggesting that it can be done via JavaScript, but expresses skepticism based on personal experience with current browser behavior.
- Another participant references HTML5 and the History API, questioning whether any features are blocked for security reasons and expressing frustration with sites that disrupt the back button functionality.
- Concerns are raised about the motivations behind wanting to manipulate browser history, with some participants questioning the ethical implications of such actions.
- There is a mention of using jQuery to load content without affecting history, but this is contingent on the pages being on the same server.
Areas of Agreement / Disagreement
Participants do not reach a consensus on whether it is possible to hide URLs from history. There are competing views regarding the capabilities of JavaScript and HTML5, as well as differing opinions on the ethical considerations of manipulating browser history.
Contextual Notes
Participants express uncertainty about the current capabilities of browsers and the potential changes in behavior since older methods were discussed. There is also a lack of clarity on the security measures in place that may prevent such actions.
Who May Find This Useful
This discussion may be of interest to web developers, programmers exploring client-side scripting, and individuals curious about web security and ethical considerations in web design.