News for hackers. Stuff that matters.
Re:Apple Releases iBeacon Specification by guelo on Tuesday February 25, 2014 @12:29PM (#7298985)
We already know what Apple's iBeacon BLE advertising packet looks like without having to sign away your first-born to read the spec. Here it is:

  ff 4c 00 02 15  # Apple's fixed iBeacon advertising prefix
  <Your 16 byte iBeacon proximity uuid>
  00 00 # major 
  00 00 # minor 
  c5 # The 2's complement of the calibrated Tx Power
Anybody can build such a BLE device and market it as "Compatible with iPhone". The question is if Apple will try to to go full-asshole and claim copyright of that packet structure or something ridiculous like that.
Re:Apple Releases iBeacon Specification by bryanpaluch on Tuesday February 25, 2014 @01:05PM (#7299248)
Apple doesn't have to claim copyright.

They can simply make sure your iBeacon proximity uuid doesn't get registered with the OS if you aren't a certified vendor.

No uuid registration with the OS and people using your app will not get a background notification for your iBeacons.

This would leave app developers with only having the ability to detect beacons when their app is foreground, or during background processing time.

Note: There are no checks like this today. You can advertise any UUID you want, and have your app subscribe for notifications if the os detects the iBeacon in the background.

Re:Apple Releases iBeacon Specification by loceng on Tuesday February 25, 2014 @01:06PM (#7299254)
Unfortunately it's likely they will go "full asshole" as Apple is a controlled ecosystem.
Re:Apple Releases iBeacon Specification by gress on Tuesday February 25, 2014 @03:26PM (#7300228)
If you don't tell us why you think it would be in their interest to do so, your comment is meaningless.
Re:Apple Releases iBeacon Specification by loceng on Tuesday February 25, 2014 @05:43PM (#7301226)
"... as Apple is a controlled ecosystem."
Re:Apple Releases iBeacon Specification by gress on Tuesday February 25, 2014 @07:39PM (#7301867)
What does that mean? Where is this idea defined? How do we know this? What are the alternatives?
Re:Apple Releases iBeacon Specification by loceng on Tuesday February 25, 2014 @11:46PM (#7302939)
Good questions. I'm sorry though I don't have time to reply in depth. The opposite of controlled is managed IMHO.
Re:Apple Releases iBeacon Specification by MichaelGG on Tuesday February 25, 2014 @04:34PM (#7300716)
What stops someone from just spamming popular beacons? Or is there a full authenticated handshake?
Re:Apple Releases iBeacon Specification by corresation on Tuesday February 25, 2014 @03:29PM (#7300251)
They can patent the specifics of the exchange, similar to how ActiveSync (the web services API that Exchange uses) is patented.
Re:Apple Releases iBeacon Specification by nathancahill on Tuesday February 25, 2014 @01:17PM (#7299334)
The first two characters of the fixed prefix are "ÿL", most likely referencing YL Ventures [0], an investor in Upstream Commerce (a real-time intelligence startup).

[0] http://www.ylventures.com/

Re:Apple Releases iBeacon Specification by HL3Confirmed on Tuesday February 25, 2014 @01:28PM (#7299424)
FF4C0002150 in Binary? 11111111010011000000000000000010000101010000

Number of 1s in that? 15

Number of spaces in the fixed iBeacon prefix? 5

15 / 5?

3

HL3 Confirmed.

That's what you sound like.