WEBVTT


00:00:02.899 --> 00:00:03.260
[Speaker 0]: Right. Okay, so hi everyone.

00:00:04.540 --> 00:00:04.839
We are now live. Hi Howard,

00:00:06.339 --> 00:00:06.839
how are you doing? Great.

00:00:09.960 --> 00:00:10.460
Lovely to hear. As usual,

00:00:11.980 --> 00:00:12.480
it's always a pleasure to see your

00:00:14.440 --> 00:00:14.599
presentation and the amount of time and

00:00:15.360 --> 00:00:15.780
energy you put into it.

00:00:17.680 --> 00:00:17.860
Slightly sorry about the shoppiness of the

00:00:18.680 --> 00:00:19.119
broadcast. Do not worry,

00:00:22.700 --> 00:00:23.200
the talk will be in its full 30 fps quality

00:00:24.779 --> 00:00:25.160
on the website after the conference.

00:00:26.759 --> 00:00:26.939
Actually, right now. It's available right

00:00:30.099 --> 00:00:30.279
now. As usual, feel free to ask your

00:00:31.560 --> 00:00:31.920
questions in the in the pad.

00:00:34.200 --> 00:00:34.360
We've linked it both on the talk page and on

00:00:38.400 --> 00:00:38.760
IRC. I think I am on the right 1,

00:00:40.080 --> 00:00:40.580
right? This is a solo.

00:00:42.660 --> 00:00:43.160
Guys, questions, where are they?

00:00:45.060 --> 00:00:45.300
Oh, we do have questions,

00:00:46.920 --> 00:00:47.240
it's just that they're not in the right part.

00:00:47.960 --> 00:00:48.340
Okay, so I'm going to start,

00:00:49.739 --> 00:00:49.920
I'm going to read the questions to Howard and

00:00:50.860 --> 00:00:51.260
Howard will be answering them.

00:00:52.960 --> 00:00:53.220
And if you are interested in asking questions

00:00:54.620 --> 00:00:54.860
directly to Howard, I see a lot of people

00:00:55.640 --> 00:00:56.140
have joined us on BBB,

00:00:58.540 --> 00:00:58.780
so we'll first go through the questions on

00:01:00.800 --> 00:01:01.020
the pad and then we'll move on to the people

00:01:03.340 --> 00:01:03.560
on BBB. So Howard, starting with the first

00:01:06.300 --> 00:01:06.460
question, does table data allow for

00:01:08.640 --> 00:01:08.800
recursion, e.g. The result that returns they

00:01:10.600 --> 00:01:10.940
are random monster haunting the cavern

00:01:14.060 --> 00:01:14.280
entrance and we roll on random monster and

00:01:16.420 --> 00:01:16.700
inject them, inject into the result?

00:01:17.920 --> 00:01:18.420
Sorry a little bit of a complicated question.

00:01:21.900 --> 00:01:22.200
Do you want me to read it again,

00:01:23.620 --> 00:01:24.120
perhaps? Yeah, I think so.

00:01:25.240 --> 00:01:25.740
I didn't quite catch that.

00:01:28.860 --> 00:01:29.060
Okay, so does the table data allow for

00:01:30.180 --> 00:01:30.550
recursion? So I think...

00:01:31.560 --> 00:01:31.880
[Speaker 1]: Oh, yeah, yeah, yeah, yeah.

00:01:33.960 --> 00:01:34.240
No, it does. I put a little,

00:01:35.440 --> 00:01:35.940
you know, there's some code that could,

00:01:38.660 --> 00:01:38.940
so you could, yeah, you get a random value

00:01:41.040 --> 00:01:41.380
that gets inserted and that random value

00:01:43.280 --> 00:01:43.580
could refer to another table and it can keep

00:01:46.000 --> 00:01:46.500
on going. I have not pushed that that hard

00:01:48.320 --> 00:01:48.820
because obviously it's,

00:01:50.880 --> 00:01:50.980
it might be a little on the heavyweight side.

00:01:52.540 --> 00:01:52.760
I can't imagine it to go too deep,

00:01:52.760 --> 00:01:53.260
though.

00:01:56.820 --> 00:01:56.979
[Speaker 0]: I'm pretty sure Emacs would be complaining if

00:01:57.940 --> 00:01:58.320
you go a little too deep.

00:01:59.979 --> 00:02:00.479
We have something as Mike's list recursion,

00:02:01.420 --> 00:02:01.840
and stuff like this. So don't worry.

00:02:03.440 --> 00:02:03.940
Go willy nilly with your recursions.

00:02:07.120 --> 00:02:07.240
We've got comments about the fact that it's a

00:02:09.180 --> 00:02:09.680
really cool project and I feel like everyone

00:02:10.680 --> 00:02:11.180
watching would be agreeing.

00:02:14.100 --> 00:02:14.340
You've got a question about where you can get

00:02:16.620 --> 00:02:16.780
this. Do you have a github repository with

00:02:17.080 --> 00:02:17.580
all of this?

00:02:20.440 --> 00:02:20.600
[Speaker 1]: Yeah, and at the well at the end of the

00:02:22.840 --> 00:02:22.960
presentation I kind of display that and I

00:02:25.920 --> 00:02:26.420
think I put it at the top of the the pad

00:02:35.220 --> 00:02:35.720
[Speaker 2]: Yeah, there's a

00:02:36.760 --> 00:02:37.260
[Speaker 0]: Yes. I don't go Gone please.

00:02:38.680 --> 00:02:38.820
[Speaker 1]: Nothing there. There's a lot of stuff that

00:02:40.080 --> 00:02:40.580
needs to be reformatted.

00:02:46.820 --> 00:02:46.940
This is all Aflacode, so obviously it's a

00:02:49.180 --> 00:02:49.480
personal hack. So people should just steal

00:02:51.880 --> 00:02:52.160
the code as opposed to looking at a real

00:02:52.760 --> 00:02:53.260
project to use.

00:03:00.420 --> 00:03:00.660
[Speaker 0]: Right, lovely. So this game plus CRDT should

00:03:01.960 --> 00:03:02.460
be great for non-solid plays.

00:03:03.640 --> 00:03:04.140
Are you familiar with CRDT?

00:03:08.160 --> 00:03:08.360
[Speaker 1]: Well, so I used to use Flubits once upon a

00:03:11.880 --> 00:03:12.160
time and after seeing the previous talk on

00:03:14.060 --> 00:03:14.340
CRDT it's like, oh, I like that,

00:03:16.000 --> 00:03:16.500
and yes, I think that would be a fun idea.

00:03:19.860 --> 00:03:20.080
[Speaker 0]: I think I remember, so I did something much

00:03:21.040 --> 00:03:21.300
more humble than you did.

00:03:24.660 --> 00:03:24.960
I did a little bit, a little package in Org

00:03:27.940 --> 00:03:28.080
Mode for rolling dice and you had like a

00:03:31.560 --> 00:03:31.780
little formula like you could write 60 20 and

00:03:34.740 --> 00:03:35.240
it would throw 6 dice with 20 faces,

00:03:39.060 --> 00:03:39.560
60 sorry, 6 die, Frenchmen here in the room,

00:03:43.660 --> 00:03:43.980
20 faces and it would average them out or

00:03:45.140 --> 00:03:45.640
provide you any kind of stats needed.

00:03:48.800 --> 00:03:49.020
And this type of stuff works really well over

00:03:52.540 --> 00:03:53.040
CRDT because it's 1 edit inside of a file.

00:03:55.900 --> 00:03:56.320
If you start making edits in different parts

00:03:58.780 --> 00:03:59.040
of your file, it starts becoming a little

00:04:02.060 --> 00:04:02.260
more complicated because CRDT struggles when

00:04:04.480 --> 00:04:04.640
you're making many discrete changes inside of

00:04:05.640 --> 00:04:06.140
the same file. Does that make sense?

00:04:07.640 --> 00:04:08.140
[Speaker 1]: It does, it does. Interesting.

00:04:10.120 --> 00:04:10.280
Okay, yeah, no, I have not played with it

00:04:10.280 --> 00:04:10.780
yet.

00:04:14.280 --> 00:04:14.540
[Speaker 0]: Well, feel free to play with it and if you've

00:04:16.320 --> 00:04:16.820
got any kind of... If it works,

00:04:17.720 --> 00:04:18.120
it works and it's amazing,

00:04:20.200 --> 00:04:20.380
but if it doesn't, feel free to send us

00:04:21.180 --> 00:04:21.680
messages because Shantan,

00:04:23.240 --> 00:04:23.740
who's the maintainer of CRDT,

00:04:25.840 --> 00:04:26.000
we've been looking into options to make it a

00:04:28.380 --> 00:04:28.880
little more resilient and work elsewhere for

00:04:31.360 --> 00:04:31.860
securely. Excellent. All right,

00:04:34.600 --> 00:04:35.080
Great. I'm going back to the previous

00:04:37.160 --> 00:04:37.500
question. So does the current version also

00:04:39.020 --> 00:04:39.520
have some utilities for doing multiplayer,

00:04:41.140 --> 00:04:41.640
like either physically or digitally,

00:04:42.520 --> 00:04:43.020
like we've done with CRUT?

00:04:45.060 --> 00:04:45.300
The question is because you mentioned you

00:04:47.360 --> 00:04:47.860
previously did multiplayer session as well?

00:04:51.180 --> 00:04:51.680
[Speaker 1]: Yeah, I mean, I was using the table,

00:04:55.940 --> 00:04:56.060
the random table at a random entry kind of

00:04:58.460 --> 00:04:58.960
thing. I was using that at my table.

00:05:00.780 --> 00:05:01.280
So, I'm an eternal DM.

00:05:02.920 --> 00:05:03.420
So I would always use that.

00:05:05.020 --> 00:05:05.220
Like somebody says, what's the name of that

00:05:07.160 --> 00:05:07.400
shopkeep? And I could just hit a key,

00:05:08.440 --> 00:05:08.660
and it'd come up with the name,

00:05:10.120 --> 00:05:10.620
and I'd just read it off.

00:05:14.440 --> 00:05:14.940
But it was still me generating it.

00:05:17.120 --> 00:05:17.540
So it wasn't something that people would see

00:05:19.540 --> 00:05:19.640
necessarily, but I would keep notes in it and

00:05:20.520 --> 00:05:21.020
then publish those notes.

00:05:24.240 --> 00:05:24.620
But yes, I don't know.

00:05:25.440 --> 00:05:25.940
This sounds all kind of,

00:05:27.260 --> 00:05:27.760
this sounds all intriguing.

00:05:28.840 --> 00:05:29.340
I think this would be fun.

00:05:32.220 --> 00:05:32.720
I think I need to get a group of like-minded

00:05:35.880 --> 00:05:36.380
Emacs people who want to play online.

00:05:39.860 --> 00:05:40.120
[Speaker 0]: I'm sure you've got plenty of people not only

00:05:41.580 --> 00:05:42.080
watching but also here in BBB.

00:05:44.660 --> 00:05:44.800
So we only have about 14 minutes until we go

00:05:46.120 --> 00:05:46.360
to the next talk and it might be a little

00:05:48.200 --> 00:05:48.700
short for a campaign, but we might just...

00:05:53.220 --> 00:05:53.720
Moving on to the next question,

00:05:56.480 --> 00:05:56.920
how does 1 become super awesome like Howard

00:05:58.200 --> 00:05:58.620
Abrams? And I very much agree.

00:05:58.700 --> 00:05:59.140
[Speaker 1]: Sure, yes. That's kind,

00:06:04.460 --> 00:06:04.600
[Speaker 0]: That's not a secret, You're not giving your

00:06:09.360 --> 00:06:09.800
[Speaker 1]: too kind, too kind. There's no trade secrets.

00:06:10.580 --> 00:06:11.080
Just follow your passions.

00:06:14.540 --> 00:06:15.040
[Speaker 0]: trade secrets. I can only conquer.

00:06:16.160 --> 00:06:16.660
All right, moving on to the next question.

00:06:18.740 --> 00:06:19.200
Please talk a little about how you produced

00:06:20.460 --> 00:06:20.960
such a slick presentation video.

00:06:22.800 --> 00:06:23.300
Everything looked completely professional,

00:06:25.120 --> 00:06:25.620
and I'd agree. So tell us more.

00:06:29.260 --> 00:06:29.760
[Speaker 1]: OK, so as you've seen my previous

00:06:32.680 --> 00:06:33.180
presentations, It's all just Emacs screen.

00:06:35.920 --> 00:06:36.060
I just felt like, oh, what I really want to

00:06:39.360 --> 00:06:39.560
talk about is how much fun I'm having and the

00:06:43.680 --> 00:06:43.840
little introduction. So my son actually is a

00:06:44.980 --> 00:06:45.240
YouTuber. So I asked him,

00:06:47.200 --> 00:06:47.360
and it's like, oh, I'll take care of your

00:06:49.940 --> 00:06:50.440
dad. And so he's the 1 that kind of prompted

00:06:51.280 --> 00:06:51.780
me. So I had a director.

00:06:53.720 --> 00:06:54.220
Don't know if that translates,

00:06:58.940 --> 00:06:59.340
[Speaker 0]: I mean, that translates amazingly.

00:07:02.560 --> 00:07:03.060
[Speaker 1]: though, but. Very good.

00:07:06.900 --> 00:07:07.400
You know, very over the top.

00:07:09.440 --> 00:07:09.940
I've never done something like this before.

00:07:10.460 --> 00:07:10.600
[Speaker 0]: I mean, the results at the end is No,

00:07:11.680 --> 00:07:12.040
but it fits you so well.

00:07:14.820 --> 00:07:14.980
I think this over the top-ness combined with

00:07:15.800 --> 00:07:16.300
the editing, it just...

00:07:18.900 --> 00:07:19.200
[Speaker 1]: I might have to keep doing it because it was

00:07:20.600 --> 00:07:21.100
fun. It was fun to do.

00:07:23.160 --> 00:07:23.300
[Speaker 0]: You've set a standard that you'll need to

00:07:24.520 --> 00:07:24.860
meet for following Emax.

00:07:28.360 --> 00:07:28.860
[Speaker 1]: I'll have to keep paying them then.

00:07:30.820 --> 00:07:31.320
[Speaker 0]: Oh no! Alright, Yes! Alright,

00:07:32.360 --> 00:07:32.860
moving on to the next question.

00:07:35.380 --> 00:07:35.540
Does table data, no sorry that's the 1 we did

00:07:37.360 --> 00:07:37.680
on recursion and we're not going to struggle

00:07:38.900 --> 00:07:39.400
through the reading of it again.

00:07:41.280 --> 00:07:41.780
Alright so with your toolkits,

00:07:43.940 --> 00:07:44.060
a list of good books would be nice to be

00:07:45.300 --> 00:07:45.800
included, example D&D,

00:07:48.400 --> 00:07:48.900
space, steampunk, cyberpunk settings.

00:07:49.800 --> 00:07:50.300
Do you have such a plan?

00:07:56.120 --> 00:07:56.360
[Speaker 1]: 00I mean, I could definitely publish a

00:07:59.640 --> 00:08:00.140
bibliography of things I'm using and reading,

00:08:03.640 --> 00:08:04.140
But I don't know if I'd be writing anything.

00:08:07.420 --> 00:08:07.640
[Speaker 0]: Oh come on, don't tell yourself short.

00:08:09.000 --> 00:08:09.140
You've already proven you were amazing in

00:08:10.640 --> 00:08:11.140
very different, very varied topics.

00:08:12.840 --> 00:08:13.340
I'm sure you should give it 1 more try.

00:08:15.460 --> 00:08:15.740
[Speaker 1]: I don't know. I've got a sabbatical coming

00:08:17.580 --> 00:08:17.840
up. I'm toying with writing something,

00:08:19.860 --> 00:08:20.360
but I don't know if it'd ever leave the Emacs

00:08:20.440 --> 00:08:20.940
buffer.

00:08:23.680 --> 00:08:24.180
[Speaker 0]: All right, I like this.

00:08:28.140 --> 00:08:28.260
Next question. Hi Howard and thanks for an

00:08:28.860 --> 00:08:29.360
outstanding presentation.

00:08:31.640 --> 00:08:31.800
What did you use to create the graphics in

00:08:34.280 --> 00:08:34.440
your presentation? Didn't we cover this 1

00:08:35.059 --> 00:08:35.380
already? I can't remember.

00:08:35.740 --> 00:08:35.860
No, that was

00:08:41.980 --> 00:08:42.240
[Speaker 1]: a good 1. So the graphics actually were just

00:08:43.179 --> 00:08:43.679
kind of hacked together.

00:08:45.020 --> 00:08:45.340
But then I just gave them to my son.

00:08:47.200 --> 00:08:47.520
And it's like, can you put the graphic right

00:08:50.140 --> 00:08:50.640
here and he goes no problem there it is like

00:08:56.280 --> 00:08:56.640
[Speaker 0]: okay great so 1 more 1 more reason to keep

00:08:57.060 --> 00:08:57.560
paying your son

00:08:59.820 --> 00:09:00.180
[Speaker 1]: perfect yeah yeah exactly so if you can get

00:09:02.760 --> 00:09:03.260
get yourself a YouTuber who knows how to use

00:09:05.800 --> 00:09:06.300
all the tools. I think he was using DaVinci,

00:09:08.860 --> 00:09:09.360
but he's got quite a few going.

00:09:12.700 --> 00:09:12.900
[Speaker 0]: Right. Alright, moving on to the next

00:09:15.040 --> 00:09:15.220
question. Any plans to borrow tables from

00:09:17.980 --> 00:09:18.240
Dungeon World or Iron Sword Starforge and

00:09:20.460 --> 00:09:20.960
publish in a TK repository?

00:09:22.360 --> 00:09:22.860
Not sure what TK is.

00:09:25.380 --> 00:09:25.880
[Speaker 1]: Yeah, yeah, okay. So yeah,

00:09:30.320 --> 00:09:30.820
so that would be fun and I'd love that.

00:09:33.840 --> 00:09:34.340
And I was just reading a way to render PDFs

00:09:38.080 --> 00:09:38.480
that you might own into Markdown format.

00:09:39.140 --> 00:09:39.560
And if it's in Markdown,

00:09:41.440 --> 00:09:41.940
it'd be easy to pull into Org Mode.

00:09:43.680 --> 00:09:44.180
So all of the Iron Sworn,

00:09:45.280 --> 00:09:45.780
that role-playing game,

00:09:48.780 --> 00:09:49.280
Since it's all under the Creative License,

00:09:51.380 --> 00:09:51.600
I think even the Star Forge is.

00:09:53.940 --> 00:09:54.280
So I think I could grab the Star Forge 1.

00:09:56.820 --> 00:09:57.100
I don't know about Dungeon World and their

00:09:59.220 --> 00:09:59.380
tables. But yeah, a lot of people are

00:10:01.060 --> 00:10:01.500
starting to publish those kind of tables.

00:10:03.760 --> 00:10:04.180
So yeah, that'd be fun.

00:10:07.160 --> 00:10:07.400
I'd like to render all those in text files

00:10:08.560 --> 00:10:09.060
that I could pull up like that.

00:10:13.180 --> 00:10:13.580
[Speaker 0]: Lovely. I think that's all for the questions

00:10:15.820 --> 00:10:16.320
we had in the pad. We still have 9 minutes.

00:10:18.280 --> 00:10:18.760
I see plenty of people have joined us,

00:10:21.060 --> 00:10:21.560
including 1 person with a microphone on BBB.

00:10:23.160 --> 00:10:23.500
PlasmaStrike, do you have a question?

00:10:24.920 --> 00:10:25.180
And would you like to unmute yourself and ask

00:10:28.440 --> 00:10:28.940
it? I'm also going to check the chat.

00:10:31.640 --> 00:10:31.920
[Speaker 1]: Oh, yeah. StarsWithoutNumber is another great

00:10:33.640 --> 00:10:34.140
1 that's got some great tables in it.

00:10:37.720 --> 00:10:37.960
Sorry, I'm just looking at the questions that

00:10:38.940 --> 00:10:39.440
are popping up here, too.

00:10:42.740 --> 00:10:43.180
[Speaker 0]: Sure. So I don't see anyone unmuting

00:10:44.540 --> 00:10:44.800
themselves. I see people typing away

00:10:45.220 --> 00:10:45.400
questions. By the way,

00:10:46.120 --> 00:10:46.560
if you're going to type questions,

00:10:48.240 --> 00:10:48.680
perhaps do not put them on BBB,

00:10:50.460 --> 00:10:50.600
put them in the pad. It's a little easier for

00:10:52.380 --> 00:10:52.880
us to archive them afterwards.

00:10:56.160 --> 00:10:56.580
I'm going to give a little bit of time.

00:10:58.360 --> 00:10:58.860
I feel bad about going on break when I have

00:11:00.940 --> 00:11:01.160
you available and ready to answer more

00:11:02.680 --> 00:11:03.180
questions. Oh, you're too kind.

00:11:07.360 --> 00:11:07.860
[Speaker 2]: How have you, as this changed,

00:11:09.520 --> 00:11:09.960
how's your visualization of the books,

00:11:11.260 --> 00:11:11.760
or of your games at all?

00:11:15.180 --> 00:11:15.680
[Speaker 1]: Sorry, can you ask that 1 more time?

00:11:16.700 --> 00:11:17.200
I didn't catch the first part.

00:11:20.140 --> 00:11:20.600
[Speaker 2]: How has this impacted,

00:11:23.080 --> 00:11:23.300
like, your imagination on the scenes and

00:11:28.240 --> 00:11:28.360
stuff like that because it's partly open and

00:11:30.720 --> 00:11:30.920
closed because you had that chart where you

00:11:32.880 --> 00:11:33.380
had that where you put it in the center of

00:11:37.240 --> 00:11:37.400
constrained by algorithms to enhance your

00:11:39.780 --> 00:11:40.020
creativity, you write it but it's not all

00:11:42.700 --> 00:11:42.900
freeform to where you have writer's block as

00:11:42.900 --> 00:11:43.400
much.

00:11:46.800 --> 00:11:47.080
[Speaker 1]: You hit the, You hit it on the head.

00:11:49.640 --> 00:11:50.040
That's exactly it. That's why I've been doing

00:11:53.940 --> 00:11:54.440
this. Creativity is a hard thing to foster.

00:11:57.520 --> 00:11:57.700
And having little prompts that you have to

00:11:58.340 --> 00:11:58.840
kind of work together,

00:12:03.660 --> 00:12:04.160
like twisty language, what does that mean?

00:12:06.560 --> 00:12:06.900
Oh, you have to kind of work with that.

00:12:08.800 --> 00:12:09.160
So yeah, that's 1 of the reasons why I got

00:12:11.800 --> 00:12:12.300
into doing the solo version of it,

00:12:14.120 --> 00:12:14.600
just because you kind of,

00:12:15.980 --> 00:12:16.480
it does really foster the creativity.

00:12:23.540 --> 00:12:24.040
Did that answer the question?

00:12:28.520 --> 00:12:28.780
[Speaker 2]: Yeah well has it kind of has it improved over

00:12:30.060 --> 00:12:30.280
time though of using it like

00:12:33.200 --> 00:12:33.700
[Speaker 1]: oh yeah oh yeah I would definitely say so

00:12:36.420 --> 00:12:36.920
While I'm still not ready to publish my files

00:12:40.240 --> 00:12:40.740
at all, but the first ones were much worse.

00:12:46.160 --> 00:12:46.320
[Speaker 2]: That was an example like after you play for

00:12:47.800 --> 00:12:48.080
like 2 months or something like that,

00:12:50.320 --> 00:12:50.440
like, could you close your eyes and see the

00:12:51.420 --> 00:12:51.920
rooms a lot better versus...

00:12:54.720 --> 00:12:55.220
[Speaker 1]: Yeah, I think so. I think so.

00:13:02.150 --> 00:13:02.500
And, you know, there's 1 solo game called A

00:13:03.340 --> 00:13:03.840
Thousand-Year-Old Vampire.

00:13:05.740 --> 00:13:06.100
I don't know if you've seen that 1 or not,

00:13:08.440 --> 00:13:08.940
but it's quite creative.

00:13:09.720 --> 00:13:10.220
It's very interesting.

00:13:13.180 --> 00:13:13.680
It's got a great setup to use.

00:13:17.200 --> 00:13:17.320
And When I was looking through it,

00:13:19.320 --> 00:13:19.820
it's like, I'm thinking of a typical vampire

00:13:20.720 --> 00:13:21.220
and this sort of thing.

00:13:25.760 --> 00:13:26.040
But then there's this YouTuber named Seth

00:13:27.880 --> 00:13:28.180
Skalkarski, if I can pronounce his name

00:13:30.020 --> 00:13:30.060
right. He was describing it.

00:13:32.040 --> 00:13:32.540
And he came up with a completely different

00:13:34.540 --> 00:13:34.940
vampire scene. And it's like,

00:13:37.560 --> 00:13:37.880
oh, I could see how people can kind of start

00:13:40.600 --> 00:13:41.000
working on these things and really see things

00:13:43.080 --> 00:13:43.260
differently. And the creativity and all that

00:13:44.340 --> 00:13:44.840
sort of stuff just really blossoms.

00:13:48.040 --> 00:13:48.540
[Speaker 2]: And then I guess as an extension of that,

00:13:53.680 --> 00:13:53.920
how has the stories changed after using this

00:13:58.140 --> 00:13:58.640
toolkit or the solo games for 2 months?

00:14:00.200 --> 00:14:00.700
Like the scenes, like how you,

00:14:02.440 --> 00:14:02.940
like the stories that you'd start generating?

00:14:05.980 --> 00:14:06.460
[Speaker 1]: Yeah, yeah, yeah. Yeah,

00:14:09.000 --> 00:14:09.200
I mean, a lot depends on just how much you're

00:14:10.140 --> 00:14:10.440
willing to put into it.

00:14:13.980 --> 00:14:14.340
But yeah, I've definitely had a lot of fun.

00:14:16.360 --> 00:14:16.760
And it's just been a lot more enjoyable and

00:14:17.680 --> 00:14:18.180
just more interesting.

00:14:21.960 --> 00:14:22.120
[Speaker 2]: Well I mean like has the types and quality of

00:14:23.940 --> 00:14:24.440
the stories changed a lot?

00:14:25.240 --> 00:14:25.740
Or more than that?

00:14:30.280 --> 00:14:30.620
[Speaker 1]: I think so, you know, but obviously the proof

00:14:34.000 --> 00:14:34.500
is if somebody else is doing the evaluation

00:14:39.060 --> 00:14:39.280
and I'm not letting that out But I think so,

00:14:42.040 --> 00:14:42.500
but I think so so but I think your mileage

00:14:44.340 --> 00:14:44.840
may vary. So yeah, try it out

00:14:47.360 --> 00:14:47.860
[Speaker 2]: Have you seen the game Dwarf Fortress?

00:14:50.880 --> 00:14:51.140
Because it's supposed to be a video game

00:14:53.040 --> 00:14:53.260
that's in a similar spirit to that,

00:14:55.080 --> 00:14:55.580
where it helps you generate stories.

00:14:56.820 --> 00:14:57.320
Dwarf Fortress, RimWorld,

00:15:00.420 --> 00:15:00.920
Kenshi is another 1.

00:15:03.400 --> 00:15:03.720
[Speaker 1]: Yeah, no, I've looked at the Dwarf Fortress,

00:15:04.640 --> 00:15:04.900
but I haven't played it.

00:15:08.160 --> 00:15:08.480
But that 1 seems a little bit more

00:15:10.640 --> 00:15:10.920
structured, but still could be a lot of fun

00:15:13.700 --> 00:15:13.860
too. And then others, it's like,

00:15:15.240 --> 00:15:15.260
how far do you want to take it?

00:15:18.280 --> 00:15:18.780
Like I just picked up this 1 called Broken

00:15:21.820 --> 00:15:21.980
Cask. There it is, where you generate a

00:15:25.240 --> 00:15:25.640
little bar tavern, and then you start rolling

00:15:29.180 --> 00:15:29.540
events. Now, it gives a lot more stuff coming

00:15:30.780 --> 00:15:31.060
out of it. It's like, oh,

00:15:32.700 --> 00:15:32.980
this person's showing up and this is what's

00:15:34.700 --> 00:15:34.840
happening, but you can elaborate on it as

00:15:36.660 --> 00:15:36.880
much as you want. And that's what I'm

00:15:39.600 --> 00:15:39.840
thinking I might do. Hi,

00:15:40.600 --> 00:15:41.100
Mike, you got a question?

00:15:47.680 --> 00:15:48.180
[Speaker 3]: Hi, Howard. Yeah, I do have a question.

00:15:50.940 --> 00:15:51.440
I'm a big fan of your work on literate DevOps

00:15:53.120 --> 00:15:53.620
and your essay and video on that topic.

00:15:56.040 --> 00:15:56.260
I'm just wondering if you still use that

00:15:59.640 --> 00:15:59.820
workflow at work and have you changed how

00:16:02.160 --> 00:16:02.420
that process works or has it evolved over

00:16:04.720 --> 00:16:05.220
time since that video and essay were written?

00:16:06.840 --> 00:16:07.340
[Speaker 1]: That's a good question.

00:16:12.440 --> 00:16:12.600
Yes, I still do it. It varies depending on

00:16:13.500 --> 00:16:14.000
the project and whatnot.

00:16:16.400 --> 00:16:16.900
But I still am using it.

00:16:20.280 --> 00:16:20.520
Yeah, yeah. In fact, I'm doing it with a lot

00:16:22.760 --> 00:16:23.260
of other things. Like all my configuration

00:16:27.660 --> 00:16:28.160
files are all in a literate style for Emacs.

00:16:31.160 --> 00:16:31.660
And even all the code that's in Ironsworn,

00:16:35.060 --> 00:16:35.560
the repo, if you go to the repo,

00:16:37.440 --> 00:16:37.640
it's the readme file. And yeah,

00:16:39.720 --> 00:16:40.140
that's just being rendered out to the Emacs

00:16:41.660 --> 00:16:42.160
file. So it is still all literate.

00:16:43.440 --> 00:16:43.940
[Speaker 3]: Very cool.

00:16:46.500 --> 00:16:46.780
[Speaker 1]: Yeah, because I don't know.

00:16:48.120 --> 00:16:48.620
Some things are just a little too complicated

00:16:49.320 --> 00:16:49.820
to just type up.

00:16:56.040 --> 00:16:56.200
[Speaker 0]: All right, sorry to be the bearer of bad

00:16:58.220 --> 00:16:58.720
news, but we have only about 3 more minutes

00:16:59.840 --> 00:17:00.060
of lifetime. By the way,

00:17:02.920 --> 00:17:03.120
feel free to stay and discuss any of the

00:17:07.540 --> 00:17:08.040
topic of today's session after we go off air

00:17:10.579 --> 00:17:10.859
and we'll be able to keep all of the nice

00:17:12.260 --> 00:17:12.540
discussion and put them on the talks page

00:17:16.560 --> 00:17:17.060
afterwards. Great. Howard,

00:17:20.020 --> 00:17:20.280
I would like to ask you if you have any last

00:17:21.760 --> 00:17:21.900
words regarding the presentation or the

00:17:23.040 --> 00:17:23.540
questions you've had. Well,

00:17:24.520 --> 00:17:25.020
the last question we had,

00:17:27.500 --> 00:17:27.720
actually, we had Mike come and ask it live.

00:17:29.440 --> 00:17:29.720
But do you have any parting words before we

00:17:31.720 --> 00:17:32.220
leave you? Okay.

00:17:37.560 --> 00:17:38.000
[Speaker 1]: I think the last thing is go and hack

00:17:41.420 --> 00:17:41.720
something. I mean, this Lisp stuff is a lot

00:17:43.860 --> 00:17:44.360
of fun. And I hope that came across.

00:17:47.240 --> 00:17:47.420
It's like, the project I made is just a

00:17:50.220 --> 00:17:50.720
personal thing and it was fun for me to make,

00:17:53.100 --> 00:17:53.400
but everybody's probably got some fun thing

00:17:54.320 --> 00:17:54.820
they could make as well.

00:17:56.200 --> 00:17:56.700
And just, I don't know,

00:17:58.460 --> 00:17:58.960
hack it yourself because all the,

00:18:01.920 --> 00:18:02.420
you know, think about adding multi-threading

00:18:04.480 --> 00:18:04.740
to Emacs. Maybe we don't want that,

00:18:06.000 --> 00:18:06.360
because that'll just complicate things.

00:18:08.200 --> 00:18:08.700
This is your own personal hacking sandbox,

00:18:09.520 --> 00:18:10.020
so go have fun.

00:18:14.220 --> 00:18:14.380
[Speaker 0]: Great. I was just going to say we were

00:18:15.060 --> 00:18:15.560
talking about Dwarf Fortress.

00:18:18.680 --> 00:18:19.180
In Dwarf Fortress, it's a very CPU intensive

00:18:21.020 --> 00:18:21.240
game because it needs to compute every single

00:18:23.480 --> 00:18:23.860
thing in the world and there's such a thing

00:18:27.700 --> 00:18:27.780
as the CPU death of the world where basically

00:18:29.340 --> 00:18:29.500
you've got too many cats that are just

00:18:31.320 --> 00:18:31.440
breeding constantly with 1 another and it

00:18:33.760 --> 00:18:34.000
creates so many entities that it just

00:18:36.760 --> 00:18:36.940
crashes, and the time it takes for the day to

00:18:38.440 --> 00:18:38.940
finish it, it just never finish.

00:18:40.680 --> 00:18:41.180
So I was going to say maybe multi-threading

00:18:43.180 --> 00:18:43.660
might be useful in this case for Emacs.

00:18:46.100 --> 00:18:46.600
So, wanting to foray into the future.

00:18:48.800 --> 00:18:49.300
[Speaker 1]: All right. Thank you.

00:18:50.900 --> 00:18:51.180
[Speaker 0]: And thank you so much,

00:18:52.360 --> 00:18:52.540
Howard, and thank you Plasma Strike for your

00:18:53.320 --> 00:18:53.560
question, as well as Mike,

00:18:55.760 --> 00:18:55.900
who joined us. We're going to go live with

00:18:57.440 --> 00:18:57.940
the next talk in about 1 minute,

00:19:00.400 --> 00:19:00.580
and until then, well, I'm not going to put

00:19:02.040 --> 00:19:02.400
music, You can wait 50 seconds without music,

00:19:03.960 --> 00:19:04.460
you Zoomers. We'll be back in a bit.

00:19:05.280 --> 00:19:05.780
[Speaker 2]: Bye-bye.

00:19:09.620 --> 00:19:09.860
[Speaker 0]: Bye, Howard. All right,

00:19:11.120 --> 00:19:11.280
we are off. Thank you so much,

00:19:11.980 --> 00:19:12.480
Howard. I need to dash.

00:19:13.940 --> 00:19:14.440
And oh, I think he's already gone.

00:19:16.360 --> 00:19:16.860
So Bye everyone, I'll see you later.