Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
- 85
- 3
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule
Jump in the discussion.
No email address required.
Notes -
Yeah there's all sorts of absolutely fascinating decisions to make. I agree that memory is the biggest hurdle and in general it seems that the more that can be handled by regular code, the better. Ideally there are multiple layers of GPT interpretation of whatever information is presented to it. Maybe you have a context layer and a location layer, and one GPT plugin summarizes them for the next plugin, which combines the summary with the player's chosen action to determine what happens next.
I like the location idea but it does have some drawbacks--namely if a branch has an explosion or something that modifies a location, the Location system will guarantee that that explosion didn't happen. Perhaps you could have a location system and then a separate plugin with branch-specific modifications to that Location. Same with characters, quests, etc. I think you definitely would need this Location system to be interpreted by GPT though, because any other solution would necessitate a grid system or something along those lines which I think would stifle creativity a bit. You'd also want the system to be able to locate landmarks and mention them when they're within sight, which would be quite difficult to implement, but very worthwhile.
To be honest I have a busy job and only have a month to build it, so I will be happy if what comes out at the end works at all haha. Once this grind is over it will be fun to put a lot more time into optimizing everything though. This is the sort of thing that could just be improved upon forever. My understanding is that in certain respects (such as the context window) AI should be subject to Moore's Law so in a few years maybe we have enormous 200k context windows and all of this becomes very easy.
I'll follow up with more details when I have them written down, but tbh Gwern's writeup suffices for me for now.
The whole crypto aspect is mostly just to get funding, right now (crypto hackathons seem to have much less competition), at the VC stage (same), and if/when it actually becomes a real company. The basic idea is that you can buy an NFT of a branch in the story, and then you "own" that branch and earn royalties whenever anyone buys a branch downstream from yours. I am not much of a crypto person (despite working in the field) but I think people would genuinely enjoy owning stories on the blockchain. My hope is that it further incentivizes people to search for high-quality branches--they get paid if they choose the best branch after all. Then all the NFT purchases would go towards subsidizing the experience for your regular consumer who just wants to read a cool crowdsourced CYOA book.
Yeah, I agree with everything you wrote here (Although I already mentioned the branch specific modification to locations in my original comment). The crypto stuff actually seems a lot harder to implement than the rest of the program, imo. I might actually try to develop a location/character database/lookup in my ample free time myself, run it all locally on some 7b model. Will share the code on GitHub if I manage. Some interesting prompt engineering challenges there, I think.
Good luck on grabbing some of that crypto money!
Oops, must have missed your comment about branch-specific modification. I'd certainly be interested in seeing what you come up with. Part of the reason I'm excited to build this is because if it works at all then I will enjoy it, even if it never goes anywhere.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link