comeonnow

Potential reason is that they need see how their tests affect screen burn. They mention they specifically need Mac hardware so this could be why they specifically need retina screens.

I agree I think this approach would appeal more to me as a user. I'd also set the options as:

1) Happy to donate 2) No, and don't ask again

I don't understand why a user would access a randomly created directory that is only mentioned in the robots.txt file. Can you explain as to why you'd think they'd stumble across this?

How about instead you discussu a SLA (Service Level Agreement). For example you agree that emails / calls are to be acknowledged or responded within 1 hour during 9-5 Mon-Fri for £/$XXX per month.

You could go a step further any have different levels, so for a higher monthly rate you'd respond within 30 minutes, etc etc.

Any idea on who is responsible for this micro-site?

I find it strange that there's no information on the author, sources, references, attribution, or credits on the page at all (other than the WordPress theme attribution).

In a way I'm in a pretty similar situation. I have a desktop for my day job, and an iPad mini 1 (1st gen) for evening browsing (so that I don't get sucked into work if I use the desktop machine).

There's been 3 updates to the iPad mini since mine, and felt zero need to upgrade. I'm very happy with my ipad, and most certaintly don't think it's meh, it's just apart of my evening cycle that I don't even think about any more.

Lots of users on Twitter saying to delete your account, but is there any proof that this will exclude your account from the API?

Totally, but in terms of readability for proof on concept, I can see why the author chose PHP. I think the repo was more for showing the vulnerability rather than an actual tool that could be used right out the box.

I'm sure others will find this reminiscent of the Minecraft in-game sounds, which makes me wonder whether they have similar logic to create on the fly, or just a pre-recorded looped audio file.

I'm assuming the later due to resources.

There wasn't a real update other than the TouchID, why would they update the iPad Air but not the Mini, in terms of chips and cameras?

I for one was hoping for an upgrade to this range in particular, and the fleeting mention in the stream was a bit shocking.

I have the 1st Gen mini, and didn't see enough to upgrade to the retina, and was hoping for a chip upgrade and camera upgrade, but alas nothing.

I almost feel as if there are 2 outcomes here; 1) the mini gets an update in March-ish and has some kind of A8Y chip especially for the mini, or 2) that is the last update we ever see for the mini

I built a scraper around 3 years ago (been through a few usernames since then), and I've had to change it once 3 months ago because the HTML output added quotes around HTML attributes.

Even though it's read only, I'll continue to use my scraper rather than the API simple because it's one request, rather than the API would require one request for the top IDs and then one call per story, so it would be 31 calls instead of just 1.

Unless I'm missing something, it seems fairly poorly designed for top stories, and non existent for new stories.

------

EDIT: Looks like I missed the text about updating to a new rendering system in 3 weeks time, and to iterate designs faster to allow mobile friendly theming. Looks Like I WILL be updating to use the API

I agree, in its current form I don't have any issues regarding bugs or stability, but assuming Yosemite support will be needed some time soon, as well as potentially a Mac App Store integration.

Other than that, I'd say it's a good candidate for a 1.0.0 release, so I'm not sure exactly what the need for $20k is, unless it's to reimburse for time already spent?