I think I’ll vote against this as it stands; for a start, I think that conceptually a deliberately-crafted typo is contradictory, so I don’t think any of these can be legally corrected.

Bucky did also post a 750-ish character version of this to the blog before cutting it down, which would have triggered Brevity’s “unpopular and may not be popular”.

I’m not sure if “and may not be popular” stops applying once a proposal has been edited below 400 characters, or if it’s an ongoing prohibition for the proposal, whatever later changes are made to it.

“may not be popular” ≠ “may not become popular”

Sure, but “this proposal may not be popular” is pretty hard to read as anything other than “this proposal may never be popular”.

I’m now taking more advantage of the “reformat a list of items” appendix clause so that all words can be correctly spelled and every word is delimited from every other word by either whitespace or punctuation.

Josh, “may not be popular” is denying permission, but it’s present tense.

“may be” may be in the present and the future tense.

“It may be snowing” can refer to today and tomorrow.

And you claimed my reading was untenable. Now you’re claiming it’s ambiguous. Which is it?

Using typos to get around the letter of the law still violates the spirit of the law, which is to keep the ruleset from growing too fast from any one Proposal. If the idea is too big to fit in without using tricks, split up the idea into separate Proposals.

For example, I re-wrote the proposed ruletext to introduce the main concepts like this, and it came to 271 characters:

There exists three Phone Lines, called Lines 1, 2 and 3. Each has two publicly-tracked Endpoints, defaulting to “5 Notochord”, that may be one of the following types of values:
* The name of an Idle or non-Idle Machinist
* Another Phone Line
* Text that describes a Location

You could then have another Proposal to set up the phone lines in the default configuration you actually want, but until then, you at least have the concept available and the phone lines simply route to the same place by default.

Probably should make that “publicly-tracked Phone Lines”, which only adds a handful more characters.

I would consider it unacceptable to leave the default value that unclear. I’m 90% sure the correct default would be “3Balance” for all endpoints but an enacting admin being 90% sure isn’t good enough.

I’m not “claiming” anything, Bucky, so ramp it down a little, yeah? I have said neither “untenable” nor “ambiguous” and I’m not sure why you’re putting words in my mouth.

I’d've been happier to chat around it a bit longer but if you’re going to force the issue then sure, I think on balance of evidence this is locked at unpopular. On that basis I’ll chuck an in to prevent further exciting exploration of ruleset edge cases.

Check that, the default is actually undefined. The problem is that “5 Notochord” isn’t a valid value, “00000015 km south of the New York Public Library” is for any number of 0s, and adding more 0s makes it a better default without limit.

It’s really up to you to rewrite the proposed idea to your satisfaction and split it up so that it fits the proscribed limits. I was simply offering an example. The point is, if you don’t follow the spirit of the law, you get a from me.

I try not to place a vote during the 4-hour edit window, and I would have waited on that vote above, but since Josh locked it down already, there was no further harm done by my vote.

yeah, this is… i’d much rather you just propose to raise the Brevity cap.

Player count is 10, quorum is 6 after my unidling.

I’d agree that a typo is pretty much by definition accidental.