On 17/10/2008, comex <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 16, 2008 at 9:02 PM, Elliott Hird
> <[EMAIL PROTECTED]> wrote:
>>> What do I need to do to leave the Bayes contract?
>> Consent to your parting, I think.
>
> And Wooble's.
After e leaves eir consent is unneeded.
>
On Thu, Oct 16, 2008 at 9:02 PM, Elliott Hird
<[EMAIL PROTECTED]> wrote:
>> What do I need to do to leave the Bayes contract?
> Consent to your parting, I think.
And Wooble's.
On 17/10/2008, Dvorak Herring <[EMAIL PROTECTED]> wrote:
> Am I still a member of the Bayes Contract?
> What do I need to do to leave the Bayes contract?
>
> --
> Dvorak Herring
>
Consent to your parting, I think.
On 7 Oct 2008, at 18:36, Sgeo wrote:
To elaborate since you might not understand being new:
Next time to the Public Forum.
You sent it to a-d, but things only happen to a-b. :-P
Not true. Things like pledges can happen in a-d, as I found out to
my dismay..
Different kinda thing.
--
ehird
> To elaborate since you might not understand being new:
> Next time to the Public Forum.
> You sent it to a-d, but things only happen to a-b. :-P
Not true. Things like pledges can happen in a-d, as I found out to my dismay..
root wrote:
> Actually, "not to the public forum." "next time..." would require an
> additional t.
Heh, I always interpreted it as "now to the public forum"...
--
ais523
<>
On 4 Oct 2008, at 16:03, Ian Kelly wrote:
On Sat, Oct 4, 2008 at 8:26 AM, ehird
<[EMAIL PROTECTED]> wrote:
To elaborate since you might not understand being new:
Next time to the Public Forum.
Actually, "not to the public forum." "next time..." would require an
additional t.
-root
I was
On Sat, Oct 4, 2008 at 8:26 AM, ehird <[EMAIL PROTECTED]> wrote:
> To elaborate since you might not understand being new:
> Next time to the Public Forum.
Actually, "not to the public forum." "next time..." would require an
additional t.
-root
On 4 Oct 2008, at 00:31, ehird wrote:
On 4 Oct 2008, at 00:01, Dvorak Herring wrote:
I leave the Bayes Contract.
nttpf
--
ehird
To elaborate since you might not understand being new:
Next time to the Public Forum.
You sent it to a-d, but things only happen to a-b. :-P
--
ehird
On 4 Oct 2008, at 00:01, Dvorak Herring wrote:
I leave the Bayes Contract.
nttpf
--
ehird
On Fri, Oct 3, 2008 at 11:26 AM, ehird <[EMAIL PROTECTED]> wrote:
> Also, someone fix this, seriously. I never knew this and I bet most people
> don't, see: all the 'can join by announcement' clauses.
IIRC, the reason we added it in the first place was that most
contracts (at least those at the ti
On 3 Oct 2008, at 17:52, Ian Kelly wrote:
Or you could interpret it as requiring you to allow Dvorak to control
it indirectly.
-root
I think we'll stick to comex's interpretation for now.
Also, someone fix this, seriously. I never knew this and I bet most
people
don't, see: all the 'can j
On Fri, Oct 3, 2008 at 10:28 AM, comex <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 3, 2008 at 12:25 PM, Ian Kelly <[EMAIL PROTECTED]> wrote:
>> Or e could create eir own bayes.py that also sends messages from
>> [EMAIL PROTECTED]
>
> It's possible that bayes.py CANNOT act on behalf of Bayes, because
>
On Fri, Oct 3, 2008 at 12:25 PM, Ian Kelly <[EMAIL PROTECTED]> wrote:
> Or e could create eir own bayes.py that also sends messages from
> [EMAIL PROTECTED]
It's possible that bayes.py CANNOT act on behalf of Bayes, because
3. bayes.py is a script whose purpose is to act on behalf of Bayes in
a g
On Fri, Oct 3, 2008 at 8:40 AM, ais523 <[EMAIL PROTECTED]> wrote:
> Wow, I didn't realise that rule existed. Game custom certainly seems to
> go against it (all the contracts made recently that were intended to
> allow arbitrary persons to join have explicitly allowed that, I think).
>
> Does this
On Fri, 2008-10-03 at 08:36 -0600, Ian Kelly wrote:
> On Fri, Oct 3, 2008 at 7:19 AM, ais523 <[EMAIL PROTECTED]> wrote:
> > On Tue, 2008-09-30 at 20:57 -0500, Dvorak Herring wrote:
> >> I agree to the Bayes contract if I can.
> >>
> > This fails, the contract has no mechanism for doing so.
>
> You
On Fri, Oct 3, 2008 at 7:19 AM, ais523 <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-09-30 at 20:57 -0500, Dvorak Herring wrote:
>> I agree to the Bayes contract if I can.
>>
> This fails, the contract has no mechanism for doing so.
You forget R2198:
If a contract does not purport to regulate b
On 1 Oct 2008, at 15:10, comex wrote:
On Wed, Oct 1, 2008 at 12:14 AM, Ian Kelly <[EMAIL PROTECTED]>
wrote:
It categorizes adopted proposals as spam, rejected proposals as
non-spam, and votes against spam?
The other way around. It votes FOR stuff like adopted proposals.
Oh. Yeah.
On Wed, Oct 1, 2008 at 12:14 AM, Ian Kelly <[EMAIL PROTECTED]> wrote:
> It categorizes adopted proposals as spam, rejected proposals as
> non-spam, and votes against spam?
The other way around. It votes FOR stuff like adopted proposals.
On 1 Oct 2008, at 05:14, Ian Kelly wrote:
It categorizes adopted proposals as spam, rejected proposals as
non-spam, and votes against spam?
-root
Bingo!
On Tue, Sep 30, 2008 at 8:27 PM, comex <[EMAIL PROTECTED]> wrote:
> although it's mostly ehird's code. While I don't think it's going to
> try being the CotC anytime soon, it has a highly interesting method of
> voting on proposals. Can you guess what it is?
It categorizes adopted proposals as s
On Tue, 30 Sep 2008, comex wrote:
> On Tue, Sep 30, 2008 at 8:30 PM, Ian Kelly <[EMAIL PROTECTED]> wrote:
>> On Tue, Sep 30, 2008 at 6:15 PM, comex <[EMAIL PROTECTED]> wrote:
>>> 3. bayes.py is a script whose purpose is to act on behalf of Bayes in
>>> a generally autonomous way, controlled by the
On Tue, Sep 30, 2008 at 8:30 PM, Ian Kelly <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 6:15 PM, comex <[EMAIL PROTECTED]> wrote:
>> 3. bayes.py is a script whose purpose is to act on behalf of Bayes in
>> a generally autonomous way, controlled by the parties to this
>> contract.
>> 4. baye
On 01/10/2008, Ian Kelly <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 6:15 PM, comex <[EMAIL PROTECTED]> wrote:
>> 3. bayes.py is a script whose purpose is to act on behalf of Bayes in
>> a generally autonomous way, controlled by the parties to this
>> contract.
>> 4. bayes.py CAN cause Bay
24 matches
Mail list logo
