I actually created and launched an API on hacker news about 9 years ago which does this, you can check it out here: https://linkpeek.com
My service makes one request and caches the result. Using Pyramid (Python) and Nginx. Lots of the code is open sourced in various libraries.
The problem with trying to sell this tech is that all the biggest players build their own in-house solution, so the target market is really smaller sites, but they have a hard time paying, and also there is a lot of competition in this space now.
Which one should we keep?
Wait, does this mean you can get the IP of most people you can contact on whatsapp by just sending them a link and waiting for their phone to check that link?
I can think of plenty of ways this could be abused!
You can also get their online/offline state by repeatedly requesting their client re-sends you their profile image, even if they have read receipts turned off.
If you're quick enough, you can see it in action:
Paste a link in a WhatsApp message. The preview might take about half a second to load. Hit 'send' before the preview has loaded, and it'll never show for that message.
Paste the same link again, but wait for the preview before hitting send. It'll stay attached to that message.
Facebook makes one request and then caches the result. Other servers may not store the result.
TL;DR, the app establishes a TLS connection directly between your phone and the site, but routes it through a proxy on Signal's server, thereby hiding your IP without being able to view the URL. I imagine Whatsapp works in a similar fashion
That means I can do the same with `og:image`, give a nice middle finger when linking my website (hey, a bit of 90s fun here)
“Microbrowsers are a class of User-Agents that also visit website links, parse HTML and generate a user experience. But unlike those traditional browsers, the HTML parsing is limited and the rendering engine is singularly focused.”
user agent ~= browser
agent ~= microbrowser
On the other hand, since this one blogger seems to be the inventor of the term "microbrowser", it's still going to be ambiguous: easily confused with potential alternative definitions such as "lightweight browser", "headless browser" (e.g. selenium webdriver), "browser with low market share", etc.
Are there good documents regarding "capitalism" (I guess; constantly reinventing better wheels) vs other systems (reusing already designed wheels, however square), in domains other than financial: what the tradeofs are, how much worse your existing wheel can be before you start to feel it, potential for innovation, etc. Free software might side with the later, but I'd like an analytical exploration.
This is for a hobby project, so rewriting it to do server side rendering etc. is not an option.
Rewrite it to do server side rendering.
Sorry if this seems facetious, but if you want it to be accessible, it needs to be server-side rendered.
Some crawlers have some (limited) JS-rendering abilities; notably Googlebot; but it's not full. Some crawlers may use a fully-fledged Chrome-headless but latency would make this uncommon.
In general, JS-dependent SPAs have always been a terrible terrible idea for anything public facing that needs to be crawled (they're fine for web applications, not for web pages).
I also might consider serving some other non-game pages statically, like the leaderboard, user profiles, etc.
I doubt you will need to rewrite it if you use React or VueJS (or any other big framework) as they have SSR support.
For React it seems that Gatsby is very popular: https://www.gatsbyjs.org/
Depending on the complexity of your hobby project it might even be feasible to write a simple script that runs node, outputs HTML files for each of your pages, and uploads them to online storage.
You might look into GitHub Pages too, although I'm not familiar with its capabilities: https://pages.github.com/
Now in my own product  I was a long time without implementing the right tags on my landing / marketing page, and blog posts. I wish I would have done this since I launched, but just started doing this 2 months ago since I switched to Gatsby for our marketing page. They have a very easy to implement SEO component , that allows you to focus more on the content than on tweaking the meta tags for social.
Sure felt silly.
That’s saying quite a lot.
The top comment on that third article about the brewery explosion in Vancouver could just as easily be about Denver - the story is nearly the same. As I understand it here in Denver, a change of law make it much easier for breweries to operate tasting rooms which can be quite profitable and spurred massive growth.
HN is perhaps the website where I find whatever I'm trying to, if it exists.