concepts, and their names

[iddi01]

If you mean threads like your tflock,

Or this very thread we're posting in. It's quite hot already despite the creator being completely inactive. In this case however, it shouldn't be called a success, because certain sandbox threads (like the historical Random Posts) have a strong tendency to be uncontrollably hot.

If you mean a thread like Grounded Life (i.e., getting loads of posts in late 2023 despite the thread being created more than ten years ago),

Or Unrecognized CA thread. The creator seems to have posted nothing after creating it, but it's now the largest thread (in terms of view counts) in the OCA forum. However, it shouldn't be called a success either, for generalized threads generally gets more posts.

If it's 3-state INT, then you're FWKnightship (or me if it's 3-state OT).

Even though they're good, they're not nearly good enough to give said feeling. JvN29 and Perrier does though.
(I'm assuming you meant SoManyShips2 and Ignorance)

47. An rle like this:

Code: Select all

x = 0, y = 0, rule = Perrier
H.E.L.L.O$W.H.A.T$D.O$V.O.U$T.H.I.N.K$A.B.O.U.T$T.H.I.S$F.O.R.M$O.F.$T.E.X.T!

48. Adding an user namespace page to a category
49. A link to a user page in the main namespace
50. A main namespace redirect to an user page
51. A rule fast to apgsearch despite having a 4-cell sqrt growth (edit: how can a 4-cell pattern be rare?)
52. A rule having so many different common speeds that it is unapgsearchable (due to faster spaceships catching up with slower ones) (edit: that rule is 2-state, and actually has only 4 common spaceships (it's enough to cause that))
53. Discovering something notable on your first haul to b3s23/C1

[b-engine]

47. An rle like this:

Code: Select all

x = 0, y = 0, rule = Perrier
H.E.L.L.O$W.H.A.T$D.O$V.O.U$T.H.I.N.K$A.B.O.U.T$T.H.I.S$F.O.R.M$O.F.$T.E.X.T!

48. Adding an user namespace page to a category
49. A link to a user page in the main namespace
50. A main namespace redirect to an user page
51. A rule fast to apgsearch despite having a 4-cell sqrt growth
52. A rule having so many different common speeds that it is unapgsearchable (due to faster spaceships catching up with slower ones)
53. Discovering something notable on your first haul to b3s23/C1

47. RLE texting.
48. Invalid.
49. Userpage link.
50. User space redirect.
51. That sqrt growth is rare.
52. SoManyShips10 (?)
53. You're lucky.

54. Discovering small stable reflector
55. Smallest orthogonoid
56. Discovering adjustable spaceship in 3-state OTCA
56. Rule with most oscillators
57. Invent a completely new technology in a CA
58. Slowest explosive growth
59. Most boring rule
60. CA textbook

Also, JVN29 and Perrier are engineered CAs.

[confocaloid]

22. A thread getting hot without the thread creator posting

when I first saw this item, I thought it was specifically about threads that are "about such-and-such CA rule" (new activity would mean that several people recently got interested in an "old" CA rule). I did not connect that to threads such as TFYUCA/MDiOCA or "meta" general discussion threads like this one.
The distinction between "activity because of the OP posting" and "activity because of other people posting" could make sense when the topic could meaningfully "compete" with topics of other threads for attention / for being famous™. while collection threads such as TFYUCA and MDiOCA don't have that property, so it becomes mostly unimportant who is the OP and whether they're active in the thread.

added: "old" CA rules with very simple definitions (such as many easily-rediscoverable Life-like cellular automata) also lack that property. B35/S23, B36/S23, B38/S23, B2/S were explored early, and those CA rules have sufficiently simple definitions that it makes very little sense to argue whether or not they are "popular" or "famous". Those CA rules are on a likely path of rediscovery for anyone interested in cellular automata.

[confocaloid]

45 Jam on infinitely lengthened triskaidekapole
50 Cross-namespace redirect
52 Overunity explosion?
53 Beginner's luck
54 Hunting the Snark
59 Every [other] cell dies or stays dead


61. When a thread for someone's CA gets only one post by them by the time when there are already multiple posts by others

[eRroR_6o6]

62. when you're running a (moderately) large soup at a (moderately) large scale, and some active region either inside or outside the soup looks like a notable thing (either unrecognized oscillator, spaceship, puffer, or something like that), but seems to hit an object causing it to destruct.
So you spend at least a minute finding the time and place you saw it and copy-pasting the region into empty space, and when you finally run it, it's either a common already-known object or just that, an active region.

(this might or might not be extremely specific)
(probably because i might or might not have experienced it multiple times before)

Edit: more broad things

63. when you forget to include the slash in the ending code tag so your entire post after that ends up in the rle
64. when there's nothing else to discover in your rule
65. accidentally quoting your post instead of editing it (without knowing)
66. being sure you pressed cmd+c but you didn't
67. being paranoid of 66 so you do cmd+c*10^10^100

[b-engine]

63. when you forget to include the slash in the ending code tag so your entire post after that ends up in the rle
64. when there's nothing else to discover in your rule
65. accidentally quoting your post instead of editing it
66. being sure you pressed cmd+c but you didn't
67. being paranoid of 67 so you do cmd+c*10^10^100

63. Mistype
64. That's the end of the rule.
65. Misclick You can click the browser go back [ <- ] button
66. You're on WIndows.
67. Are you a Mac user? I doesn't even know how to type c followed by 10^10^100 0s
-
68. Trying to get WLS to work in Android
69. WLLS
70. What had Conway done?

[confocaloid]

64. when there's nothing else to discover in your rule

64. That's the end of the rule.

But really, this rule is dying. I can't do anything anymore. I only posted because of dvgrn.

That kind of attitude is the only reason Conway's Life has orders of magnitude more discoveries than any other rule. Somewhere around 1971 John Conway basically tried to say that B3/S23 was dead -- but then a bunch of unreasonable people refused to believe him.

LeapLife today is about where B3/S23 was in 1971... well, maybe not quite that far along. By 1971 there were more people doing fairly good systematic searches in B3/S23 than LeapLife has seen so far.

[Haycat2009]

54. Discovering small stable reflector
55. Smallest orthogonoid
56. Discovering adjustable spaceship in 3-state OTCA
56. Rule with most oscillators
57. Invent a completely new technology in a CA
58. Slowest explosive growth
59. Most boring rule
60. CA textbook

In order:
Instant fame and fortune
Einstein, the rule
Happiness
Most rules - many rules have infinitely extensible oscillators
Instant fame, a Youtube video, toppling the rule of Conway Life (In a different sense of the word "rule") and fortune
O(sqrt(log(t))) (Actually true)
Hard to say
Our work

71. Refusing to use uppercase letters
72. The difficulty of finding p19/p41
73. The magic of prime oscs.

[b-engine]

71. Refusing to use uppercase letters
72. The difficulty of finding p19/p41
73. The magic of prime oscs.

71. You don't know what is shift key.
72. The difficulty of hunting something decides the year of discovery.
73. A LCM osc can't have prime period. Dependent or independent reflectors are also hard to find.
-
74. Making an orthogonoid
75. Discovering engineered object in a soup
-
Did you forget this?

59. Most boring rule

[eRroR_6o6]

Did you forget this?

59. Most boring rule

they said "hard to say"

[confocaloid]

they said "hard to say"

They edited that in later; it wasn't there initially.

Anyways

76. Writing and posting ruletables in pseudocode, just to make them somewhat more human-readable
77. Accidentally creating a file named 'table: 0x60e5716306c0_testing_3_16.rule' and not noticing it until two hours later

[tommyaweosme]

8. When you call a small lake "misshapen honeyfarm" by tommyawesome

two things
1. you deadnamed me. its tommyaweosme
2. i always allow people to use me as an example of stupidity/newbieness/whatever

[Haycat2009]

Did you forget this?

59. Most boring rule

they said "hard to say"

Use the pronoun “it” please.

Anyways

76. Writing and posting ruletables in pseudocode, just to make them somewhat more human-readable
77. Accidentally creating a file named 'table: 0x60e5716306c0_testing_3_16.rule' and not noticing it until two hours later

76: Explaination. Frankly this virtue is too rare.

77. Being careless

[eRroR_6o6]

they said "hard to say"

Use the pronoun “it” please.

ok
it's just that I automatically use "they" for pronouns I don't know

Anyway:

78. when your rule is stable on C1 but is basically Seeds on other symmetries

[confocaloid]

78. when your rule is stable on C1 but is basically Seeds on other symmetries

Sometimes it's the other way round. Try apgsearching b36ns237c in the C1 census. I would be surprised if you manage to submit more than two or three C1 hauls using unmodified official apgsearch.

[b-engine]

79. An apgsearchable rule with a 5-cell dirty quadratic replicator
80. When you messing up with LWOD and LFoD, especially if Live Free or Die is suspiciously similar to Life Free of Die

[hotcrystal0]

81: When you attempt a seemingly impossible weld and find out that everything fits perfectly (check the honey ring-based sparker)

[d/dx]

It's quite hot already despite the creator being completely inactive.

Did you say something about me?

I might not be active here but I am active. This thread should be dead now but it's not somehow (and that's a good thing btw)

This thread isn't going where I expected it to but that's fine too.

[b-engine]

81. Crashing spaceships together to prove a rule Turing complete (That's what Matthew Cook done)
82. Mashing large oscillators to just hassling a small region