Whereas other links (e.g. the immediate next one to arxiv) seem unaffected.
edit: That was a red herring. It seems to redirect all .pdf links I try that don't point to a valid snapshot. Very interesting.
150 karma · joined December 14, 2016
Whereas other links (e.g. the immediate next one to arxiv) seem unaffected.
edit: That was a red herring. It seems to redirect all .pdf links I try that don't point to a valid snapshot. Very interesting.
The main difference is that you're exploiting your own weaknesses, rather than others'. Limitations in typing speed, information gathering, pattern recognition.
Maybe there's a critical mass of Linux users that will force AC support. Maybe new cheating paradigms (DMA) will obsolete local AC. I suppose one of those could happen in the next 10 years.
* "We've received reports about the latest content" - weird copy
* "which doesn't meet X Terms of Service" - bad grammar lol
* "Important:Simply ..." - no spacing lol
* "Simply removing the content from your page doesn't help your case" - weird tone
* "We've opened a support portal for you " - weird copy
There should so many red flags here if you're a native english speaker.
There are some UX red flags as well, but I admit those are much less noticeable.
* Weird and inconsistent font size/weight
* Massive border radius on the twitter card image (lol)
* Gap sizes are weird/small
* Weird CTA
An entire article about a beta feature they haven’t even seen? I normally wouldn’t read Ars but I’m on flight with nothing else to do and still feel swindled
Look at the critique [0] and then look at the code [1].
[0] https://web.archive.org/web/20250423135719/https://github.co...
[1] https://github.com/ricci/async-ip-rotator/blob/master/src/as...
It happened outside of Alexa too. Every team with a public facing product was directed (it seemed) to come up with some sort of Alexa integration. It was usually dreamed up and either a) never prioritized or b) half assed because nobody (devs, PMs, etc.) actually thought it made any sense.
The uniformity in the NK photo is bizarre.
I’m similarly surprised to see such an ingrained skill undergo such rapid change. And it’s funny because for me prettier was originally just meant to fix the chaos that is every dev having their own style/editor preferences.
It seems like it would solve most of the PWA issues. Although I vaguely recall reading that Apple is not too fond of apps that are basically just wrapped web views.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Scrolling is such a natural behavior for internet natives. Being able to leverage a large screen to visually compare things has its place, but the article uses a horrible example:
> Our condensed product page prototype took the same information from the original dispersed page and arranged it in a 2x2 grid that allowed users to compare multiple services simultaneously, without having to remember the details of each service.
What's to compare? They're disparate services.
I do like the example of the product specifications. But that was more of an objective usability issue: requiring more clicks for more information.