#lambdamoo — Public Fediverse posts

So, it seems LLMs are really good at generating test cases, that *this* at least is one application they're ideally suited for.

Clearly, the question of whether something is a bug has pretty much *nothing* to do with how it was found, and finding the bug is better than NOT finding the bug.

That even if, say, it turns out that it was Jeffrey Epstein who found the bug, I should not care; it still goes on the list of things to fix.

But then I think about the pressure experiments Nazi doctors performed on death-camp inmates (i.e., following exactly ZERO ethical guidelines), producing valuable data (1) that essentially could not have been produced any other way, (2) that professional divers rely on to this day.

Discuss.

#LambdaMOO

@darkgriffin
There is an object-oriented mud, MOO. The most well-known instance is LambdaMOO. The original server code dates back to 1990; it has been updated since then. The current maintainer, @wrog, has been working on a major update which includes Y2038-proofing, adding 64-bit integers, and a number of other major improvements, but this is not yet released. For more, including the git hub link, see https://lambda.moo.mud.org

Maybe you know about this already, but I didn't see it mentioned in the other replies so I thought I would do so.

#LambdaMOO

#lisp The Delete Problem #lambdaMOO immersive #VR Alexandrian architecture with Ramin Honary #lispyGopherClimate

https://toobnix.org/w/kSbsFxarX8FAb8c55BsZVt

#lisp is the premier #VR language community ! #lambdaMOO and trying-harder. yduJ's moo.el #emacs. Mic working at least.

https://toobnix.org/w/m4AdkbJgRQ1prjSvSrirQG

I made a codeberg account and added the moo.el that I have been using for the past N decades after getting permission from the original authors (in 1990) to GPL it and publish it. I did not get permission from any of the people who have made changes along the way and emailed it around. (You know who you are.)

https://codeberg.org/nosrednayduj/moo-el

#LambdaMOO #Emacs

#climateCrisis with Kent Pitman and Ramin Honary, #lambdaMOO digging a new #gofaiLab and #lispyGopherClimate community

https://toobnix.org/w/1wbMEGRvVeRrbSviJVxy8H

DEAD MIC #lispyGopherClimate live installing #acl2 #lisp #fol and #lambdamoo using #emacs #tramp over #i2p #ssh .

https://toobnix.org/w/7BpQvVU9KQnKWVsVWF2HNb

My favorite hashtag to follow on Mastodon is #LambdaMOO

IYKYK

Oops. We just upgraded our linux machine, and now it has emacs 30.2, and moo.el doesn't work!

Package cl is deprecated
let: Wrong type argument: symbolp, #<obarray n=55>

Investigating shows that a value in mud-worlds is not a symbol. I guess I'll have to actually learn how to use the debugger... And remember how to use emacs lisp. In fact it appears that the first element in mud-worlds may be intended to be the value of mud-worlds. But (elt (elt mud-worlds 0) 0) (and length and other functions) give (wrong-type-argument sequencep #<obarray n=55>). Did something change in obarray with emacs 30?

@kentpitman You did something for emacs 29, so tagging you...

#LambdaMOO #emacs

#lambdaMOO #sixel #scheme #schemacs #lisp #interface #learning #accessibility w/ Ramin, Kent Pitman #lispyGopherClimate

https://toobnix.org/w/a81QeDWyq3hrNUKp7bELZa