[8pla.net]

Hello LOCKSUIT,

Three Likes... That's unbelievable!

Thanks for the Like!

[LOCKSUIT]

Definite!

[8pla.net]

Found a bug, bigger than a patch !
Young Alpha's train of thought is broken.

More than a syntax adjustment,
this will be a partial rewrite, at least.

It pays to keep new code short and simple,
rather than rush to build on top of it, I think.

[8pla.net]

Got it!

( I think... )

Searching the nearest memory, Young Alpha recalls properly.

Any ideas why Young Alpha reprogrammed itself to stop reprinting the question when asking again?

All I know is I did not program that, however it does make the interface cleaner, so it stays for now.

[8pla.net]

Thanks for the Like, LockSuit 

Let me add another link to page 2 for convenience sake...

Live Demo: http://aihax.com/codename

[Art]

Got it!

( I think... )

Searching the nearest memory, Young Alpha recalls properly.

Any ideas why Young Alpha reprogrammed itself to stop reprinting the question when asking again?

All I know is I did not program that, however it does make the interface cleaner, so it stays for now.

Perhaps...

IT'S ALIVE!!!

[LOCKSUIT]

Because it had some sort of cue or reward? Or you knew what you were doing 8pla when coding ?

[Art]

It could be a "glitch" in the code somewhere (a fall through).

Perhaps an internal condition had been met.

Could be that to code followed the next logical step.

Was there a code counter that determined a limit had been reached?

[8pla.net]

The truth is, I don't know, yet.

I ran out of time, and since it seemed to be working,

I just left it.

But, I wasn't working on the part of the code at all.

My guess is that it may be a rare software bug,

that accidentally improves the program.


Just noting, that as you can see from view source,

and from the web interface

in the browser, Young Alpha is writing its own code.

Don't worry though, it's memory gets wiped when you leave the webpage.

There is nothing logged because it is too experimental.