Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #14437
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: Dealing with timestamps from different timezones - general approach for basic saving? |
| Date | 2014-10-31 09:51 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <m3045c$bk7$1@dont-email.me> (permalink) |
| References | (2 earlier) <3237691.dGveQkY2Hi@PointedEars.de> <m2tghg$vpt$1@dont-email.me> <1678143.gufaXuZXlV@PointedEars.de> <m2uelb$ld2$1@dont-email.me> <12869065.30PDesOKB2@PointedEars.de> |
On 10/31/2014 12:33 AM, the troll Thomas 'Pointed Head' Lahn wrote: > Jerry Stuckle wrote: > >> […] Thomas […] Lahn wrote: >>> Jerry Stuckle wrote: >>>> […] Thomas […] Lahn wrote: >>>>> Jerry Stuckle wrote: >>>>>> 1. Ask for their timezone and save it in a cookie (an extra operation >>>>>> on their part) >>>>> Or local storage. For privacy, in a server-side session. Could be in >>>>> a database. >>>> And how are you going to do that unless they sign in? >>> >>> 1. STFW for “Local Storage”. >>> >>> 2. Server-side (PHP) sessions set a cookie with a session ID, but the >>> privacy-critical payload is stored on the server. No sign-in >>> necessary. >> >> And just how is he supposed to get the timezone from your answer? > > Those who can read and have not closed their mind have surmised by now that > instead of saving the timezone *as provided by the user* in a cookie *as you > proposed*, it could be saved in Local Storage or in a server-side session > instead, whereas, with PHP at least, the session data could be held in a > database. > Which still doesn't answer the question. How does it get the timezone from the user? Does the user have to answer a question (another added hurdle for the user to jump through)? Getting it through javascript means the user doesn't have to answer a question. And how many users (besides yourself, of course) sets up their system with a timezone other than the one they want to see the time displayed in? And you never said why it should be stored in local storage or server-side instead of in a cookie. And if it's held in a database, how does the database entry get related to the user - other than through a registration process (another hurdle). And the database idea fails when people travel to other timezones. Your idea has more holes than a sieve. >> BTW - what's wrong with storing the timezone in a cookie? There isn't >> any security issue here - if the user changes the contents of the >> cookie, it will just display the wrong time for him. > > Once you have looked deeper into those issues, you will have realized that > *any* personal information is a matter of *privacy*. Security is a > different concept that you were the first to mention here, confusing the > issue. > Show how storing a timezone in a cookie on the user's computer affects privacy - and how storing it on the server is better. >>>>>> 2. Use javascript to fetch the user's timezone and display it >>>>>> accordingly (off topic in a PHP newsgroup) >>>>> It would be the *system’s* timezone, which is why it is error-prone. >>>> It is the user's system - not the server system. >>> *sigh* I know. Nobody but you, now, referred to the server in *that* >>> regard. The point here is, it would be not the user’s timezone, but that >>> of the local computer system. Big difference. >> >> Yes, and I don't know about you, but people keep their local system >> timezone to the one they want their time displayed in. > > Iff they are aware of the issue and able to do something about it. That’s > the point. > Of course, you try to sidestep the question instead of admitting you are wrong. How many people (besides you, that is, because we know you don't know how to change the time) set their computer to a timezone other than the one they wish to view times in? Even Windows makes it quite easy. >> Now why don't you crawl back into your little hole. But please don't >> insert your head where the sun doesn't shine - the point might perforate >> your colon. > > It is fortunate that your vocabulary forms an empty intersection with mine. > Yes, but then it's easy for anyone to form an empty intersection with an empty set. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Dealing with timestamps from different timezones - general approach for basic saving? e.blumstengel@googlemail.com - 2014-10-28 12:42 -0700
Re: Dealing with timestamps from different timezones - general approach for basic saving? Jerry Stuckle <jstucklex@attglobal.net> - 2014-10-28 16:51 -0400
Re: Dealing with timestamps from different timezones - general approach for basic saving? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-30 08:14 +0100
Re: Dealing with timestamps from different timezones - general approach for basic saving? Jerry Stuckle <jstucklex@attglobal.net> - 2014-10-30 10:04 -0400
Re: Dealing with timestamps from different timezones - general approach for basic saving? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-30 22:38 +0100
Re: Dealing with timestamps from different timezones - general approach for basic saving? Jerry Stuckle <jstucklex@attglobal.net> - 2014-10-30 18:38 -0400
Re: Dealing with timestamps from different timezones - general approach for basic saving? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-31 05:33 +0100
Re: Dealing with timestamps from different timezones - general approach for basic saving? Jerry Stuckle <jstucklex@attglobal.net> - 2014-10-31 09:51 -0400
Re: Dealing with timestamps from different timezones - general approach for basic saving? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-11-01 09:31 +0100
Re: Dealing with timestamps from different timezones - general approach for basic saving? Jerry Stuckle <jstucklex@attglobal.net> - 2014-11-01 09:31 -0400
drifted into ABUSE: Re: Dealing with timestamps bill <william@TechServSys.com> - 2014-11-01 11:21 -0400
Re: drifted into ABUSE: Re: Dealing with timestamps Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-11-01 17:04 +0100
Re: drifted into ABUSE: Re: Dealing with timestamps Jerry Stuckle <jstucklex@attglobal.net> - 2014-11-01 21:32 -0400
Re: drifted into ABUSE: Re: Dealing with timestamps Tim Streater <timstreater@greenbee.net> - 2014-11-02 09:27 +0000
Re: Dealing with timestamps from different timezones - general approach for basic saving? Denis McMahon <denismfmcmahon@gmail.com> - 2014-10-29 01:50 +0000
csiph-web