Popped into #LambdaMOO for a birthday celebration that took place inside my sushi restaurant. This got me to thinking. I wonder if it's possible to tie my restaurant's code into the birthday machine somehow so that people can get free food on their birthday.
#lambdamoo
1 post1 participant0 posts today
#lispyGopherClimate #live American Tuesday evening = 12am Wednesday UTC+0
#climateCrisis #haiku @kentpitman
need to repair archive
https://communitymedia.video/c/screwtape_channel/videos
#podcast #gopher #technology #gameDev #lispGameJam #programming
#interview -ing @someodd !
+ Notes from solderpunk and @tomasino
Also, ino's https://thehierophant.world exists
- someodd's games and programs
@mdhughes 46 years of game wisdom phlog
#lambdaMOO turned 35
#commonLisp https://screwlisp.small-web.org/fundamental/a-prog-feature/
#lambdaMOO #MOO #MUD 35th #anniversary #party ! #RightNow
World's longest running persistently online #virtualReality #VR https://lambda.moo.mud.org/
telnet lambda.moo.mud.org 8888
co guest
@join screwtape
(or any of the other crowd in here. The party is in the Smoking Room if you want to walk there the old fashioned way or teleport)
lambda.moo.mud.orgLambdaMOO
What do people use to map MUDs or text adventures, that isn't for fucking Windows, or unmaintained for 30 years?
#mud #moo #lambdamoo #interactiveFiction #textAdventure
Replied to screwlisp
@screwlisp @spidercat @pizzapal @me @nosrednayduj @dougmerritt
> From: AlexTheRed (#125529)
To: *chatter (#16543)
Subject: 35 Years of MOO
Talked to JCub and Mazuli, and 10 am -- 1 pm MOO time (Pacific) on October 30
sounds like a good time to celebrate the anniversary.
That overlaps with
evening in Europe and lunch breaks in US time zones.
What's your favorite
old-school MOO party venue?
<
Dining is #28, Drawing is #56651, Smoking 51556
My map is such a terrible mess.
#lambdamoo
#lambdaMOO 35th #Anniversary #VR
I guess in PDT, the MOO time zone *right now* is just after midnight Moo years eve, October 29th. So Moo years day would be 24 hours from right now.
Edit: #rightNow
Er, I lost the thread of some of the moomails I was included in plz help @spidercat @pizzapal @me @nosrednayduj @mdhughes @dougmerritt I don't even know the object numbers of the smoking room or drawing room. Boost plz
( https://lambda.moo.mud.org/ , #MUD ). Does somemastodon have the deets.
lambda.moo.mud.orgLambdaMOO
https://communitymedia.video/w/h1jdbHm8xTj5VEDuCWAbBW
#lispyGopherClimate #technology #podcast #weekly
featuring @kentpitman @ramin_hal9001 @jns
Longterm #reliability , the #climateCrisis , technology and knowledge
Kent has found the source to his Cross referenced editing facility from Open University #lisp #lispm example.
#scifi #books with this theme? Ending of Cats Cradle?
On the #art side check, @prahou 's #unix_surrealism, https://photronic.art
Happy #lambdaMOO year! 35 years! https://lambda.moo.mud.org as always.
Replied in thread
Continued thread
Not quite, but still promising. #lambdamoo
Tonight I asked Claude Code to use Google Nano Banana to make a point-and-click adventure out of actually browsing #lambdamoo via a telnet connection? Where the mind wanders sometimes...
#lispyGopherClimate
https://communitymedia.video/w/1iDniLCpYPSPjxFww6TzJ9
#climateCrisis #haiku by @kentpitman
Thinking about scarcity.
Interesting #IT notes from @AmenZwa recently
@jackdaniel 's #McCLIM #commonLisp multi-input ! (And moving towards #WECL for a few weeks)
https://functional.cafe/@jackdaniel/115334363009353916
- My #NicCLIM #gamedev and Dungeon Crawler Carl #bookReview (AMA in #lambdaMOO #live)
https://screwlisp.small-web.org/lispgames/nicclim-alpha-part-iii-map-edit-macros
I'm sure there was another topic. I think now just ping me in the hour before the show if you would like to be a guest
#LambdaMOO
(...guess it'll wait until *after* I announce that I discover some outstandingly stupid mistake, so... time to get this out of the way: )
I have now dropped LambdaMOO 1.9.0alpha
Should I make it to an actual ready-for-prime-time release, this will be the first since 1.8.1, roughly 25 years ago.
I'm looking for anyone *already* running a MOO instance of some sort (*) who needs a path forward (I figure for each of the 3 or 4 I know about there should be others I don't, which should add up to at least several)
to kick tires and try it on on your own platform
and maybe others that I can't do myself.
(*) and perhaps other folks who build unix software for fun, who are bored today
Details here:
https://wrog.net/moo/1.9.0
gahh...
feels like Mark Watney at Scapperelli crater, breaking open that last "Goodbye Mars!" meal packet.
(... such a good movie. Ridiculous, but still...
Probably the most realistic of the Mars movies.
Still ridiculous.
Because he really should have died.
NB: This is *not* Apollo 13 where the survival probability was probably around 25% and they managed to beat the odds
This is more like 0.1% and they managed to beat the odds, which only happens in movies.
Still much more realistic than the book,
in which YET MORE SHIT goes wrong, and he still lives.)
(yes, this might have a teentsy bit to do with 1.9.0a)
(yes, it's a completely ridiculous metaphor. Don't try to make too much sense of it...
need sleep)
#lispyGopherClimate #LIVE #technology #podcast
https://communitymedia.video/w/vY4A9hxkZEQCe47UBASXFa
@kentpitman #climate #haiku and note on https://climate.us
@jns #gopher #phlog about #vcfmw
Mastodon #lisp happenings recently @mdhughes etc
#emacsconf proposal deadline is Friday!
Otherwise, I did lots of #commonLisp #programming this week and will talk about the #gof_ai & #DeepLearning #AI one, and maybe my spacetime-box #NicCLIM #gamedev.
https://screwlisp.small-web.org/fundamental/classical-ai-and-deep-learning-ai-difference-in-two-examples/
https://screwlisp.small-web.org/lispgames/spacetime-boxes-nicclim/
Replied in thread
Archive is up! https://communitymedia.video/w/2YtDzQ55UsgSfuVqoexPAZ
Mostly me reading a really great vignette by Kent remembering the ANSI standards process and common #lisp (and the shock twist ending). Links on the #peertube
ggxx's rmoo for #emacs current: https://codeberg.org/ggxx/rmoo #lambdaMOO
Continued thread
@corwin @bandali @publicvoit @vnikolov @kentpitman
We will of course be hanging out live in @me 's Paradise Sushi establishment in #lambdaMOO #MUD as always!
telnet lambda.moo.mud.org 8888
co guest
@join screwtape
See you RIGHT NOW
Continued thread
https://anonradio.net:8443/anonradio
Chat as always in #lambdaMOO ! or #emacsconf .
telnet lambda.moo.mud.org
co guest
@join screwtape
Some links:
https://climatejustice.social/@kentpitman/115095772270336518
https://gamerplus.org/@screwlisp/115121392950752968
https://gamerplus.org/@dougmerritt@mathstodon.xyz/115135804001902867
https://gamerplus.org/@eduardoochs@emacs.social/115126442996930370
https://gamerplus.org/@masso@mastodon.sdf.org/115118024453938584
@kentpitman @dougmerritt @mdhughes @vnikolov @eduardoochs @masso
Replied to Judy Anderson
Thanks. I'm sure that's in violation of there license whatever it is.
The problem is without knowing what the license is for the moo how can you copyright your own work? With the GPL derivatives are automatically GPL and so you have a strong viral license in place to deal with outright theft.
Most people don't think about this kind of stuff when they are customizing a room. That's why the developers of the moo should think about it and make it clear.
part1
Replied to hairylarry
@hairylarry @me The sharing is from the object oriented nature. You inherit from some other person's object, and make modifications by overriding some verbs (i.e. methods). Or you call verbs from some utility object. Or someone does that to your code. Of course you can make it so your code is not callable in that way, but most stuff is public.
I have NO IDEA what the copyright status of MOO language code is. I get pissed when people copy my wind-up duck tutorial, change all the names to their own, and publish it on the internet. I mean, how low can you get?
And you can't modify the *server* you can only modify/inherit/call moo-language code.