On Tue, Jan 11, 2011 at 1:54 AM, Ed Murphy wrote:
> tl;dr: the alleged-NoV quoted by Wooble was ineffective, thus eir
> alleged-closing of it was also ineffective.
I should learn not to listen to comex.
Yally wrote:
> On Mon, Jan 10, 2011 at 22:19, Geoffrey Spear wrote:
>> On Tue, May 26, 2009 at 12:07 PM, Elliott Hird
>> wrote:
>>> 2009/5/26 Elliott Hird :
NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
Eyes Bleed, by publishing a report in HTML (which is not plai
On Mon, Jan 10, 2011 at 22:19, Geoffrey Spear wrote:
> On Tue, May 26, 2009 at 12:07 PM, Elliott Hird
> wrote:
>> 2009/5/26 Elliott Hird :
>>> NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
>>> Eyes Bleed, by publishing a report in HTML (which is not plain text).
>>
>> I cont
coppro wrote:
> Ed Murphy wrote:
>> coppro wrote:
>>
>>> Ed Murphy wrote:
Rule 1504, in the section on SILENCE: "The judge CAN, with 2 Support,
set the fine" etc.
>>> I'm not the judge yet, unless I missed the announcement.
>> R1728(c)(1) allows the judge to do it; R1728(c)(3) allows on
Ed Murphy wrote:
> coppro wrote:
>
>> Ed Murphy wrote:
>>> Rule 1504, in the section on SILENCE: "The judge CAN, with 2 Support,
>>> set the fine" etc.
>> I'm not the judge yet, unless I missed the announcement.
>
> R1728(c)(1) allows the judge to do it; R1728(c)(3) allows one of the
> supporter
coppro wrote:
> Ed Murphy wrote:
>> Rule 1504, in the section on SILENCE: "The judge CAN, with 2 Support,
>> set the fine" etc.
> I'm not the judge yet, unless I missed the announcement.
R1728(c)(1) allows the judge to do it; R1728(c)(3) allows one of the
supporters to do it, since R1504 doesn't
Ed Murphy wrote:
> Rule 1504, in the section on SILENCE: "The judge CAN, with 2 Support,
> set the fine" etc.
I'm not the judge yet, unless I missed the announcement.
coppro wrote:
> Ed Murphy wrote:
>> coppro wrote:
>>
>>> Ed Murphy wrote:
TTttPF and (the needed support having been achieved) I set the fine
at 3 Rests.
>>> Fails, you aren't the judge.
>> R1728(c)(3).
>>
> What authorizes me to do that?
Rule 1504, in the section on SILENCE: "The judg
Ed Murphy wrote:
> coppro wrote:
>
>> Ed Murphy wrote:
>>> TTttPF and (the needed support having been achieved) I set the fine
>>> at 3 Rests.
>> Fails, you aren't the judge.
>
> R1728(c)(3).
>
What authorizes me to do that?
coppro wrote:
> Ed Murphy wrote:
>> I wrote:
>>
>>> coppro wrote:
>>>
Sean Hunt wrote:
> Alex Smith wrote:
>> I CFJ on this; the issue of whether MIME messages containing both
>> plaintext and HTML are legal is a rather important one, and I think it
>> should go through the co
2009/5/28 Sean Hunt :
> I publish an NoV alleging that Yally violated Rule 2143, committing the
> Class-6 Crim of Making My Eyes Bleed, by means of publishing eir most
> recent IADoP's report in HTML.
>
> I contest this NoV.
>
MIME, not HTML. Maybe. Probably.
2009/5/28 Geoffrey Spear :
> Then don't submit them in any font. Send plain text, like every other
> officer. Many of whom use Gmail with no problems whatsoever.
yes plz
On Wed, May 27, 2009 at 11:15 PM, Aaron Goldfein
wrote:
> Defendant's Arguments: Regardless of my guilt or innocence on the matter, I
> believe that if I am found guilty, it would be fundamentally unjust for any
> sentencing other than DISMISS as it is standard for gmail to use MIME and I
> cannot
Ed Murphy wrote:
> I wrote:
>
>> coppro wrote:
>>
>>> Sean Hunt wrote:
Alex Smith wrote:
> I CFJ on this; the issue of whether MIME messages containing both
> plaintext and HTML are legal is a rather important one, and I think it
> should go through the courts.
I favor this c
I wrote:
> coppro wrote:
>
>> Sean Hunt wrote:
>>> Alex Smith wrote:
I CFJ on this; the issue of whether MIME messages containing both
plaintext and HTML are legal is a rather important one, and I think it
should go through the courts.
>>> I favor this case.
>> I intend, with 2 sup
coppro wrote:
> Sean Hunt wrote:
>> Alex Smith wrote:
>>> I CFJ on this; the issue of whether MIME messages containing both
>>> plaintext and HTML are legal is a rather important one, and I think it
>>> should go through the courts.
>> I favor this case.
> I intend, with 2 support, to set the fine
On Tue, May 26, 2009 at 5:29 PM, Elliott Hird
wrote:
> 2009/5/26 comex :
>> the rest of the report follows. Only after the plain-text version
>> (and 3 lines of multipart header at the top) is the HTML version.
>> Rule 2143 requires that reports be published in plain text, not *only*
>> in plain
2009/5/26 comex :
> the rest of the report follows. Only after the plain-text version
> (and 3 lines of multipart header at the top) is the HTML version.
> Rule 2143 requires that reports be published in plain text, not *only*
> in plain text.
>
MIME != plain text
On Tue, May 26, 2009 at 5:13 PM, Elliott Hird
wrote:
> 2009/5/26 comex :
>> I support. I want a precedent in favor of dual-format messages for
>> previously stated reasons. (Considering that the text/plain was first, is
>> there any mail client where this is an actual problem? Why don't you lik
2009/5/26 comex :
> I support. I want a precedent in favor of dual-format messages for
> previously stated reasons. (Considering that the text/plain was first, is
> there any mail client where this is an actual problem? Why don't you like
> it ehird?)
My eyes bled because he chose a small-sized
2009/5/26 Alex Smith :
> On Tue, 2009-05-26 at 20:40 +0100, Elliott Hird wrote:
>> Actually, no.
>>
>> These NoVs were not valid, as they did not specify the rule's power.
>>
>> NoV: Yally violated R2143, a Power-1 rule, commiting the Class-6 Crime
>> of Making My
>> Eyes Bleed, by publishing the I
On Tue, 2009-05-26 at 20:40 +0100, Elliott Hird wrote:
> Actually, no.
>
> These NoVs were not valid, as they did not specify the rule's power.
>
> NoV: Yally violated R2143, a Power-1 rule, commiting the Class-6 Crime
> of Making My
> Eyes Bleed, by publishing the IADoP report in some nonsense M
On Tue, May 26, 2009 at 10:07, Elliott Hird
wrote:
> 2009/5/26 Elliott Hird :
>> NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
>> Eyes Bleed, by publishing a report in HTML (which is not plain text).
>
> I contest this. It wasn't the Registrar's report, and the HTML wasn't
>
On Tue, May 26, 2009 at 12:15 PM, Quazie wrote:
> COE 6309 passed, ai=vi
VI has to be > 1 as well.
Nope, the conditions are vi>=ai -and- vi>1
Sent from my iPhone
On May 26, 2009, at 12:15 PM, Quazie wrote:
On Mon, May 25, 2009 at 9:20 PM, Ed Murphy
wrote:
6302 6303 6304 6305 6306 6307 6308 6309 6310 6311
ais523F F F F F F A2A
It's as much a standard as the aforementioned email headers.
Sent from my iPhone
On May 26, 2009, at 12:07 PM, Elliott Hird > wrote:
2009/5/26 Elliott Hird :
NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
Eyes Bleed, by publishing a report in HTML (which is not plain tex
Gratuitous: does the message contain a plain-text version without
artifacts? (I can't check...) If so, it's absurd to punish Yally for
including a monospaced HTML version. In Gmail and on iPhone, a
plaintext version would be displayed in variable width font (and it
can't be toggled on the
On Tue, 26 May 2009, Alex Smith wrote:
> On Tue, 2009-05-26 at 16:58 +0100, Elliott Hird wrote:
>> NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
>> Eyes Bleed, by publishing a report in HTML (which is not plain text).
>
> Arguments: R101 allows players to participate in the f
2009/5/26 Alex Smith :
> On Tue, 2009-05-26 at 16:58 +0100, Elliott Hird wrote:
>> NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
>> Eyes Bleed, by publishing a report in HTML (which is not plain text).
>
> Arguments: R101 allows players to participate in the fora. Email format
On Tue, 2009-05-26 at 16:58 +0100, Elliott Hird wrote:
> NoV: Yally violated R2143, commiting the Class-6 Crime of Making My
> Eyes Bleed, by publishing a report in HTML (which is not plain text).
Arguments: R101 allows players to participate in the fora. Email format
is not plain text either, bec
30 matches
Mail list logo
