HNHacker News
TopNewBestAskShowJobs

drewcrawford

4,834 karma · joined June 13, 2008

AI tooling and systems/SDK engineer · Rust, WebAssembly, Swift/Apple platforms · wasm-bindgen contributor · building AI Bot Mafia (botmafia.games) · sealedabstract.com · github.com/drewcrawford
submissionscomments
drewcrawford··on CoreOS is building a container runtime, Rocket
I've been involved in that ticket since the dark ages. There's a philosophical disconnect between how (some) people want to use Docker and how the maintainers want it to be used, and it comes to a head in that thread.
drewcrawford··on Postal Service almost never denies mail-surveillance requests
> where we should insert things into the Constitution that aren't there, "because change."

Not sure if sarcastic, but how is it possible not to do this?

e.g. the 1st Amendment grants the right to a "free press". Are there really constitutional literalists who believe that because the word "press" as used in the 18th century contemplates the operation of a machine that imprints ink onto dead trees that we should not consider wsj.com within the scope of its protection?

Or consider that the Constitution uses male-gendered pronouns to describe the requirements and duties for the offices of Congress and the President. Are we then to infer that only men can hold these offices?

It seems to me that everybody interpolates the Constitution to some extent, and the difference is a question of degree. So quite frankly I'm puzzled how it can be an accusation against someone that they interpret the Constitution freely, as if the real moral high ground is a the belief that e.g. judicial review doesn't exist.

drewcrawford··on Show HN: Timely for iPhone – Scheduling and Time Tracking, Simultaneously
And an iOS app I wrote back in 2008. It's defunct now, but these guys were aware of it when it was still a going concern, and used the name anyway.
drewcrawford··on Amazon Prime Members’ Newest Benefit Is Free, Unlimited Photo Storage
> I'm willing to pay $5 for 100GB.

Well there's the issue. S3 rates are $3 for 100GB, which leaves $2/mo to provide the value-added services you enumerate.

You'd need 5k monthly subscribers just to hire 1 engineer.

drewcrawford··on Show HN: Professional sound effects for UI projects
It's better. I still think that "contributes to the core value" is vague.
drewcrawford··on Tim Cook Speaks Up
The nature of politics is that if we want to accomplish things, we have to work together. When you throw out statements like

> If conservative politics is directly linked to bigotry I see no reason we should support it. Perhaps the fiscally conservative, small government political groups should work to dissociate their ideas from intolerance.

All this does is create animosity with moderates who do not consider themselves linked to bigotry, and it does not advance your position, except among people who already agree with it.

If you don't want the support of these moderates then that is one thing. But that raises the question of why you would engage them, if not to garner their support.

drewcrawford··on Show HN: Professional sound effects for UI projects
I mean it's true that your terms are standard for the likes of Getty Images. But I think what this conversation reveals is that the userbase of Getty Images and software developers don't have a lot of overlap.

I think if you want to target a software developer audience you will need a single-project, multiple-user model. The majority of projects where we would use this are a revolving door of contractors, and nobody is going to do the accounting to figure out how many licenses that is.

drewcrawford··on Feds identify suspected 'second leaker' for Snowden reporters
This is probably a trial balloon [1], a tactic of leaking information in order to gauge the reaction.

For a long time in US foreign crime/terrorism policy there has been a sense of "find our enemies, no matter where they are, no matter the cost." Changing that positioning would be a big U-turn in rhetoric.

By floating this change under the guise of "sources close to the matter", they get to gauge the reaction of interested parties while maintaining cover of deniability if it's poorly-received.

[1] http://en.wikipedia.org/wiki/Trial_balloon

drewcrawford··on Bill Gates answers questions about Java during a deposition (1998) [video]
From 32m 50s, one of the most wonderfully pedantic exchanges I've heard:

Q: Did you send this email Mr. Gates, on or about Aug 8, 1987?

A: I don’t remember sending it.

Q: Do you have any doubt that you sent it?

A: No it appears to be an email I sent.

Q: You recognize that this is a document produced from Microsoft’s files, do you not?

A: No.

Q: You don’t?

A: Well how would I know that?

Q: Well, you see the document production numbers down at the bottom?

A: I have no idea what those numbers are.

Q: Do you recognize this as the form in which email has been printed out by Microsoft?

A: I don’t know what that means. All email printed by anyone looks just like this. So the fact that it looks like this doesn’t give me any clue as to who printed it.

Q: Well, let’s begin with that sir. E-mail printed out by other people are not stamped with Microsoft confidential stamps and Microsoft document production numbers. You would agree with that?

A: That has nothing to do with printing out.

Q: Do you understand my question sir?

A: Nope.

Q: Okay. Do you see down at the bottom where there are “confidential” stamps, and a stamp that says “Attorneys only”, document production stamps? Do you see those?

A: I see the stamps. I can’t characterize whether they’re document production stamps. To me they look more like you’d see on a prisoner’s uniform.

Q: You don’t have any knowledge about these stamps, it is your testimony? You don’t know what they are?

A: I’ve never seen a stamp like that. I’ve never used a stamp like that.

Q: Haven’t you seen stamps like that in every single one of the documents that you’ve been shown during this deposition?

A: (To counsel) Can you get me all the exhibits?

drewcrawford··on Greenpeace deluges Amazon Fire Phone with one-star protest reviews
Hang on a minute. I've reverse-engineered icloud and I have personally verified that it is hosted, in significant part, on AWS and Azure.

Is Apple buying some kind of carbon offset? Or has Greenpeace gotten the information wrong? Or did things change in the year or so since I looked at this?

drewcrawford··on TestFlight Beta Testing
Good point. Better now?
drewcrawford··on TestFlight Beta Testing
Tester? Seeking tester? I'm running a list to connect developers to people who want to test their apps.

All feedback appreciated.

http://sealedabstract.com/betalist

drewcrawford··on U.N.C. Investigation Reveals ‘Shadow Curriculum’ to Help Athletes
Collegiate athletics is organized under a league called the NCAA. The NCAA sets rules requiring players to have certain ACT/SAT scores, GPAs, prohibit players accepting compensation for participation, etc., and there is a complicated enforcement division that metes out discipline for violations.

Schools can technically do whatever they want, but in practice this would put them in violation of agreements with the NCAA, they'd get kicked out, and then they'd have nobody to play against.

drewcrawford··on Mac App Store: The Subtle Exodus
Suppose you have a video converting app. Further suppose your headline new feature is converting 2x as fast as the old version, pretty much the holy grail of video conversion software.

In the MAS you have a set of bad choices:

A) Release the upgrade free to everybody. Great for them, bad for you.

B) Make the new encoder an IAP. Problem is, now you are maintaining "old" code that you may not want to maintain anymore. You may need to wrestle with the old encoder to get it compile for new versions of the compiler, etc. You have to fix bugs that occur with the old encoder and new, unanticipated changes in OSX. If you're still compiling and uploading it every month you can't plausibly claim that it's no longer supported.

C) ship the new encoder, but cripple it so it's slow until users upgrade. This seems capricious. Also, you can't get exactly the performance of the old encoder; you'll either overshoot or undershoot. And the nature of the MAS is that user's can't effectively downgrade, so they'll be SOL if you're wrong.

D) Remove the app from sale and submit a new app. You're wiping your slate with links, app reviews, etc. You also lose customers, who don't find out about your shiny new version. OmniGroup pursues this strategy, and they lose a lot of revenue from me (an avid user) because I completely miss certain upgrades because I don't hear about them. I can't imagine how it is for marginal users.

E) Don't update the app after all, because in spite of the fact that 2x video encoders obviously add value to the world, the MAS adds too much friction to make it a viable business. I would argue that the majority of iOS and Mac apps face this sad reality at some point in their lifecycle.

I submit to you, that if you manage to write a video encoder that is 2x faster, that should be the hard problem. The hard problem shouldn't be to figure out how to structure your upgrade pricing. But with the MAS, it is.

drewcrawford··on Belkin Breaks Its Routers Worldwide, Issues Temporary Fix
What would you suggest? Placing the question of whether or not their products continue to work in the hands of third parties?

I think there is a conversation to be had here about the proper way to tie add-on services (which are inevitable) with one-time-purchase products. Consumers want some indication of whether they can reach the Internet, but this really requires some ongoing cost on the router manufacturer's part, which cannot be recouped indefinitely from a one-time hardware sale.

we face a similar crisis in mobile apps. Apps increasingly require backend services to provide core functionality, which just isn't sustainable indefinitely with a fixed-price model. Inevitably when these companies are acquired, the backend shuts down, and people lose the product that they "paid" for.

I think in the long-term, we are going to have to move to a subscription-based model where people are paying regularly for things they used to buy one-off. But in the short-term, you can have an endless stream of VC-backed companies who can afford to take on that cost for short periods. So anyone who actually broke rank would get beaten back pretty hard by the market.

drewcrawford··on With Dry Taps and Toilets, California Drought Turns Desperate
We have a system like what you describe here, but for electricity.

The "problem" is that the large users go off the grid (via solar, etc). Well, that is not a problem. The problem is that this introduces variability into the grid. That variability is expensive to smooth over, with the result that it can actually be more expensive as a fully loaded cost to supplement your power with solar than getting it from the grid, due to the equipment needed to manage the sun's mood swings.

The result of all this is it is really hard to get the incentives right for pricing electricity. I suspect the same is true for water; it is hard to store, there are demand spikes, and there are things like private wells that have weird effects on the water available to everyone else.

drewcrawford··on Beyond Objective-C, Beyond Swift
With regard to the first two of these points, Databases / Persistence and automated REST APIs I fully agree with the problem and I'm working on it pretty hard. My e-mail's in my profile if you want to chat.

However, the nature of writing a good, broad, solution as a third party is you have to capture some senior engineers for long hours, which costs money. And it's not clear to me if there's enough money available, for a third party to build the kind of broad-reaching solution that would be nice to have.

drewcrawford··on An Analysis of the CAs trusted by iOS 8.0
This is a controversial opinion, but I am actually of the view that SSL is structurally unworkable against nation-state-level adversaries. There are too many dark corners and not enough eyes, and you can't dig your way out of complexity with a volunteer standards committee.

I am working on the problem (and by that I mean "it's in private beta"). Mobile is sort of a unique opportunity because a typical mobile app doesn't have the same interoperability requirements as the web more broadly.

However, it's hard to sell, which explains why nobody does it. First it's hard to sell commercially, which you really need if you want it audited by people who know what they're doing. But it's hard to even give it away, because nobody wants to be the test pilot when it comes to security.

Solving this requires a level of cooperation that we may not have as an industry right now. That may mean dark days ahead.

Email in profile, if you want to chat about it

drewcrawford··on What “technical” concerns do I have with systemd?
osx guy here.

Yes and no. It's true that OSX uses a variety of separate daemons, that run in different pids.

However they are all "required", "packaged together", "part of one source tree" and "shipped by a single vendor". In this respect they are a lot like systemd.

In fact it is arguably a lot more integrated. Both Python and Ruby are OSX dependencies. systemd isn't even close to that much of a power-grab.

drewcrawford··on How Apple Pay works and why it matters for developers
My understanding is that this operates on basically the same principle as RSA SecureID. You have an unlimited-use token stored in a dedicated chip, that for all practical purposes is impossible to access, short of, let's say, a scanning electron microscope.

That chip, with its unlimited-use token then generates one-time tokens which are sent over the payment network.

In theory the chip could issue an arbitrary number of tokens if criminals got ahold of it. But in practice, it stores a little bit of the data it needs to make a token in the neighboring TouchID chip, which operates on essentially the same principle (stores fingerprint data and missing payment data in secure hardware location, only lets it out if fingerprint sensor looks good).

To summarize you have to steal both the phone (or both chips anyway) plus the fingerprint information so the chips are useful. But wait, you say--I did steal the fingerprint data! The user left fingerprints on the back of the phone!

Well, you've got me there. But hopefully by the time your very sophisticated gang of gloved thieves has bagged and dusted your phone for prints, you've made your way to iCloud.com and revoked the phone's forever-time token, so all future one-time tokens will be considered invalid.

Keep in mind, the standard being replaced here is one where you carry all your payment information around in your pocket in plaintext. This scheme is a massive improvement on that. There's an old saying that seems relevant here: I don't have to outrun the bear, I have to outrun you. There's tremendous amount of value in being marginally safer than the next guy.

drewcrawford··on Urgent security warning that may affect all internet users
> Where are we with replacing the password?

The state of the art of the technology, in my opinion, is GRC's SQRL: https://www.grc.com/sqrl/sqrl.htm

However I think you have captured something essential in the idea that Mozilla Persona "failed to catch on", and it wasn't, as far as I can tell, for technical reasons.

The real problem is that any change from the username/password system has a cost (in programmer hours, and support retraining, etc.) and so long as "nothing is broken" it is hard to justify diverting funds from features that are customer-visible to providing a defense against an attack that is arguably the user's fault anyway (password re-use).

To me this issue is sort of a monument to the strange insincere lipservice we pay to technology and technologists. Of course technology is business-critical and of course we work to hire the best and brightest, etc. But somehow organizations keep storing passwords in plain text in spite of the fact that engineers who work there know better.

drewcrawford··on Cider Project: Run iOS apps on Android
I actually know the engineer who used to be responsible for porting some of the technologies you're talking about to non-Apple platforms.

According to this person, the barrier is not some strategic lock-in plan at Apple. The barrier is more about business incompatibilities.

For example. It's fully possible for Apple to ship an iCloud SDK for Windows. But the way iCloud works is, it's integrated deeply with each application. It is believable that your average iOS app, or your average Mac app, would be willing to integrate with iCloud's SDK. But is it believable that your average Windows app will? Will Microsoft do the work to integrate the iCloud SDK with Office on Windows? Of course not! The idea is preposterous.

Far more likely is that Microsoft's own SkyDrive or will become standard on Windows, or maybe Dropbox will, which is designed in such a way that it doesn't have to integrate with anybody's product. Apple could have designed iCloud in a way that didn't require third-party support, and maybe they should've, but they didn't. And anyway that would be a completely different thing than the way iCloud is used right now.

Apple has the willingness, particularly post-Jobs, to license some things to other platforms. Especially if it grows their own ecosystem, and a lot of Apple's stack falls into that category. But getting the deal done has more ingredients than just Apple being willing and some end-user who wants it. You can't say, merely because there is no technical barrier, that clearly every time an Android user buys a book from Kindle instead of the iBookstore that Tim Cook cackles with glee. I pretty much guarantee he'd be interested in getting a deal done on that.

drewcrawford··on Lime Text: Open Source Sublime Text clone
The real issue is that of nomenclature. If you are a professional software developer (ST target audience) then you are careful about how you use a #1 development tool that calls itself "unstable". It implies certain things about whether it is a good idea to install on a mission-critical server for example, or whether it is a good idea to invest time in writing plugins against its API.

The product itself may be relatively bug-free, but that is not really the issue. RHEL7Beta was relatively bug-free, but I would not advise you to use it for most purposes.

drewcrawford··on Ask HN: Why don't more apps use peer to peer networking?
You certainly can. The thing is though that the hops surrounding the server are generally the fastest hops in the whole path. The server is sitting in a big datacenter somewhere with multiply-redundant, professionally-managed network connectivity.

Doing a direct shot from client to client would be some faster, but not much. Meanwhile there are usually optimizations that are better you could do in the same amount of time.

drewcrawford··on Show HN: Self-hosted project management application
I'm working on a self-hosted product.

My market research suggests that the market for hosted products is much larger but the market for self-hosted products these days is underserved.

There are people who for various reasons refuse to use any hosted product (legal issue, boss said no, etc.) and depending on the competitive landscape they may not have any other options than buying your product. This produces a captive audience.

drewcrawford··on Ask HN: Why don't more apps use peer to peer networking?
Let me give you a comprehensive answer on this that goes back to first principles. I've worked on apps like SnapChat, so I am probably pretty close to an authority on why apps like that don't use p2p.

The first problem is that mobile devices are pretty much inherently asynchronous. There are apps that you would use at the same time as another person (like real-time games) but especially on cellular, lag is an issue. This pushes people into designing products that can tolerate lag measured in seconds (because that isn't shockingly bad performance on cellular networks for apps that use your standard off-the-shelf tools like REST/HTTPS/AWS for example). This produces a lot of asynchronous, or semi-asynchronous applications.

Now partly due to those product designs, and partly due to people having lives, they use these apps asynchronously. You pull out SnapChat, fire off a message, and go back to reading Reddit or whatever. Snapchat is off. There's no way to reach you.

Okay, so why don't we run SnapChat in the background? Well there are layers of reasons. The first layer is that it costs energy, and the mobile revolution is in large part possible because software and hardware developers got very aggressive about energy management. If we ran things in the background like you do on your laptop it would need to be as big as your laptop and plugged in regularly like your laptop. There are also practical problems, like announcing every time your network address changes, or even figuring out when your network address changes, which is hard to do passively. I'm glossing over some networking details but there's a deep principle here that within the design of existing TCP/IP/cellular stack you can't have reliability, energy-efficiency, and decentralization. You must pick 2.

Apple, very presciently IMHO, has decided to legislate a lot of rules about background processes that I don't have time to go into here but basically they try to regulate the types of work that apps can do in the background to only the energy-efficient kind. The rules are actually pretty well-designed but they're still rules and they restrict what you can do. Android doesn't have this limitation but unless your product is Android-only you're going to comply with the iOS rules when you design a feature that communicates across platforms.

Okay, so we can't run Snapchat in the background. But what if two users happen to have it open? We can use p2p then right?

Well sure. But the user may be on a network that blocks p2p traffic. That is their network's fault, but they still e-mail you to complain, and leave bad reviews for your product, because as far as they can see "the Internet works" so it's your app's fault.

So what you do is you design a scheme that uses p2p by default and client-server as a fallback. There are actually apps that work like this. Problem here is, instead of getting support tickets about it not working, now you get support tickets about it being slow.

And there are ways to solve this, like permanently giving up on p2p after a certain numbers of failures for example. But the first experience is still pretty bad, which is what counts in mobile. And I remind you, this p2p feature is already a scheme that only works in the 0.3% of cases that users actually have the app open at the same time, and now you want to add code that disables p2p in even more cases than it's disabled already. This process continues until basically zero actual customers will ever use the feature.

And we haven't even gotten to cases like "Why didn't this message get delivered to all my devices?" because there is just zero chance that any customer, anywhere, will have all his devices turned on at the right time to receive incoming p2p connections.

Now non-messaging products like Spotify or Netflix are more plausible, but you still have to ask who wins here. Customer experience is worse, both because of connectivity problems and increasing bandwidth bills and the energy efficiency losses that comes with rebroadcasting content to other users. Developers are worse because they probably have to build both client-server and p2p architecture, because p2p isn't reliable enough on its own. Support is worse because almost any issue is potentially a p2p-related issue, have you tried disabling p2p and seeing if the issue persists?

There's really no reason, certainly no compelling business case, to inflict that much pain on any mobile product I can think of. I mean, there's probably a place where p2p makes sense--we live in a big world--but in general it makes things much worse for everybody.

drewcrawford··on Remy – Computer-generated TCP congestion algorithm
Providing an implementation of a network protocol is hardly doing "real work in real situations". I mean, it ships the packets from here to there but so does every other implementation of every other protocol.

The thing that is interesting or novel about this protocol as opposed to the thousands of other proposals is that it's supposed to be faster than the other proposals for a broad range of applications with a broad range of link topologies and across a broad range of software/hardware platforms.

Of course, to establish that claim replication is completely critical.

drewcrawford··on Apple Allows the World’s Most Popular Bitcoin Wallet Back Into Its Store
I have extensive, direct, front-row experience with getting difficult apps into the store (though not Bitcoin-related).

The pattern you describe "shut it down, we need to figure this out first" is very accurate. The app is pulled while somebody high up figures out what the policy is going to be. Often the policy involves setting up safeguards (that you may or may not have already implemented) for abuse, user privacy, legal compliance, etc. These new guidelines are then consistently applied throughout the store (although some of them are unwritten and never make it into the official list.)

This process is slow, and not very transparent. However as a person who has been on the receiving end many times I think it is a net positive for the end customer. Sure, I would prefer a system that is both transparent and safe, but it's not so bad really.

drewcrawford··on AltBeacon
I've done quite a lot of thinking about how governance boards could work (or not) for mobile-based projects.

The short answer is that sitting on a governance board takes time and effort, and mobile developers at large aren't really convinced of the benefit (relative, to, say, the Debian advisory boards).

To overcome this you'd need to recruit from people invested in the problem. Probably your competitors.

drewcrawford··on Hold the Phone: A Big-Data Conundrum
I think people substantially underestimate how hard the iOS GUI pushes the performance wall, from one release to the next.

There was a talk at WWDC this year (session 419, if you want to watch it) that goes into some detail about how the blur effects on e.g. the lock screen, notification center, control center, toolbars, etc. work.

You can watch the talk for the details, but as a practical matter several of these effects involve seven (!) full GPU passes, just for these effects alone, let alone whatever UI is under or over them. And not even the very latest-gen devices can do it consistently full-screen at 60fps. iOS displays motion underneath blur effects in very small areas (e.g. a toolbar) on new devices but if you think about it, you never see motion underneath, say, the lock screen. The reason is that not even the latest iPad Air has the GPU to apply some fullscreen blurs in enough time to meet the draw deadline.

This actually surprises a lot of people--I can't count the number of designs I've gotten where some designer has made a large blurred UI element and expects something to move underneath it. Which, depending on the size of the element and the target hardware you can sometimes get away with, but you are in for quite the lengthy performance test, and a complicated spectrum of fallbacks for all the devices that just aren't fast enough.

And that's just one blur effect. You take a look at all the other "new" iOS things that are less visible, like the endless stream of new background technologies (background fetch, silent push, NSURLSession, multi-app audio routing, various iCloud syncing stuff) the new bluetooth stuff (iBeacon, HomeKit, Multipeer), turning WebKit into an LLVM compiler, and all the other things that are going on in iOS it really is "doing more of everything". I remember a time when iOS was basically just a few OS processes plus 1 active app, and as we speak ps on my phone lists 87 processes.

← PreviousPage 6 of 29Next →