dreamrealMost of the issues right now are pretty much in-stream, with the design. The grammar parser's the one that's probably the "hardest" - a lot of issues are just "oh, let's fix that" and ten minutes later, we're good.
dreamrealThat karma one (209) is likely to be one of those ten-minute things where five of the ten minutes is running tests.
dreamrealI noticed that the other day and it's definitely a little annoying :D
dreamrealthere're still LOTS of little bugs here and there, but most of them ... well... I noticed that chunk thing at 8:50
dreamrealthe UI's wonkiness is mostly because it's an SPA
Chronosdreamreal: Thank you! I'm okay with the default being 24 hours, or 7 days, or whatever you prefer. I was just hoping for an option for ~30 days.
dreamreal720 hours it is!
dreamrealAnd I really appreciate the feedback - I notice a lot of things, but I certainly have my blind spots
dreamrealChronos: ++
nevetChronos now has karma of 5.
dreamrealyou are, BTW, at the top of the karma board :D
dreamrealthe site should be a little more resistant to updates now than it was, too
dreamreal(if I updated content, the router handled that slightly poorly. yes, the UI kinda sucks.)
Chronos\o/
Chronosdreamreal: ++
nevetdreamreal now has karma of 1.
dreamrealwhat how
dreamrealdamn it
dreamrealgrrrrr
dreamrealthat's *annoying*
dreamrealokay, karma cleaned up
dreamrealall that testing, you know :D
Chronosdreamreal: ++
* Chronos chuckles
dreamrealthe .env was missing my nick :D
dreamrealI overwrote it at some point and didn't realize the version I was working with didn't include me as an "ignored karma target"
dreamrealin javabot there's a special case for me and karma, nevet just says "you can ignore these nicks, as a configuration"
ChronosKarma reminds me of the TV show The Good Place
dreamrealheh. I LOVED that show
dreamrealthe good place++
nevetthe good place now has karma of 1.
ChronosFantastic show.
dreamrealI wish kristen bell would learn how to act, though
dreamrealshe's one of those actors who's fun to watch because SHE is fun to watch, but she really doesn't ACT
nevetA new game of 21 Matches begins! There are 21 matches on the table. Take 1, 2, or 3 matches each turn. Whoever is forced to take the last match loses. Use '21 take <1-3>' to play.
dreamreal21 take 5
nevetError: Please specify a number between 1 and 3. Usage: 21 take <1-3>
dreamreal21 take 3
nevetHow delightfully aggressive. After much deliberation, I take 1. There are 17 matches remaining.
dreamreal21 take 3
nevetI see dreamreal picked 3. I'd expected 2. Without a hint of doubt, I take 1. There are 13 matches remaining.
dreamreal21 take 3
nevetI see what you're doing there. With a knowing smile, I take 1. There are 9 matches remaining.
dreamreal21 take 3
nevetYou surprise me. After pretending to think about it, I take 1. There are 5 matches remaining.
dreamreal21 take 1
nevetExcellent choice! Methodically, I take 3. And so the last match falls to you. A noble effort.
nevetnevet 1.0 | e66b635 (feat-220-ai-content-workflows) | Built 2026-03-09 16:42:29 EDT
dreamrealokay, cool.
dreamrealAnyone here?
dreamrealOkay, so pardon the flood, but I gotta test.
dreamrealI chose 21 matches for an early operation in nevet - the bot that runs as part of bytecode.news - because it's one of the first things I write in anything.
dreamrealIt's a game - so it has "winning and losing conditions," except it's so fundamentally easy to play that it really doesn't.
dreamrealBut it has state (i.e., multiple turns), it has input (how many matches does the player choose), it has output (how many matches does the COMPUTER choose), and thus it hits the entire programming cycle: loops, input, output, exit conditions, without being taxonomically or programmatically complex.
dreamrealIt's like a "hello world" for games; hello world tests compiler input and output, with programmatic output being part of it, but 21 matches is "gamer hello world," with no drama, because there's no way the computer can lose unless it's programmed poorly, and that, too, is a part of it.
dreamrealSo in nevet, 21 matches proved out a way to store state from operations, such that they could see things that have happened before, as well as using the i/o mechanisms other operations had already proven - but those other operations had no state, only call/response mechanisms.
dreamrealarticle Why I Chose 21 Matches in Nevet
nevetIdea session started: "Why I Chose 21 Matches in Nevet". Use 'content <text>' to add body paragraphs, 'includeai' to enable AI summary/tags, 'done' to save, or 'cancel' to discard.
dreamreallogs 6m
nevetAdded 13 log messages (last 6m) as content block #1.
dreamrealincludeai
nevetAI summary enabled for "Why I Chose 21 Matches in Nevet". On 'done', a generated summary and suggested tags will be appended to the draft.
dreamrealcontent I chose 21 matches in nevet deliberately.
nevetContent block #2 added to "Why I Chose 21 Matches in Nevet". Use 'content <text>' to add more, or 'done' to save.
nevetIdea saved as draft: "Why I Chose 21 Matches in Nevet" (2 content blocks). AI summary requested but response was invalid JSON; saved without AI summary.
dreamrealoof!
dreamrealversion
nevetnevet 1.0 | c99835b (feat-220-ai-content-workflows) | Built 2026-03-09 17:07:01 EDT
dreamrealI chose 21 matches for an early operation in nevet - the bot that runs as part of bytecode.news - because it's one of the first things I write in anything.
dreamrealIt's a game - so it has "winning and losing conditions," except it's so fundamentally easy to play that it really doesn't.
dreamrealBut it has state (i.e., multiple turns), it has input (how many matches does the player choose), it has output (how many matches does the COMPUTER choose), and thus it hits the entire programming cycle: loops, input, output, exit conditions, without being taxonomically or programmatically complex.
dreamrealIt's like a "hello world" for games; hello world tests compiler input and output, with programmatic output being part of it, but 21 matches is "gamer hello world," with no drama, because there's no way the computer can lose unless it's programmed poorly, and that, too, is a part of it.
dreamrealSo in nevet, 21 matches proved out a way to store state from operations, such that they could see things that have happened before, as well as using the i/o mechanisms other operations had already proven - but those other operations had no state, only call/response mechanisms.
dreamrealarticle Why I Chose 21 Matches in Nevet, Really
nevetIdea session started: "Why I Chose 21 Matches in Nevet, Really". Use 'content <text>' to add body paragraphs, 'includeai' to enable AI summary/tags, 'done' to save, or 'cancel' to discard.
dreamreallogs 2m
nevetAdded 12 log messages (last 2m) as content block #1.
dreamrealincludeai
nevetAI summary enabled for "Why I Chose 21 Matches in Nevet, Really". On 'done', a generated summary and suggested tags will be appended to the draft.
dreamrealcontent I chose 21 matches in nevet deliberately.
nevetContent block #2 added to "Why I Chose 21 Matches in Nevet, Really". Use 'content <text>' to add more, or 'done' to save.
dreamrealdone
nevetIdea saved as draft: "Why I Chose 21 Matches in Nevet, Really" (2 content blocks). AI summary appended for admin review.