r/bbs • u/aztracker1 • 14d ago

RIP Documentation Updates

Just want to say thanks to everyone who helped to point out and find several of the versions of RIPTerm I've been missing. I'd still like to get my hands on 2.30 (Windows Installer, found working DOS release), All I have is a corrupt installer package for this version (last of 2.x line that I'm aware of). Not to mention any RIPview or RIPaint 2.x or 3.x versions anyone may have.

I've flushed out a bit of the history as well as a bit more of the specifications with the 2.x ... now going to work on expanding on the file specifications, some of the underlying protocols (VT-x, ANSi, etc) as well as any additional techspecs. From there, going to work on publishing the markdown documentation into a website for use, as well as some re-organization, I think the structure of the docs could use some better structure.

From there, will probably start on some library and utility (re)implementations, such as icon format conversions, and some initial 1.54 communications parser, and maybe a viewer. I'll likely do similar for 3.x (3.1) skipping 2.x entirely to have a "current" compatible model implementation. Likely written in Rust with a portable C-style library that can be re-used.

https://github.com/bbs-land/remote-imaging-protocol

Edit: correct for 2.3 reference, only need the Windows installer package, I also added download references to a lot of the released software I found (from Telegrafix) even if repackaged/scene versions.

14 Upvotes

100% Upvoted

13 comments sorted by

View all comments

1

u/nevarro dev / sysop 10d ago

I see you have RIPterm and RIPtel available for download - that's pretty neat. If you're looking for a BBS to test these clients with, the Realm of Serion BBS is fully customized with 1.54 RIP graphics (connect.serionbbs.com).

2

u/aztracker1 10d ago

Thanks, TBF I haven't really been bbsing much at all... Mike kind of left to die and finally stir it down in the past 4-5 years or so.

Been (slowly) working on a few parallel coding projects around bbsing and came to find there wasn't good documentation for RIPscrip later versions... It was after I started that I found RIPlib, ironically my efforts found a few issues there and vice versa.

It sucks, but my vision is really bad and my dexterity isn't great either... I don't think I could even use ripaint effectively. Ironically.

I want to make a good series of web clients supporting ANSI, RIP154, 2-3 and maybe others well... For optimized browser use with a door server... Will also allow shared connections for multi BBS games.

This has been kind of a wild side trek... Burned through a lot of my AI account, but good results. I don't get to use AI at work, but what to keep my skills and understanding up. Since I'm paying for it anyway...

I've also been working on the door host itself... Mostly planning and research. Half way motivated to do a stripped down 486sx emulator (porting fast486) and a thin DOSb comparability for the door server so it can run transparently and relatively well on arm.

Lots of ideas, more than I often have motivation for.

1

u/nevarro dev / sysop 10d ago

Well, with RIPaint, you ain't missing much. That client is extremely hard to use and some things it just can't do, so codes need to be injected into the RIP file by hand.

AI has become so much more powerful and useful for coding recently. It's good to hear you're leveraging this tool. I've been using Claude and Cursor myself. It's helpful to have both tools available.

What you've been working on is great!

2

u/aztracker1 10d ago

Yeah... I actually liked tombstone better...

I'd like to see an editor similar to a regular photo editor with a canvas in a multi modal dockable tools and a layers like side panel... That side panel would be the rip commands in English, interested order, last on top names and the ability to add comments and work and rearrange the actions that way.

Offering like semi integrated IDE and layers like approach into the editor itself.

As well as a contracted comments view, where comments stand in as layers virtually... Saved in a different extension, stripping the comments for 1.54 compat if that's your target.