How do you turn this feature on? I don't have it.
Why it took a long time to build the tiny link preview on Wikipedia
141–150 of 255 posts
Re: Why it took a long time to build the tiny link preview on Wikipedia
#142When we do finally send people to Mars I think they'll appreciate having a local copy of Wikipedia with them. This would be one of the top 10 resources beyond what's required to produce air, food, water, and heat. Otherwise, something comes up and any question you have could take almost an hour to get a response from someone on earth.
Wikipedia is, by my estimate, to 90% about animals, places, historic places, historic animals, historic people, "notable" living people, and so on. How's that going to be relevant on mars? And who's going to vet all the articles?
Re: Why it took a long time to build the tiny link preview on Wikipedia
#143How do you turn this feature on? I don't have it.
Enable js ?, Or if you are logged, must turn it on
Re: Why it took a long time to build the tiny link preview on Wikipedia
#144When we do finally send people to Mars I think they'll appreciate having a local copy of Wikipedia with them. This would be one of the top 10 resources beyond what's required to produce air, food, water, and heat. Otherwise, something comes up and any question you have could take almost an hour to get a response from someone on earth.
Wikipedia is, by my estimate, to 90% about animals, places, historic places, historic animals, historic people, "notable" living people, and so on. How's that going to be relevant on mars? And who's going to vet all the articles?
Maybe, but those 1% remaining (thousands of articles) about physics, engineering, and so on are a goldmine if you are stranded without anything else.
It would be dumb no to take it as the complete dump is < 1Tb
Re: Why it took a long time to build the tiny link preview on Wikipedia
#145There's a lot of negativity in these comments (which is to be expected, as it is still HN after all) but I've been using the preview boxes for a while now and have to say that I absolutely love them. I use Wikipedia a LOT for primative/secondary research and being able to even just figure out the dates someone lived, the very basic information, or even sometimes just a photo saves me from so many instances of new-tab opening of links that I have to remember the context of after I'm done reading the passage. Really happy to see this is more available now
EDIT: This is unrelated, but after reading more of the comments, I legitimately can't believe how absolutely disrespectful and hateful so many of these comments are in here. I appreciate this site as a place where you can express your opinions, even if they aren't just placid support of whoever the OP is, but I really don't want to see this community dive further and further into the echo chamber of hate that it seems to be becoming.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#146Wow. Had just read that and then saw the feature first time while browsing over a list page. Was moving my curser down the list and when ever I wanted to click a link, the above link hat popped up the layer, highjacking my click and leading me to the wrong page. What a great way of destroying the user experience with a beautifully over-engineered feature that is utterly crap while actually trying to use the underlyin…
I have a habit to select some text in a page when I'm reading it. And I hate websites that trying to immediately interact with me when I'm selecting a text (usually it's "fix a typo" or something similar).
Hate is a pretty strong word and kind of irrational.
Textselection was probably not intended as reading aid, so don't be disappointed if it is abused to actually, you know, select text to do something with it.
I agree, user scripts can be presumptuous and what not. I used to read with text selection the same way, and even reacted repulsed at advertisement hover pop-ups. But somehow I don't do it anymore, so I don't care as much.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#147Earlier quoted context omitted.
SO's hot network questions was so bad that I enabled my ad-blocker on SO and added a custom rule to hide that part of the page. At least now when I go to find an answer on SO without falling in a 30-60 min rabbit hole.
Please post this rule, it would be very helpful. What’s frustrating is that this has been brought up as an issue on StackExchange and rejected as WONTFIX.
I'm using uBlock origin. The rule is:
stackoverflow.com###hot-network-questions
Edit: more on this: https://meta.stackexchange.com/questions/222721. Linked in one of the answer is an extension: https://chrome.google.com/webstore/detail/sidebaroverflow/lh...
There are also other solutions on that page.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#148Earlier quoted context omitted.
SO's hot network questions was so bad that I enabled my ad-blocker on SO and added a custom rule to hide that part of the page. At least now when I go to find an answer on SO without falling in a 30-60 min rabbit hole.
Please post this rule, it would be very helpful. What’s frustrating is that this has been brought up as an issue on StackExchange and rejected as WONTFIX.
These rules work for me, using uBlock Origin:
stackoverflow.com###hot-network-questions
stackoverflow.com###feed-linkRe: Why it took a long time to build the tiny link preview on Wikipedia
#149Why so much effort on a feature that doesn’t and probably can’t work on mobile? Were they happy enough with Safari’s 3D Touch preview which does more or less exactly this? (Only with a full screen preview so they don’t have to get into the messy business of summarizing pages.)
I imagine it's because they see high readership on desktop browsers.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#150Earlier quoted context omitted.
Wikipedia's markup is just terrible for trying to do any sort of scraping or analysis. I once tried to write a script that pulled the latest version of macOS from the sidebar of this article[1] and I gave up because it was difficult and brittle in a way that made it nearly impossible. I'd probably have better results parsing the HTML with a regex. Likewise, I know a friend who literally had to scrap an entire project…
How hard did you try? These are not hand-written pages, and their output is actually pretty clean compared to the crazy things I've tried to scrape. They have tons of APIs to access the backing data, and that should be your first stop. Even if you insist on scraping, in your case you're just looking for a whose immediately preceding contains the text "Latest Release", and that's something any XPath-based scraper can…
> Even if you insist on scraping, in your case you're just looking for a whose immediately preceding contains the text "Latest Release", and that's something any XPath-based scraper can give you straight out of the box
Sure, until it changes. Here it is in Jan 2016 when it was included in the opening paragraphs as the text "The latest version of OS X is ".
https://en.wikipedia.org/w/index.php?title=MacOS&oldid=69769...
And here it is in June 2016 where that sentence was changed to "The latest software version is "
https://en.wikipedia.org/w/index.php?title=MacOS&oldid=72528...
Then around September 2016 it was moved into the sidebar using the template you linked. It looks like that template has been a consistent and reliable element for this since 2012, but then why was it only used in the OSX infobar in middle/late 2016? How else would anyone have known to find it?
And this is just OSX, what if OP wanted a web page that tracked the latest stable release for 20 different OS's? It ends up being pretty frequent maintenance for a small project.