When I talk about a room, in Gladys 4 each room has a unique name. So if you want to know the temperature in Paulâs room, you say « What is the temperature in Paulâs room? ».
After that, this request is a very specific request.
We can certainly imagine making another request solely for voice commands (and not textual ones), since we know where the microphone is located, we know where to look for the temperature.
In my small house, itâs simple to have the temperature or turn on the lights by naming the rooms.
But imagine if you rent a room in a guest house or hotel equipped with Gladys, voice commands based on the location where the microphone is installed become very useful!
Hi, I was just thinking the same thing ^^ well, something like that.
I was thinking of a little script that detects where youâre coming from and directly changes the language of the interface according to the country.
Couldnât a script pre-select? Generally, but not always, French users will prefer to use everything in French. If they ultimately prefer to continue in English, they will only have to change the selection.
In any case, itâs really not a big deal, just a detail!
We will need to consider the case where the user does not want to save their date of birth, and not make this field mandatory. But I imagine thatâs what you were planning to do
When it comes to details and birth dates, since we ask for the personâs first name, canât we make it so that Gladys also celebrates their name day? ^^
Given that she can make coffee and also start my vacuum cleaner, if Gladys wished me a happy birthday, she would be more effective than my girlfriend, thatâs why I ask.
Yes, there will be a user photo Iâm still hesitating whether to include it in the registration process or to ask later (and use a default avatar in the meantime).
Good idea! We can use the browserâs recommended language to pre-select French if the user is French.
Unlike an online service, Gladys is local (your data is for you), so I struggle to see why the user wouldnât want to save their date of birth? For now, I had made it a mandatory field, but thatâs open to discussion!
I like the idea! Letâs see how we handle:
Internationalization (are the dates the same for each country?)
Compound names
I think for a first alpha of this v4 weâll stick to the essential features, Iâll do this a bit later!
Entering your address would mean using a geocoding solution (finding a latitude/longitude from a physical address). Unless we integrate a database of all addresses in Gladys (too heavy), this means using an online service and sending this data to a third-party service. Iâm not sure this is what we want in Gladys (if it were in an optional module, maybe, but here itâs the default registration process).
For geolocation, the slight issue is that browser geolocation only works over HTTPS. At this point in the process, the user may not necessarily be in HTTPS (Iâm not saying definitely because Iâm considering adding the possibility of being in auto-signed HTTPS automatically at the first boot), but in any case, it will be something that is not forced (self-signed certificates are not very nice and for users who donât know much about it, itâs not necessarily easy to understand).
Another geolocation solution is GEO-IP, a database of IPs that provides an approximate address for each IP. Again, this is too heavy to have in Gladys, but we can use online services or integrate this service into the Gladys Gateway.
But I completely understand the need, itâs clear that itâs annoying to point on a map your home⊠^^ If anyone has an idea that is a good compromise between practicality and respect for privacy, Iâm interested!
