search

google / eddystone

Specification for Eddystone, an open beacon format from Google
Apache License 2.0
3.08k stars 762 forks source link

Request: Add ".me" to Eddystone-URL Table #100

Closed eileenod closed 8 years ago

eileenod commented 8 years ago

I wanted to request that the byte codes for the Eddystone-URL HTTP URL encoding include expansion to the .me domain. As they say: "a byte saved is a byte earned".

mmocny commented 8 years ago

@scottjenson.

Interesting suggestion, but I'm not sure how to best roll out changes to these values. As soon as you start advertising URLs with this change you isolate all clients which are not up to date with the latest spec.

I wonder if we should send the raw bytes of the advertisement packet to the PWS, which can update more easily to support new values?

scottjenson commented 8 years ago

Interesting thought. The whole intention was to roll out new compression codes, so I'd hate to say we're done forever. The longer we wait, the harder it will get. Fortunately, old beacons will work with new clients. But as you point out, the opposite isn't the case.

One possibility is that clients expand the opcodes they are able to and then allow the PWS to extend any codes that are left over. This allows much of the decoding to still be in the client but the PWS is there to clean up any older clients. This allows both approaches (client vs PWS) so we can allow both approaches.

It's been a back burner issue to revisit the code expansion but it's likely going to be tricky as we can't, for example do every country code. We could add intermediate codes like ".co" and ".gov" as they are used in most country expansions (e.g. bbc.co.uk)

If we can find a way forward with the client/PWS approach, I'd like to focus more on TLDs such as .info, .io, .cc and other popular ones we missed in our first pass.

jerryhimmersion commented 8 years ago

Are these TLDs included: .xyz, .guide, .biz, .tours I need alternatives to .com, all the names I want to use are taken.

mmocny commented 8 years ago

You are free to use those URLs, they simply will not be "compressed" down to a single byte.

On Tue, Dec 1, 2015 at 2:50 PM jerryhimmersion notifications@github.com wrote:

Are these TLDs included: .xyz, .guide, .biz, .tours I need alternatives to .com, all the names I want to use are taken.

— Reply to this email directly or view it on GitHub https://github.com/google/eddystone/issues/100#issuecomment-161076372.

jerryhimmersion commented 8 years ago

Is there a link to the current list of acceptable TDLs

eileenod commented 8 years ago

I believe you can find it here https://github.com/google/eddystone/blob/de5ff70112e73616ab63de3e91a038c70cf9f5bf/eddystone-url/README.md