SoylentNews is people
SoylentNews
posted by
Woods
on Thursday May 01 2014, @07:37PM
from the now-all-those-URLs-I-memorized-are-worthless dept.
from the now-all-those-URLs-I-memorized-are-worthless dept.
Yesterday, a Canary build of Google Chrome removed something kind of important from the browser: the URL. Basically, it only shows the domain and leaves the rest of the URL bar as a search field.
Allen Pike, a blogger who writes "about technology and crap like that" suggests burying the URL like this will probably have some usability and security benefits. From the article:
More recently, browsers started hiding the URL scheme. http:// was no more, as far as most users were concerned. In iOS 7, Mobile Safari went even further and hid everything about the URL except the domain. With the Chrome "origin chip" change, the URL will move out of the field entirely, to a tidy little button that many users will never even realize is clickable.
This discussion has been archived.
No new comments can be posted.
Chrome Experiments with URL-less Web
|
Log In/Create an Account
| Top
| 67 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Insanity is considered a ground for divorce, though by the very same
token it is the shortest detour to marriage.
-- Wilson Mizner
(Score: 0) by Anonymous Coward on Saturday May 03 2014, @12:31AM
I don't think there is a need for a warning (in the web browser), if the domain registrars simply do not allow letters in domain names that look like other letters... in the swedish .se example the letters they allow are åäö and various accents, they also allow hebrew letters but they are not allowed in the same domain name as the latin characters so there is no risk of them being used to look like another character.
(the web browsers do have a white list of domain registries that prevent IDN homograph attacks, showing punycode for others)
(Score: 1) by Aiwendil on Saturday May 03 2014, @12:32PM
Interesting info about what .SE allows in their names - thanks.
I used swedish as an exmaple of false positive with a utf8 warning.
(For a thing I've stumbled over in japanese)
A fun case where I would appreciate a warning for utf8 would be in the cases of dash/minus/ichi/hyphen , they are four different signs, and even when reducing "visually similar" we still have the problem with ichi (unless we plan on either banning japanese numerals or allowing equal-sings (ni)).
This problem is compunded by the japanese habit of using arabic numerals instead of their own even when writing in kanji (so it makes sense to keep the minus/dash sign when writing in kanji, it also makes sense to keep the non-formal ichi-symbol, and it makes sense to keep them separate (and to just disallow the non-formal ichi would cause problems with 'ni' unless one plans to allow equal-signs, and then we have the question of how odd dash and equal would look next to 'san')).
Then again, in this specific case it probably would be better to simply enough write utf8 and ascii in different colours - which probably is a better solution to being with.
So, I retract my idea of having a 'red 8'-warning and replace it with an idea of simply showing utf8 and ascii-characters in different colors (or regular/bold).