1. 15

I think we lost it when we did the migration over to the new server, but I really liked the old BBS style lobste.rs. Is there any way we could set that back up, or has the code been lost to the wind?

  1.  

  2. 11

    Its code was never in the main Lobsters repo. If you’re curious about it, the only thing to do is mail jcs.

    1. 8

      The BBS that I built for it was not open source, but did interact with much of the website components with telnet, SSH, and Javascript/WebSockets interfaces. (source)

      Quite a few people asked me how the whole system worked, and since I am not currently planning on releasing the source code (as it was largely a creative effort) (blog post)

      1. 1

        (as it was largely a creative effort)

        i know this is heresy to some of you, but if jcs is still attached to this code, maybe some copyleft license would be appropriate for it?

        1. 2

          Or maybe we could just collectively pay for it?

      2. 4

        I think an API would be nice for custom clients, esp without web browser included. The one HN has led to lots of interesting clients and analysis. Then, Lobsters could build anything from a customized UI to a BBS to partition on Muen/seL4. Anyone wanting a specific setup can just build it themselves without bothering admins.

        What yall think?

        1. 2

          There’s .json mappings for many existing routes (and XML, for RSS) - it’s just there’s no writeable API. jcs was considering working on OAuth to start with, but lost interest when the author of a mobile app who requested it didn’t respond?

        2. 2

          The code to run that was not transferred by /u/jcs when /u/pushcx took over. Its remnants in the codebase were also removed recently, so any new BBS would need some new scaffolding.

          1. 1

            It was cute, but I suppose no one really used it enough to justify the maintenance.

            1. 1

              I enjoyed it too, but I don’t know Javascript and my understanding of RAILS is tenuous at best (So let me understand this - there’s a controller and then Big Magic happens and HTML gets rendered? :) - so I can’t actually put any sweat equity in to bring it back.

              1. 2

                “but I don’t know Javascript and my understanding of RAILS is tenuous at best (So let me understand this - there’s a controller and then Big Magic happens and HTML gets rendered? :) “

                Aside from saving @pushcx and company time, that’s exactly why I thought an API would be a good idea. Anything I did to improve or experiment on UI requires learning the Lobsters stack. Whereas, an API might not. There might be preexisting libraries for a lot of that, too.