Hacker News new | past | comments | ask | show | jobs | submit | more thomasjoulin's comments login

The boarding pass format spec linked in the article [1] shows the support for signing (page 49, fields 25 onwards)

The boarding pass data is still plaintext as explained, but a signature is appended to validate that the content has not been tempered with, and who generated it.

I think boarding pass signing is mandatory on all U.S. airlines at least but I have no source for that

[1] http://www.iata.org/whatwedo/stb/documents/bcbp_implementati...


Wow, tough crowd! I'd be curious to see what some of the commenters have shipped...

One question for the PaintCode team if they read this: is it possible to have dynamic star shapes? i.e I set it grows with the frame

This update looks awesome, can't wait to use it


The lib is 17.7MB, that's pretty big for tap detections

Direct link to download: http://www.kiwimotion.io/library/kiwi-motion-app-master.zip


I'm pretty sure it's so big because it includes the Parse framework (31MB framework, uncompressed)


Government is a special entity to sue. Musk said himself, SpaceX has good relationship with the vast majority of Air Force, it's probably some individual that prevent the process to be more open and competitive.


In the case of the tankers, someone needed to get the USAF or DoD Office of the Inspector General involved.


Any source on that? Here[1] it says otherwise : "farmed salmon generally has more omega-3s, it is sometimes a more healthful choice than wild."

[1] http://www.washingtonpost.com/lifestyle/food/why-farmed-salm...


I don't understand why he's getting fine for that. Those were publicly accessible documents, even though they were intended not to be, as indicated by the login form that Bluetouff admitted to know about.

If that's the law, then it needs to change.


Congratulations. This is an amazing app (that I discovered only because you put the code on GitHub). And going through the code is very interesting. It's sad you went through burnout, but I can see why. Any chance you will blog a bit about the technical challenges you faced? There is quite a lot of code, I'm sure you have a lot to write about.


The man publish a 40 pages technical document and you dismiss it with a comment. At least provide a single argument


No prototype - nothing even remotely close to a prototype. At least rockets and electric cars had some basis in reality before Elon started working on them.


High-speed trains don't have a basis for reality? http://en.wikipedia.org/wiki/Shinkansen


The hyperloop is not a high-speed train.


The Space-X rocket isn't a rocket.

The Tesla Roadster isn't an electric car.

See what I did there?


Yeah, I see that you make no sense ...


Those two statements are however false. As is calling the hyperloop a train. If it was a (fast) train, Musk likely would not have called it a fifth mode of transportation.


This isn't like any other high speed train in existence. The rail cars have more in common with a vtol jet than the train you linked.


What leads you to believe that Musk is incapable of building an entirely new technology?


I believe Musk is perfectly capable - just as Dean Kamen is a capable, successful inventor.


I don't think it can be underground, since Musk said it would cost $6 billion to build. Also, the plan is to build something similar for east-west coast travel, and underground would be even less possible.


The other consideration aside from cost is that seismic activity, even minor, can skew a tunnel. (Edit: for deep tunnels, that is. I have no idea about tunnels right below the surface.) That's bad news at high speed. I've given the tunnel approach some thought.[1]

And I keep hearing people trying to apply Hyperloop to coast-to-coast travel, but I don't recall Elon every saying anything about that long of a distance. In fact I recall him specifically talking about "the right city pairs", which implies some kind of distance limit.

[1] http://www.youell.com/matt/writing/?p=1050


In an interview, Elon said that the system could work underground but that it would be more cost effective above ground...


I do wonder if there's something specific about LA to SF that enables the low low cost Elon's suggesting. Like the fact that they share a coastline with the Pacific Ocean.

The $6 billion cost seems too good to be true for any transportation system that would require significant land acquisition. California is set to spend some $60 billion on a train between these cities, and most of that cost is for right-of-way.


the time to travel between ny and sf can be the time it takes me to come to work. they'd make that 6 billion back in a month.


> "Complex" Layouts"

> Neither Android or iOS support this "Flow Layout" natively

I don't know about Android, but iOS has just that : UICollectionViewFlowLayout. It would be trivial to implement a tag list as he did.


Was just about to post this. Also, IB is great and constraints are easy to manage once you realize that it's a calculated ruleset that enforces unambiguous constraints. The iOS framework is beautiful, and the author favored Android mostly due to his inexperience with both platforms.


Is that therefore a failing in the apple documentation, or perhaps not meeting the conventions with other frameworks and languages out there?


There is no failing in documentation. The framework is the same (UIKit), and in fact the API is a lot like that for UITableViewController—the cornerstone of many iOS apps.


AutoLayout in IB in Xcode 4 was an absolute nightmare. Easily one of my most frustrating dev tool experiences ever.

It's much better in Xcode 5.


A UICollection view is complex solution compared to the CSS equivalent of "float:left", or "display:inline-block".

Furthermore, you will be responsible for resizing the collection view and its sibling views or getting auto-layout working correctly to do part of this for you.

In the tag layout, it would be about as easy to just write line-wrapping code by hand, than to use a UICollectionView.


> In the tag layout, it would be about as easy to just write line-wrapping code by hand, than to use a UICollectionView.

Possibly but the code you would be writing for UICollectionView would be mostly boiler plate. All the layout would be handled for you. Updating a few parameters would be quite easy and you could do it via IB or via code. Once you wrote this once it would also be quite portable.


> All the layout would be handled for you.

No it won't. The tags are variable width, you have to implement something like sizeForItemAtIndexPath. You also must monitor the height of scrollable content region, so you have to monkey patch the collectionViewContent size (or KVO a non-public property), so you can resize the collection view and have the outer controller layout the subviews.

Collection Views don't really make sense when the collection view shouldn't scroll.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: