kaolinite

This service has been spamming developers, harvesting emails from open source repos and then emailing them, advertising the service. Really not cool.

Even though it looks like quite a cool service, honestly I wouldn't use them on principle.

Here's the email I received: http://i.imgur.com/Kf9Nv3F.png

Just a little tip: we can get that information from the product page, I think most of us would prefer if you instead introduced yourself, explained the backstory, maybe some technical details, etc.

Nevertheless, a very interesting product and congratulations on launching. I couldn't work out how big the device was, however. I was wondering whether it would fit on the back of a watch (whilst the watch isn't being worn, I mean). If this was small enough, I could see this being very valuable for watch collectors.

It was my understanding that the optimised library changes in size based on your hard drive. So if you have only 10GB of space left, say, your photo library will be reduced drastically. They need to work on this because most people aren't going to want their computer downloading 80GB of photos, but yes, I'd call that a bug.

Failing imports / duplicates is another issue I've heard about. I haven't personally experienced it and don't know how prevalent it is, but I hope they fix it soon. I don't know about library size - I've heard of people with massive libraries using Photos.app without trouble, but perhaps they had a Mac Pro or something.

As for selective synchronisation, I'd say that it won't be needed if they fix the issues (mentioned above) with library size optimisation. The point is: the user shouldn't have to worry about filling up their devices with photos. As soon as they're running low on space, Photos will reduce the library size. Now, that might not be working perfectly at the moment (not sure, works ok for me), but again - I'd call that a bug.

As I said earlier, the main problem here is whether Apple keeps working on this and gets updates out quickly. The worst problem of all would be if we don't see another Photos update until the next version of the OS (well ok, that's only a month or two away, but nevertheless). If Apple iterates quickly and keeps on improving the service, personally I'll be happy.

Very good point. Hard to know who is right without data, which I can't imagine we'll find. I know for a fact that if I were a flight attendant, I'd certainly make sure I had the latest flu vaccine, etc.

Honestly, most of these complaints just seem like bugs. I've heard a number of people complaining about speed / CPU usage problems. Genuine problem, but presumably not a design flaw. Frankly, iCloud Photos is so much better than the previous photo solutions on iOS that slight troubles at the start can be overlooked. Now let's just hope Apple fixes these problems soon. If they don't, that will be the real problem.

What drama are you talking about? I see no drama at all. There's a bit of marketing copy for a product description, but it's hardly calling it innovative or life changing - it just explains what it can be used for. And if you're referring to the fact that a dock was submitted to HN at all, it's somewhat interesting because Apple hasn't produced docks for a while, and people on HN might be interested.

This isn't showing off Apple's engineering or innovative genius or whatever, it's just a courtesy to the Apple customers of HN: here's a new product, you might want it.

There might be. I bet flight attendants take more sick days than most workers do and there are very real financial implications of a flight being delayed due to lack of staff.

There isn't much Apple technology that isn't shared between all of their products and in this case, I suspect that it's for the Maps project - which in turn will be central to the development of Apple Car.

If possible, Apple likes to have their cake and eat it too.

As far as I know, the iPhone doesn't contain an antenna per se, rather they use the frame of the phone as the antenna. I believe many other phones do this too. There are some pretty clear advantages (weight, size of device) but presumably some downsides too (which is why perhaps they're buying this company).

People are always complaining about some aspect of Apple devices where there is apparently an easy solution (latest example would be Apple Watch water-proofing) but there is always a downside, even if it isn't clear - otherwise Apple would have done it. The problem is the compromise and where you draw the line.

That's the current model I'm using, thinking it'd be cheaper for most users. I'm not doing any pre-buying yet but was planning to, however now I'm considering a subscription model.

Thanks, appreciate it. That's a very good point, I hadn't considered that. I'm going to have a think about changing it - thanks for bringing that up.

I recently launched Pleasant.io (http://pleasant.io/) for this exact problem. I wanted a simple, easy to use alternative to Google Analytics (and one that respected the privacy of me and my users). Please feel free to give it a try - any money you spend over the first 3 months is given to Watsi :-)

For what it's worth, if I'm writing a quick script I'll often write a few quick comments first (e.g. "Load data from file", "Connect to API", etc) before I start writing any code, just to plan it out. Similar to how many people will create a bunch of empty methods when creating a new class, before fleshing them out.

Why not ask them? Just send them an email saying that the offer sounds fair and you'd be happy to agree to it (assuming that's the case), but you're intrigued as to why they increased it by so much.

If I had to guess, it sounds like perhaps they had no idea how much the market rate was and then, after you countered, sought advice on this. Having learnt what the going rate is, they then offered what they thought was a fair price. Whilst it seems crazy to offer someone more than what they were asking, they might do so if they're planning to hire you full time.

Another vote for SSLMate. Used them recently and was stunned at how great they are. Definitely an SSL company for developers/sysadmins (in a good way).

Are you talking about mobile web or mobile apps? I'm only referring to transactions that take place through the web browser.

If you're talking about the mobile web though, fair enough - I find that surprising. It has certainly altered my habits.

That really would make a fantastic gift for your friend, although you're right - they are rather expensive :-)

> That claim about wristwatches not being popular...

Agreed, it certainly seems obvious. I suspect at the time there may have been some advances that allowed smaller wrist watches, and that's what allowed them to take off - however that's just a guess. Women's watches at the time were quite large and elaborate, covered in jewels and such.

There's quite a good NYTimes article you might like, though it doesn't go into much detail about Santos-Dumont: http://mobile.nytimes.com/2013/10/23/fashion/wrist-watches-f...

There's also a bit more information on the Cartier Santos watch, including its modern variants, here: http://monochrome-watches.com/history-of-the-pilot-watch-par...

Regarding the wristwatch, not quite true, but almost (I'm nitpicking, really - I recently spent some time looking into this).

The wristwatch became popular with men shortly before as they were given to soldiers at the very end of 1800s. Previously seen as an accessory only for women, the use of watches in war (as it wasn't practical to pull out a pocket watch) made them eventually become fashionable.

That said, the watch produced for Santos-Dumont by Cartier did become the first widely available watch for men, and is still on sale today, in a more modern form: http://www.cartier.co.uk/collections/watches/mens-watches/sa...

It's quite possible this changed with iOS7 with the introduction of iCloud Keychain, which enabled storage of credit card information. I've found myself buying a lot more stuff on the mobile web since then, things that previously I only would have bought on a desktop.

Whilst that may be bad, I hardly think it puts them in the same tier as GoDaddy. In fact, it seems your problem is mainly with Tucows, rather than Hover. Nevertheless, the problem with GoDaddy isn't the feature set or product offering, it's the way they treat their customers. Hover could certainly bring the price down on DNSSEC support but that really doesn't make them a "scumbag registrar". Do you really think that's fair?

It hasn't really run off iTunes for 3-4 years now. I can't remember the last time I had to launch it. Besides, whilst iTunes isn't great, if most crapware was even as good as iTunes then there wouldn't be much of a problem.

I have no experience with Namecheap at all but it's definitely worth picking a good registrar. Before I moved to Hover, I had some domains at Gandi and some at 123-reg. My most important domain was knocked offline after 123-reg failed to renew it (they said they had renewed it, invoiced me for the renewal but then didn't renew it). It took them ~5 days to get it back. Up until that point, I'd never had any trouble with 123-reg (I thought they were fine - they did the job), but then I lost access to my main email account for 5 days.

It really pays to make sure you have a good registrar.

I really couldn't recommend Hover enough. I switched from Gandi (who I was very happy with - and still am, in fact, they're a great registrar too). Their interface is great - incredibly clear, simple and fast. Their support is even better.

The only downside is the email hosting. I was used to free email hosting from Gandi so it's annoying having to pay now - $10/year/mailbox.

Huge advantage of Hover: if you have domains elsewhere, you can give them your credentials for the old registrar and they'll log in and transfer your domains over (and DNS, etc). Saves a bunch of time.

Finally, if you don't go with Hover, go with Gandi. Their interface isn't nearly as nice but the support is good and they won't screw you around.

They probably won't mind if you choose to work on Linux (and as others have said, if they do it might be a bad sign), but I'd think about a few things first.

1. Are they relying on any OS X software? For example, at my last job the front-end developers relied on Codekit, an app for compiling CSS, etc. Now, it could totally have been replaced with Gulp or similar - but do you want the first thing you do when you join the firm to be proposing they alter their workflow around you?

2. Whilst you work best on Linux currently, perhaps you could learn to use a Mac too? Then you have experience with both platforms. You could always use Linux in a VM as a backup too.

3. If you have issues as the only person running Linux, you'll have a harder time fixing them and people will have less time for you. I've seen this a number of times. People choosing something different to the rest of the team because they prefer it and it improves their productivity, only for it to cause trouble (rarely their fault) and them get looked down upon because of it.

Overall, it probably won't matter - but it might be worth thinking about it. If there were some other people running Linux too, I'd say go for it. If you're going to be the only one, you might end up making too many waves - it's up to you if you're comfortable with that.

People said that charging your mobile phone each day was ridiculous too, but now we all do it. Besides, I wind my mechanical watch each day - that's never been a problem.

Obviously, whether you like the look of current smartwatches is your view, but lots of people - including those in the watch world - are praising Apple Watch for aesthetics and build quality. There are some nice looking watches on the Android Wear side coming out too, although I question the choice of circular display.

Here's the Apple Watch next to a Patek Philippe perpetual calendar, arguably one of the finest watches in the world. Honestly, whilst it will never match such a classic, it stands up pretty well.

http://cdn.hodinkee.com/uploads/block/inline_image/content_i... http://cdn.hodinkee.com/uploads/block/inline_image/content_i...

I recently did a very small amount of advertising on Twitter and managed to reach 20,000 people for around $15 which I thought was quite reasonable, although I haven't tried any other platforms yet. You don't pay for views, only interactions, so it can be quite affordable.

Does that really matter? Log files are often unimportant when they get over a month or two old, what is it in your log files that has to be kept for 40 years?

Longevity of log files hardly seems like a reason to pick an otherwise inferior format.

As soon as you push something sensitive to a public GitHub project, you need to immediately assume that it has been noticed and that someone is on their way to try and exploit you. There's a very high chance that it's the case, especially with API keys for services like MailGun, etc, which can be used by spammers.

Attackers are using the Github firehose to look for credentials. You need to immediately revoke them.

Thanks for replying and thanks for the article too - great read with some fantastic photography.

Really interesting to hear how you provision servers, had no idea that OS X Server came with tools for that, but it certainly makes sense. I wouldn't have thought Apple would have put much time or thought into creating tools for large deployments, but glad to hear that they have.

Three possible reasons I can think of for doing this over using PCs or Linux servers:

1. Using the same operating system as the developers of the software, plus access to Apple's fantastic imaging libraries.

2. The Mac Pro, whilst expensive, is good value for money. The dual graphics cards inside it are not cheap at all. As servers with GPUs are fairly niche, this might actually be a cheaper solution.

3. The form factor. Even if you could create PCs that are cheaper with the same spec, they'll use more power, possibly require more cooling (Mac Pro has a great cooling architecture) and will take up a lot more space.

I'd be very interested in hearing how they manage updates and provisioning, however. I can't imagine that'd be much fun on OS X but perhaps there's a way of doing it with OS X Server.