From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id KJf9H6c6ymPZBAAAbAwnHQ (envelope-from ) for ; Fri, 20 Jan 2023 07:54:31 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id mNEMIKc6ymMSmAAA9RJhRA (envelope-from ) for ; Fri, 20 Jan 2023 07:54:31 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4C3EA3A93A for ; Fri, 20 Jan 2023 07:54:31 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pIlHh-00051q-R3; Fri, 20 Jan 2023 01:53:58 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIlHf-00051V-Kt for emacs-orgmode@gnu.org; Fri, 20 Jan 2023 01:53:55 -0500 Received: from gproxy3-pub.mail.unifiedlayer.com ([69.89.30.42]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIlHd-0003Vq-J3 for emacs-orgmode@gnu.org; Fri, 20 Jan 2023 01:53:55 -0500 Received: from cmgw11.mail.unifiedlayer.com (unknown [10.0.90.126]) by progateway5.mail.pro1.eigbox.com (Postfix) with ESMTP id 486BA1004132D for ; Fri, 20 Jan 2023 06:53:49 +0000 (UTC) Received: from box2035.bluehost.com ([74.220.219.237]) by cmsmtp with ESMTP id IlHZpe6LhJceRIlHZphQt6; Fri, 20 Jan 2023 06:53:49 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=Or6Kdwzt c=1 sm=1 tr=0 ts=63ca3a7d a=VozZY++RX3oc2UgfNhVfaA==:117 a=VozZY++RX3oc2UgfNhVfaA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=MKtGQD3n3ToA:10:nop_fastflux_from_domain_1 a=1oJP67jkp3AA:10:nop_fastflux_mid_domain_1 a=RvmDmJFTN0MA:10:nop_rcvd_month_year a=DPR-AOO6AYYA:10:endurance_base64_authed_username_1 a=A2tt7buDTgEA:10:from_fastflux_domain1 a=pGLkceISAAAA:8 a=o9zw6IYYAAAA:8 a=Pl2Sm1NVD-BpRFe7MNUA:9 a=-FEs8UIgK8oA:10:nop_fastflux_domain_1 a=BtxB1_lq3pBo68oZtZ_9:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tsdye.online; s=default; h=Content-Type:MIME-Version:Message-ID:In-reply-to :Date:Subject:Cc:To:From:References:Sender:Reply-To:Content-Transfer-Encoding :Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=viJZsFE/i9c7+4detqCLR7WR72CPnNYyUBzbwHkwHq8=; b=jvsjncEGsq4hMGD3TlFUZrCpGH isny8gMfmGbdLfYr7jRP2+DXp7qay92kYMiWLkDNhTBZtl5tZIDG78HEqHHYkPcNnowElWRhJ9go0 wzFfKVvW5iqvOJYs05jGAoDqtEdlVnFu39oGQPIjclNQrP0xbZ7Pu/lLzg4tsKkh3XjchvpZJsvNQ KQC6bULj+kuWjidbqW5qWrb443Z6FobQXv5j12r9DdzSKoVAJCM7xKFGDdm5FCuWpqmdtnBSqGfYD bQKtv7JA2YT4Toivzfpm6CW+8Ku7E+nfsGWwnpNBE8Uj+yRZckbYW2cVf0dRqW3pYNSbfGb4xmD8u OnUxmFbw==; Received: from cpe-50-113-33-148.hawaii.res.rr.com ([50.113.33.148]:54486 helo=poto-foou.tsdye.online) by box2035.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pIlHX-0033sc-Lp; Thu, 19 Jan 2023 23:53:47 -0700 References: <63c66048.630a0220.427bf.a5f6@mx.google.com> <87r0vtiks0.fsf@localhost> <63c671c0.a70a0220.61aa5.56b8@mx.google.com> <87fsc88aq9.fsf@localhost> <63c7dd3d.170a0220.6b4d6.f84f@mx.google.com> <877cxk6oeu.fsf@localhost> <63c86454.170a0220.80970.652d@mx.google.com> <63c8f5a6.170a0220.ea8cf.7f96@mx.google.com> <63c9b654.170a0220.d82d2.4254@mx.google.com> User-agent: mu4e 1.6.10; emacs 27.1 From: "Thomas S. Dye" To: Max Nikulin Cc: emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Date: Thu, 19 Jan 2023 20:46:21 -1000 In-reply-to: Message-ID: <87lelxk87a.fsf@tsdye.online> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box2035.bluehost.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tsdye.online X-BWhitelist: no X-Source-IP: 50.113.33.148 X-Source-L: No X-Exim-ID: 1pIlHX-0033sc-Lp X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: cpe-50-113-33-148.hawaii.res.rr.com (poto-foou.tsdye.online) [50.113.33.148]:54486 X-Source-Auth: tsd@tsdye.online X-Email-Count: 8 X-Source-Cap: dHNkeWVvbmw7dHNkeWVvbmw7Ym94MjAzNS5ibHVlaG9zdC5jb20= X-Local-Domain: yes Received-SPF: pass client-ip=69.89.30.42; envelope-from=tsd@tsdye.online; helo=gproxy3-pub.mail.unifiedlayer.com X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_SUSPICIOUS_NTLD=0.499, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_PDS_OTHER_BAD_TLD=0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1674197671; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=viJZsFE/i9c7+4detqCLR7WR72CPnNYyUBzbwHkwHq8=; b=qO5bDs5ED5q5Own13rp3HVL3TNQ34X/KM30CuxDA+cc82eFfvT+cB8ruiTnGB0hPdpedND MFts0xGiKrbqbgre8dlQxphLYzj5yZXSKhpQ8R1TEFrMKQxYX/r0DZOckXsRYoPPlMW/As PZBq4TQjAwSWD84ECHPG+ZsShv/eKsx+tO7at528u418NhZVCRMu1F4TTvSkUWXjiIIP9e JagH5jUBCU+zBDKLsVLW/OxvJc5gkPrARckmy6l60DyEAHQdlOJb3Xcdjc1ukPAA3MaBia TO4YPK0Rzb/EFWMZlC0kae4zO7j+SBIDfOldKtlDZ5+MpNo8cJXBy+XdIE8SkQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=tsdye.online header.s=default header.b=jvsjncEG; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1674197671; a=rsa-sha256; cv=none; b=adKwE095lz2NCaN8y3K21dyKWUazHBZ+mS8/V2DTUS0Mj/1t0TuZDd+/idhuMu/exYhjxh 6xPNGJ40jYeu8jKtI56TxpW07s5Bo5M/WJMsWz8+o/mhCoLkk/Y9W6EL4+OUm5GAoa1Og6 h2UL8bAXGLxJBTV+wntOzTWbIk/r09aNr7bfr32FKHjVwcVOqHesDvnXKLT6ppHkEyZuyj JgeFTsvI3e0mYgaKm8Zu8JRe/eVAygpU+tikvlMnYB1W2weu/HswuHYniQ8vOxZEoQUcup aQJhc4V3NDguCh5tGhXOgIqupmRw5Dx7Z5+SvJWCOhwH4Z2HFNEznVncVFXygA== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: 2.59 X-Spam-Score: 2.59 X-Migadu-Queue-Id: 4C3EA3A93A Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=tsdye.online header.s=default header.b=jvsjncEG; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-TUID: dVxsM29RH4xv Aloha Max, Max Nikulin writes: > On 20/01/2023 03:09, Tim Cross wrote: >> To reiterate for the last time, there are 2 clear and different >> use >> cases for timestamps associated with meetings. >> 1. A meeting timestamp for a meeting where all the participants >> are in >> the same time zone. > ...> 2. A meeting timestamp for a meeting where all the > participants are in >> different time zones.... > > Tim, every scheduled meeting event is associated with some > particular time zone, > often implicitly. So it is single use case. > > It is up to participants to negotiate which timezone is the > primary one for each > event. It is matter of people communication, not technical > issue. > > First Monday 15:00 is (almost) equally precise for > - Australia/Canberra having DST > - Australia/Darwin where currently no DST > - +1000 (the highest chance of improper use unfortunately) > - UTC > > Aside from time transition intervals, it is possible to take any > of this variant > and to present time local for other participant across the > globe. > > Storage timezone may differ from the current user preference > which time zone > should be used to display timestamp or to export it. > > The problem arises when several participants believe that their > timezones are > primary ones and they do not sync their schedules through a > shared file or a DB > entry. An application can not solve this problem, but it might > try to help to > identify it. Some efforts are necessary from user side. > Timestamp should contain > list of timezones of other participants and cached local time. > In such case an > application may warn users that local time values become > inconsistent due to DST > transitions or due to update of time zone database. Unsure to > what degree it > should be implemented in Org. > > So > - It is participants fault if a meeting is not associated with > particular > timezone > - Having a fair time handling library, it does not matter what > time zone is used > to schedule the meeting. Or, one can recognize that the meeting is an occurrence that requires absolute time and a timestamp with UTC. Each participant will resolve UTC to the local time where they happen to be when the meeting takes place. The user might toggle between UTC and the local time translation using overlays, like pretty entities. This avoids the problem of negotiating a timezone caused by forcing an occurrence to be represented as an event relative to a fictitious space/time. hth, Tom -- Thomas S. Dye https://tsdye.online/tsdye