Additional gratuity:
There are currently several people who can push to those links (via GitHub)
without the push/overwrite being visible or evident to someone following the
link. However, the underlying github repo (not findable from those links)
would show the commit history that can be cross-referenced link publication
timestamps (e.g. as CFJ evidence).
The judge should consider whether it's "beyond a reasonable effort" for a
typical player to check the underlying evidence (including comparing message
and github date stamps) when verifying whether a document is the correct one.
(this is a "if the rules are silent...for the good of the game" argument if
the matter is otherwise unclear).
I'm thinking of this in terms of trying out github as a public forum, I'm not
opposed in principle, but the default interface of github focuses on the Now,
and requires more digging to go through history as opposed to say the mail
archives (e.g. if an officer is ordering transactions in a log or needs to
know if A happened before B). Not sure if there's some tools that I don't
know about that would make it easier.
On Wed, 20 Jun 2018, Publius Scribonius Scholasticus wrote:
> I, for one, would be willing to experiment with it, if we made sure that
> there was strict protections both technically and in the rules to avoid
> tampering or loss of information.
>
> On 06/20/2018 05:17 PM, Alex Smith wrote:
> > On Wed, 2018-06-20 at 17:11 -0400, Publius Scribonius Scholasticus
> > wrote:
> >> I raised the issue of having a certain GitHub repository as a public
> >> forum and people opposed it because it would not be within the TDoC
> >> of a member and it would break the precedent of mailing lists being
> >> public fora.
> > We've had public fora that weren't mailing lists before now (although
> > admittedly, it was a consequence of a scam).
> >
> > I'm opposed to being required to use any external interface to
> > participate in the game. On the other hand, I'm less opposed to being
> > /permitted/ to use an external interface to participate in the game.
> > Reports could still go to a-o if necessary.
> >
> > It's probably a good idea to have an email copy of everything for
> > recordkeeping purposes (i.e. Agora historical records, rather than
> > recordkeepor records), but we could post that to the email archives
> > from the Git repository using a hook, or perhaps in batches.
> >
>
> --
> ----
> Publius Scribonius Scholasticus
>
>
