i like that we can plan out ohc's well in advance now, i think its really helpful to set that level of commitment and its not always just "do we wanna do it NOW or" level of stuff, or if we can only do it later and the host forgets we're SOL

however one issue i kinda take up with it is that, often i really have to plan out and do Mind Tricks to see when the ohc actually takes place, time remaining till it starts works well if its just 30 minutes or w/e but i think if its 10 hours or more it starts to kinda fail

my suggestion is really to just include the time it starts at somewhere alongside the countdown, potentially in the users own timezone (this i know is very tricky to implement and i wont hold it against you if you just use utc or gmt or something)

looks like shit but heres an example of what i mean really: https://i.imgur.com/9HZeawi.png

"starts in 18 hours" unfortunately doesnt tell me much, "starts at 10 pm utc" tells me a lot more and i can just say "ok i can be there" and set an alarm on my phone or something haha

thats all i have to say! thank you

I think botb as a whole avoids users' timezones and uses it's own standard of time. By design.

yeah i can see that now, but i think that kinda design mentality might be actually hurting more than helping in this case (and also, that post is almost 5 years old by now, maybe thoughts have changed since? who knows ¯\_(ツ)_/¯)

https://github.com/jessicarobo/userscripts/blob/main/botb%20custom.user.js

kleeder that helps so much, thank you!
(still wish it was integrated as part of the site's actual design though if only so it could be affected by the palette i have haha)

I would say I'm not against this as much as I used to be.

But, also, there are some larger priorities in front of it.

oh absolutely, if there's bigger priorities then those should prolly be taken care of first, i appreciate it being considered to begin wth!

i'd also say this feature would be really important to get correctly

like, there are probably libraries to help, but it would probably be an opt-in feature for the first while

Opt-in beta is a good idea, will definitly try that. But having both, countdown and datetime can also prevent most errors :)
Then switch to opt-out will probably be simple, and will let people using VPNs to disable the feature if they don't want to see random times!
Using library is a good idea too, if you want to avoid summer/winter hours of some countries ahah. Would be a lot of effort to do that from scratch and right...