Proposal
Would an explicitly opt-in weather module fit MacMonitor's menu bar customization, or should weather remain out of scope for a hardware monitor?
The implementation originally explored in #9 used Open-Meteo without an API key. Before preparing any code, I want to settle the product/privacy boundary raised in review.
Proposed safeguards
- disabled by default
- no DNS lookup or HTTP request until the user explicitly enables weather and saves a location
- a clear Settings description naming Open-Meteo
- README documentation explaining that the configured location (or resolved coordinates) is sent to Open-Meteo to retrieve current conditions
- easy disable/remove behavior, with no background requests after disabling
- failure is quiet and never interferes with hardware monitoring
Possible UI scope
- optional menu bar module only
- compact current temperature/condition; no forecast dashboard in the first version
- refresh infrequently (for example, every 15 minutes)
If weather is considered outside MacMonitor's scope, I am happy to leave it out rather than submit a code PR.
Related: #9
Proposal
Would an explicitly opt-in weather module fit MacMonitor's menu bar customization, or should weather remain out of scope for a hardware monitor?
The implementation originally explored in #9 used Open-Meteo without an API key. Before preparing any code, I want to settle the product/privacy boundary raised in review.
Proposed safeguards
Possible UI scope
If weather is considered outside MacMonitor's scope, I am happy to leave it out rather than submit a code PR.
Related: #9