Give user feedback for mistyped beacon id

[je-l]

Currently user receives no feedback when invalid beacon id is given. Location is simply not visible on map.

Ideas:

• Always require that the given beacon id is known, so that location data includes the given id, and user cannot give unknown beacon id.

• Prompt the user if they really want to use unknown beacon id. The advantage would be that user can "register" the beacon id and then enable bluetooth later on, finally seeing the location on map.

[ptesavol]

I think we need to consider carefully the implications of different policies of handling beacon IDs, but this doe not need to happen during the current project.

One idea is that people could claim ownership of beacon id:s. This could happen so that the user would be required to give a password (also "repeat password" field is obviously needed) when introducing a new beacon id to the system. After this, all subsequent changes to the settings (visibility, deleting etc.) of the beacon would require this password.

An obvious way to attack against this kind of system would be to listen to all beacon traffic with an android app, and claim ownership of all seen beacon ids. Maybe this attach could be overcome by asking the user to bring the beacon within 10cm of some specific scanner tablet to complete the beacon id registration. This could also be a great opportunity perform the normal signal strength calibration.