That was a bug: our TLD validation wasn't considering .brussels to be a valid TLD - I've made it more flexible.

We've pushed a fix, it should be live soon. The validation and login flow take place entirely on the client, so make sure you refresh. Thanks the report!

Let me check the validation - we are using it ourselves, so it might be the fact that the handle is directly under a TLD.

The more context you give, the better the pour. Give these a shot and let us know how it performs! 🥂

#winesky #wine #sommelier

Finally, you can iterate on your recommendations!

#Winesky explains the characteristics of the wines it recommends why they may match, so if something doesn't sound to your liking, or a bottle isn't available, scroll down, tap on "Iterate", and give it more details to get an update.

Winesky searches the web, so here's a surprise:

If you’re heading out, tell the Sommelier the name and location of the restaurant. If they have their wine list online, Winesky can cross-reference their actual menu to give you the perfect pairing recommendation! 🍽️

#winesky

Stuck between a few options at the wine shop? You can upload up to four images at once. 📸

Snap the labels of the bottles you’re considering, tell #Winesky what you are aiming for (e.g., "date night", "carbonara pasta", or "a mixture of tapas including kakuni"), and let it pick the winner for you.

More details, better results. Instead of saying "I like red wine," try telling #Winesky specific bottles or regions you’ve enjoyed before.

Mentioning "I love earthy Oregon Pinot Noirs" gives it a much clearer push for its next suggestion. 📍

This seems to be Webkit-specific, since it happens with Safari and Kagi's Orion browser, but works just fine on Firefox mobile or Opera.

Likely related to an initialization glitch we are seeing.

The Winesky backend will keep a pair of record IDs and encryption keys, which the user can request at any point.

This also allows for an update process where a user can decrypt all their records if they want to keep them in clear text in the future.

#ATDev

Slightly trickier to decide how to handle context for sommelier recommendations. The user should be in control of their information, but we also want to provide a measure of privacy.

For now the recommendation context will be AES-256-GCM encrypted, with one-time keys per record.

#ATDev