Second-rate fruit.
Check out @Eurovision and @CollinsSubmissions
I don't have any hidden profile links, you're not missing anything.
just now i went to a wikipedia article, and it showed a link to another article i'd read before in purple. and like. how the fuck does that WORK. do they have to keep your entire browser history in memory and perform a lookup for every \<a> tag before the page is rendered??? how is that not prohibitively expensive???
there probably is a simple answer to it (something something hashmaps, if i were to hazard a guess) but i'd never thought about it until now tbh
They've been doing this since the 1990s, it couldn't be too complex.
huh went searching and turns out websites can't check your browser history anymore, because it'd be fucked up security-wise. which is why :active has limited styling options. as for how it actually works i couldn't find anything and don't really know enough about computers to hypothesize anything. interesting though :0
This question of yours may have some relevance to the fact that browser histories have been weird non human-readable database file formats since the beginning of time.
My guess is that they were probably using tries. It's not that much when it comes to memory usage (most URLs share big prefixes with other URLs).
