Friday, January 09, 2009

Proposal: [GNO] You are on the way to encryption

s/ked then vetoed—Yoda

Adminned at 09 Jan 2009 15:34:50 UTC

SHHHH

52713495957160697902506325238517626023789511657793952
60097222837091838857431183072156143825977969543445774
43254097632995592783996533632616755433337610118085670
19411667117943147390102786157216061318892513167621179
27305282471992190058121298742217086496135022857224965
46

Comments

Qwazukee:

09-01-2009 22:41:06 UTC

for

Yoda:

09-01-2009 22:41:49 UTC

against Like I said, there needs to be a way for existing propals that are in the old encryption to still be valid.  The way it is now, I can change the encryption method if I don’t like a proposal just so that it has no effect.

Qwazukee:

09-01-2009 22:58:06 UTC

How is this a problem for you, then? I would have grabbed that opportunity. But if you really object to having veto power . . . oh wait. You already have a far easier way to veto proposals. So what’s the problem (other than a slight lag everytime you want to change encryptions)?

Yoda:

09-01-2009 23:00:26 UTC

That any time I choose to change encryptions, the existing proposals are doomed to failure.

Qwazukee:

09-01-2009 23:07:20 UTC

So you wait a tiny bit before implementing the encryption change. Like, 48 hours max, since there would be no reason to make new proposals in an old encryption that needed to be changed.

Klisz:

09-01-2009 23:16:00 UTC

Perhaps Take 3 could override the rule which prevents people from editing proposals after they’re commented on.

Klisz:

09-01-2009 23:26:12 UTC

against  s/k in favor of take 3

Yoda:

09-01-2009 23:34:11 UTC

veto to clear