Timeline for Is there a userscript to mark lq/rq/cb/whatever links visited?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 23, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
Mar 9, 2017 at 18:04 | history | edited | CommunityBot |
replaced http://i1322.photobucket.com/ with https://i1322.photobucket.com/
|
|
Feb 3, 2015 at 14:24 | comment | added | Ilmari Karonen |
@BrockAdams: I think the simplest solution to that problem would be to strip the tracking parameters from the URL as soon as the page loads, as if it had been redirected. Do that with @run-at document-start and you shouldn't even have much extra latency. I've thought of maybe adding this to SOUP at some point.
|
|
Jan 19, 2015 at 22:51 | comment | added | Nathan Tuggy | @BrockAdams: There might still be a solution to that (silently double-opening the link in a hidden iframe?), but like I said: fragile. | |
Jan 19, 2015 at 22:50 | history | edited | Nathan Tuggy | CC BY-SA 3.0 |
Added screenshot
|
Jan 19, 2015 at 22:45 | comment | added | Brock Adams | Oops, never mind. That above approach won't work, because the URL in the history-list will still not match the displayed URL unless you perma-sanitize all links (messing with SE's tracking and statistics). | |
Jan 19, 2015 at 22:41 | comment | added | Brock Adams | I forgot about that approach. Since you aren't trying to fool the user, or clickjack for revenue or otherwise be Evil (like that site that rhymes with "Google"), that approach may actually be relatively easy. Still have the judgement issues though. Just trimming links is sometimes a disservice. | |
Jan 19, 2015 at 22:36 | comment | added | Nathan Tuggy | @BrockAdams: I had a few ideas about clever trimming to get the equivalent URL and then monkeypatching in the right thing when you click, but that would be fragile and a bit hard to get right. (Like most clever solutions.) | |
Jan 19, 2015 at 22:33 | comment | added | Brock Adams | The only way a userscript could do this is to keep track of every visited URL you browse on SE sites! That could get real messy, real fast. ... But a proper browser extension (Add-on) could leverage the protected history API. Both approaches would have to make judgements about what URL-parameters were equivalent though. For example, this and this are obviously the same, but this is not the same at all. | |
Jan 19, 2015 at 6:07 | history | edited | Brock Adams |
edited tags
|
|
Jan 19, 2015 at 5:32 | review | First posts | |||
Jan 19, 2015 at 6:08 | |||||
Jan 19, 2015 at 5:29 | history | asked | Nathan Tuggy | CC BY-SA 3.0 |