Tuesday, August 06, 2024

Call for Judgment: No Illegal Actions

Unpopular, 0-5. Failed by JonathanDark.

Adminned at 07 Aug 2024 16:23:58 UTC

Undo the dynastic actions taken by SingularByte took between14:41 and 14:55 on 5 August 2024

Add a dynastic rule called “Revelations” with the following text

The Elder Judge must, at their earliest convenience, publicly reveal in a blog post any information privately revealed to the Fishing Contestant known as SingularByte as a result of actions taken by the Fishing Contestant known as SingularByte which took between 14:41 and 14:55 on 5 August 2024 then delete this from the rules.

Not a fan of the “you got information out of this so we’re just going to uphold your actions” approach proposed here https://blognomic.com/archive/disturbance_in_the_time_space_continuum#comments

If a piece of information is described as being tracked secretly or privately by the Elder Judge (including secretly random selections), then that information may only be revealed by the Elder Judge when the ruleset allows it.

Seems like the ruleset didn’t actually allow for certain information to be revealed, and when in doubt if private information is incorrectly revealed the best solution is to reveal it to everyone

Comments

Clucky: he/him

06-08-2024 06:49:40 UTC

if we want to informally establish that were gonna cut down on stuff like this going forward but want to chalk this up to an honest mistake and let SingularByte have this I’m okay ultimately okay with it. I’m mostly worried about the precedent it sets if we allow a play on, and then later down the road a similar situation arises and we have no choice but to allow another play on

SingularByte: he/him

06-08-2024 06:55:31 UTC

There is the strange quirk here though that this gives me, JonathanDark and Lukas the ability to get a trophy almost immediately - depending on who’s faster on the draw and who can work out the text of the Big One.

On thinking about it, a less dangerous option might be to set the timestamps of my actions to be the same as the Sight Disturbances action - that way, my actions are only considered to have been done when legally possible to do so, without giving three players a large advantage.

Clucky: he/him

06-08-2024 07:00:44 UTC

even if you have all 9 letters… you’ve still got 362880 possible names for the big one. Will it really be that easy to figure out?

SingularByte: he/him

06-08-2024 07:03:55 UTC

Potentially. JD is probably in the best position there having spent all of his catches to get 0 hits, combined with the fact that you spent all of yours to get 2 hits.

It’s building up a picture of what kind of rules we’re looking at, even from my outside perspective. It’s not a sure thing, but it’s definitely a non-zero chance of getting it - especially when you’ve got 3 people looking at it independently.

Clucky: he/him

06-08-2024 07:10:53 UTC

JD lacks catches to submit with though. So sure he might have some idea of what letter it starts with, but will get fewer guesses to try and nail it

Clucky: he/him

07-08-2024 04:58:01 UTC

as its already been 24 hours since I made this and the other CfJ passed, at this point I feel like its too late to undo this so I’ll   against

SingularByte: he/him

07-08-2024 06:15:43 UTC

against

Lukas:

07-08-2024 10:35:02 UTC

against
To clarify my own comments on that post, I’m okay with upholding SingularByte’s actions primarily because doing them in the correct order would have had exactly the same result. It is true that the difficulty of trying to undo the actions had a slight influence on whether I thought it was worth trying to make an argument against the scam (not that I had a major problem with it, but I’m still figuring out the BlogNomic culture and how my own interpretation of the rules should interface with that).

I do think making incorrectly revealed information public can work in many situations, but I’d be hesitant to make it the general rule, as it can throw everything off balance.

JonathanDark: he/him

07-08-2024 14:04:32 UTC

against

Darknight: he/him

07-08-2024 15:07:13 UTC

against