Made it compatible with other devices

[SylvainGa]

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
472105	Triggered	OpenWeatherMap Token	29b43bfa980549ba999796b92317f453d67e862f	source/BackgroundService.mc	View secret
472105	Triggered	OpenWeatherMap Token	d1266be0fbd63bf3eaa5affd92306f06cb603dd1	source/BackgroundService.mc	View secret
472105	Triggered	OpenWeatherMap Token	d1266be0fbd63bf3eaa5affd92306f06cb603dd1	source/BackgroundService.mc	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[SylvainGa]

Hi, I haven't had the time to look at it yet but should be able before the end of the week.

Le lun. 18 sept. 2023, à 17 h 46, Adrien Chenu @.***> a écrit :

@.**** commented on this pull request.

Longitudes go from -180 to +180. This current check restrict the time zone east of Chicago and west of India (roughly).

The local city feature does not currently work for East Asia (China, Japan) or California for example.

Hopefully this change will fix this. Thanks for considering it.

— Reply to this email directly, view it on GitHub https://github.com/warmsound/crystal-face/pull/209#pullrequestreview-1632029382, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALYXESXLNTMTB5ETZDWHHT3X3C6LLANCNFSM5ESSMNUQ . You are receiving this because you authored the thread.Message ID: @.***>

[AdrienChenu]

Thank you. No rush at all.

I'm quite new to contributing to Github, I thought my comment was linked to the line of code when I wrote it, and I posted the same comment twice. Sorry. 😅

I managed to create a Pull Request that should hopefully fix it: https://github.com/SylvainGa/crystal-face/pull/8

Feel free to reject if I did it wrong, and thanks again for making that watch face. It's the main one I use.