4 ms·
There are all different links: https://medium.com/reboot-leadership-resiliency/how-i-burned-10-million-dollars-so-you-dont-have-to-4e9e83754ce9#.f6ckizs5s
by user5994461 10y ago
There are all different links:
https://medium.com/reboot-leadership-resiliency/how-i-burned-10-million-dollars-so-you-dont-have-to-4e9e83754ce9#.f6ckizs5s
https://medium.com/reboot-leadership-resiliency/how-i-burned-10-million-dollars-so-you-dont-have-to-4e9e83754ce9#.xp1acya7o
The last part of the url after the "#" symbol should be ignored for deduplication.
- carlosdp 10y agoThat wouldn't necessarily work for every site though. Some JS single-app routers default to using the # symbol as a routing delimiter instead of slashes.
- user5994461 10y agoPoorly coded JS applications will experience issues. Sounds like an acceptable downside.
- lucideer 10y agoJS single app routers is not the issue: these can opt for historyState instead. The issue is normal HTML pages with anchors, and possibly with no JS. This is a very normal age-old standard feature of web hyperlinking. It's not a weird new artifact of badly coded apps as someone commented below.
- user5994461 10y agoCare to explain why this is not a problem of bad anchor? I don't understand why that page should be giving unique anchored links to each user. As far as I recall. Anchors belong to an HTML page, it should be okay to filter by the page and not each individual anchors within it.
- lucideer 10y agoI wasn't commenting on this particular example, just pointing out that for most caseses the use of anchors in the URL is normal and functional and not just a JS SPA thing.