From: Juliusz Chroboczek <jch@irif.fr>
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Virtual groups v.s. new API branch
Date: Sun, 03 Mar 2024 17:07:40 +0100 [thread overview]
Message-ID: <87il23fgdv.wl-jch@irif.fr> (raw)
In-Reply-To: <D21B4C71-8D23-4CA7-923B-FA628C620C66@webweaving.org>
>> Perhaps it's worth adding "not-before" and "expires" fields to the
>> group definition, and have groups be automatically purged by the
>> server?
I've just done that.
https://github.com/jech/galene/commit/de0c42faaf1a72f1e850f64bc720fd2e824f8cb8
You may format ISO 8601 dates from the shell using
date -Iseconds -d tomorrow
from Go using
json.Marshal(time.Now().Add(time.Day)
and from Python by doing
(datetime.datetime.now() + datetime.timedelta(days = 1)).isoformat()
>>> Or is there also a plan for a more 'reactive' mechanism -- i.e. one that
>>> does not require a configuration sitting pretty `ahead' of time. We're
>>> finding this quite useful (and then lock the room one we're started).
Not opposed, but you'd need to set your requirements more clearly. Do you
want the whole "/groups" hierarchy to be fetched over HTTP on demand?
A subtree? Individual groups?
-- Juliusz
prev parent reply other threads:[~2024-03-03 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 9:20 [Galene] " Dirk-Willem van Gulik
2024-02-13 13:14 ` [Galene] " Juliusz Chroboczek
2024-02-13 13:55 ` Dirk-Willem van Gulik
2024-02-13 15:15 ` Juliusz Chroboczek
2024-03-03 16:07 ` Juliusz Chroboczek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il23fgdv.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=dirkx@webweaving.org \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox