leeola has quit [Quit: Connection closed for inactivity]
harish_ has quit [Remote host closed the connection]
pdurbin has quit [Quit: WeeChat 0.4.2]
pdurbin has joined #sandstorm
jemc has quit [Ping timeout: 260 seconds]
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jemc has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
Zarutian has joined #sandstorm
Salt has quit [Ping timeout: 240 seconds]
Salt has joined #sandstorm
nicoo has quit [Ping timeout: 240 seconds]
Tryum_ has joined #sandstorm
Tryum has quit [Ping timeout: 240 seconds]
nicoo has joined #sandstorm
jemc has quit [Ping timeout: 260 seconds]
jadewang has joined #sandstorm
ShalokShalom has quit [Remote host closed the connection]
xet7 has quit [Quit: Leaving]
Zarutian has quit [Quit: Zarutian]
yeehi_ has quit [Remote host closed the connection]
nicoo has quit [Ping timeout: 240 seconds]
Mitar has quit [Ping timeout: 240 seconds]
XgF has quit [Ping timeout: 264 seconds]
XgF has joined #sandstorm
Mitar has joined #sandstorm
nicoo has joined #sandstorm
ecloud is now known as ecloud_wfh
ShalokShalom has joined #sandstorm
ragesoss has quit [Quit: No Ping reply in 180 seconds.]
ragesoss has joined #sandstorm
yeehi has joined #sandstorm
harish has joined #sandstorm
harish has quit [Remote host closed the connection]
harish has joined #sandstorm
afuentes has joined #sandstorm
yeehi1 has joined #sandstorm
yeehi has quit [Ping timeout: 240 seconds]
samba_ has joined #sandstorm
samba__ has joined #sandstorm
samba_ has quit [Ping timeout: 268 seconds]
yeehi has joined #sandstorm
samba__ has quit [Ping timeout: 260 seconds]
yeehi1 has quit [Ping timeout: 260 seconds]
cevi has quit [Quit: ZNC 1.6.4+deb1+b1 - http://znc.in]
cevi has joined #sandstorm
samba__ has joined #sandstorm
samba__ has quit [Ping timeout: 258 seconds]
yeehi1 has joined #sandstorm
yeehi has quit [Ping timeout: 264 seconds]
samba__ has joined #sandstorm
samba__ has quit [Ping timeout: 264 seconds]
tobald has joined #sandstorm
samba__ has joined #sandstorm
samba__ has quit [Ping timeout: 256 seconds]
samba__ has joined #sandstorm
samba__ has quit [Ping timeout: 258 seconds]
leeola has joined #sandstorm
dongo_ is now known as dongo
jemc has joined #sandstorm
bodisiw has joined #sandstorm
Zarutian has joined #sandstorm
samba__ has joined #sandstorm
jemc has quit [Quit: WeeChat 1.4]
jemc has joined #sandstorm
Tryum_ is now known as Tryum
ill_logic_ has quit [Quit: ill_logic_]
samba__ has quit [Ping timeout: 264 seconds]
tobald has quit [Ping timeout: 256 seconds]
harish has quit [Ping timeout: 240 seconds]
harish has joined #sandstorm
samba__ has joined #sandstorm
<isd>
Something I've observed with my znc port is that all the playback timestamps are in UTC. Is there a way to detect/query the user's timezone?
<isd>
capnp schema in the sandstorm repo suggest not.
<isd>
I guess I can probably do this with javascript.
<isd>
standard http mechansims and such.
<isd>
Can find ways of getting the utc offset, but the zone is more complex. Also, tz data varies so frequently...
<dwrensha_>
hm, yeah arguably "preferred timezone" should be part of Sandstorm's profile data for a user
<isd>
Having irc timestamps played back in not-my-timezone is rather disorienting.
<dwrensha_>
detecting the timezone client-side should work in many (most?) cases
<TimMc>
Should it be the profile data, or detected from the browser?
<TimMc>
err... what you said
<TimMc>
isd: Having an explicit setting would be nice in any case, though; I prefer my IRC timestamps in UTC even though my (main) desktop clock is Eastern Time.
tobald has joined #sandstorm
samba__ has quit [Ping timeout: 264 seconds]
tobald has quit [Ping timeout: 264 seconds]
<isd>
Having done a bit of searching, I'm finding ways of getting the UTC offset from the browser, but not the *timezone,* so it's going to do weird stuff around DST, and wrangling that without being told which thing it's supposed to be is... complicated.
<TimMc>
interesting
<isd>
TimMc: do you mean you'd want the timestamps do display something different that the times you seee in your browser?
<isd>
Short-term I might add a setting to the app anyway.
<TimMc>
Different than the times I see in applications, yes.
<zarvox>
isd: new Date().getTimezoneOffset() gives browser timezone offset in minutes, FWIW
Telesight has joined #sandstorm
<isd>
zarvox: yeah, but it doesn't give you info re: DST, for example.
<dwrensha_>
what specifically are you worried about re DST?
<isd>
dwrensha_: So, in my case, I'll actually need to configure the znc daemon somehow (probably by fiddling with the /etc/localtime symlink (which will probably have to go through something in /var)). So I won't necessarily be able to query the time zone when the user re-connects to the bouncer. So if all I had was the UTC offset, I can't detect when/if it should shift.
<isd>
It would be easier if I was only going to use this when the user was looking at the web ui
ShalokShalom_ has joined #sandstorm
ShalokShalom has quit [Ping timeout: 240 seconds]
ShalokShalom_ is now known as ShalokShalom
<zarvox>
isd: hmmm, yeah. I suppose you could try comparing the offset for new Date() to the offset for ~six months ago? but that's clearly hax
<isd>
It's more complicated than that. E.g. GMT switches off of daylight savings time about a week before US/Eastern does.
<isd>
You could do a binary search until you got within < 1 day.
<zarvox>
Yeah, and it's not guaranteed to be valid for six months.
<isd>
but yeah, it's a hell of a hack.
<isd>
And you'd have to find two points, not one.
<zarvox>
But really, trying to infer what time it "really" is for a user seems like doing the Wrong Thing, and better would be for all timestamps to be stored as UTC and converted to whatever the client's timezone (or user-configured override) is
<zarvox>
unclear if ZNC's architecture allows for that though
<isd>
Yeah. This sort of thing is why I decided to try to write my own IRC bouncer. Experience has convinced me that leveraging existing protocol support is the better side trade-off.
samba__ has joined #sandstorm
<isd>
*side of that
<isd>
hence having since abandoned IRC Idler.
<isd>
Looks like there is a ZNC config setting that does what I want, it's just a question of how to collect the right value.
<isd>
(So no symlink nonsense necessary)
samba__ has quit [Ping timeout: 240 seconds]
<isd>
I think what I'm going to do short term is just have a setting for it on the web dashboard for the app, rather than trying to detect it.
<isd>
Maybe if/when sandstorm let's me query this, I'll use that to choose a default.
samba__ has joined #sandstorm
samba__ has quit [Ping timeout: 260 seconds]
<dwrensha_>
powerbox project idea: port supermute to sandstorm