I have 3 beacons that I’m trying to program remotely for a friend of mine, we are trying to put this url on a notification:
That is a test link, it is for a contest they are having for giving away a free gas gift card, no purchase necessary, just trying to promote their new app, that is about to launch that is free.
But I cannot get that URL in the eddystone-url, it says it is too long.
How do we get urls in there?
How can a URL be too short, when some domain names are long tail domains?
We need to use that shortened url service we own, (YOURLS) so that we can pass the long url it has, so it identifies which beacon they used, because different people will carry the beacons out around…
Anyhow, where do I find out how to do this? I’m not afraid of hard work, but I don’t even know where to start and it seems there is a year of documentation to go over, I don’t have that kind of time.
Can someone point me to the place to find the answer?
I’ve looked at everything I could find on eddystone-url but have not found my answer.
Thank you in advance for any tips/advice/pointers you can share with me.
-Richard
I don’t think there’s any hard work involved here, no worries You just need to use a shorter URL—here, the part after the slash could probably be shorter. It doesn’t need to be human-readable—if you want to use the Physical Web, then Chrome/Android will automatically expand (i.e., follow the redirects) the URL. So maybe something like https://olink.us/WFGP1?
You just need to use a shorter URL—here, the part after the slash could probably be shorter. It doesn’t need to be human-readable—if you want to use the Physical Web, then Chrome/Android will automatically expand (i.e., follow the redirects) the URL. So maybe something like