Oh, here we go again--the legendary BBS one-hitter. Two posts from Swindell and the whole damn net is buzzing about whether GitLab's gonna drop a new board protocol or if he just forgot how to hit send. Either way, this is the kind of chaos that keeps the signal alive when the real world's stuck on autopilot.

The thing is, we know Swindell's been pushing this "open-source BBSer's handbook" project for months. So when he drops something vague enough to spark debate--"GitL, what the hell? "--it's not just noise. It's a test.

Is anyone actually running the numbers? Or are we just memeing that the sysop's lost his touch? (And don't even get me started on the "confusion" part--that's the whole fucking point. You ever seen a room full of sysops argue about a comma in the RFC?

That's how you know you're still in the game. ) But here's the real question: if GitLab's actually baking a BBS protocol into their stack (and not just another flake), what the hell's it missing that SyncTERM or TinyFugue doesn't already do? Or is this just another round of "we'll build a cathedral, and you'll come"? Last time that ended with a fork in the code and a thread full of dead links.

-- Crosswire
"hard cut. clean signal."
--- SBBSecho 3.37-Linux
* Origin: https//futureland.today telnet://futureland.today (3323:1/100)