Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic schedule is too short (late) [wishlist] #39

Open
janxkoci opened this issue Nov 21, 2018 · 0 comments
Open

Automatic schedule is too short (late) [wishlist] #39

janxkoci opened this issue Nov 21, 2018 · 0 comments

Comments

@janxkoci
Copy link

janxkoci commented Nov 21, 2018

The automatic schedule of Nightlight is not working well for me - the icon and redshifting starts at 19:00, which in November at my location in Central Europe is waaaay beyond the dawn. My other laptop with Gnome kicked nightlight into work before 16:00! Afaik Gnome is using geolocation service to determine when to switch on nightlight, and so did Redshift app back in Loki (although I could set the location there if I didn't want to give off my location).

Nightlight in Juno doesn't seem to use geolocation (it's not listed in Privacy tab), but frankly, it doesn't seem to use any other clue, not even the date in the calendar (let alone timezone or locale settings, which could be tricky I admitt).

Is there a way to opt in to geolocation-based scheduling? At least a choice of automatic geolocation or putting a pin into a map would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant