Do it [SchemeBBS]

Can we fucking wake up here sheeple? We need a SchemeBBS. We need to restore all of prog.db in it. This regex crap the admin does is no good right now for the job.

,______ ___ ___ ____.,
/* ' ' ' \_
| \
- ~ ~lmbd
| \
- |
/ \
- ________________________ \
. _ _/ \_ \ __.,._
. \.., / \,. *__/ \
'* / *
/ | /
\_ ,._.#####.__. .___#####._,. /- -.-
*,==| <._# )> vvvv <. # )> |==#" \
/ | | | | \ *
^_ | .,-* / \ | / /
/_ /\__________/ \_________/ - |
/ (__ __ ) | / \__,
| ** \ / " /.
" / \ \_- / /
\ / / v |
- | /
\ ,-''"''--"''"'-.. / \
\ \.,.-,.,.--,.../ |
\_ |
\_ _____ /.
.-/ <>>>____,.,..,____/ ___ / \
,./ \ .
,.*/ \ |\
* * \ /\
,.___/ | \ / |

\
| -- G. J. Sussman

>>1
Scheme is not webscale. The recommended LISP to use for Web Apps is JavaScript nowadays.

lol...

U MENA HASKAL BBS?

That sounds great OP, how much have you written so far?

>>3
What is gaylisp

>>3

implying such a BBS will ever see large traffic.

Write a minimal BBS in C using and CGI.

Challenge: write a ``Minimal BBS'' program in Lambda Calculus.

>>7
Whom are you quoting?

Let's discuss BBS design for a bit here. Having plain text threads that posts get appended to is simply god-awful. Why not have each individual post get its own file?

>>11
Why is it god-awful and why would individual files be better?

I think we all can agree that web is shiet, but a convenient shiet at times. Therefore http should be only one of many interfaces. CL-BBS (/clēbs/) should be actually a NNTP server. NNTP is a simple decentralized protocol that was designed for this kind of things.

>>11
Isn't that how Shiichan does it?

>>12
Because we are constrained by the HTML/JS/CSS/BBCode, the layout of the website, et cetera. Consider this:

Progrider should serve only the raw content of the posts, on demand of the client, which may or may not be a web browser. I am talking about a programmable programming BBS (that makes sense for us, doesn't it?).

It's very troublesome to change the order the threads are shown, for example. Maybe someone wants to view threads per creation date instead of last post. It's also stupid that you have to scroll 100 screens in order to find the 5 latest posts that have been made to this website.

That's why I believe individual posts would be better. It would also get rid us of the "whom are you quoting" dude. Imagine, if >>4 meant literally a single post ID. Threads would literally be connected graphs.

What if someone wants to write an OpenGL client where you are a little spaceship travelling in space, and posts would be stars? Of course this is obviously not handy to use, but it is sure an impressive visualizaton of the bbs. Maybe someone wanted to write an emacs script so that he/she can read progrider from inside emacs. As it is, it's god-awful to do this. What if we want to get rid of BBCode? That's easy too. All you have to do is write a client where you parse & visualize posts differently.

Of course it all rests on the fact each post is a different file, which means you need some protocol for rapid GETs (i.e. to view a thread of 1000 posts would mean to download 1000 files). I'm not an expert but I guess nginx is not made for this.

Seriously, don't we need something more programmable than this old piece of shit?

>>15
I agree that raw data should be served somewhere so we don't have to use a crappy web interface. Ideally, you could query new posts since $DATE, so you could maintain a local copy and display it however you wish, /prog/ isn't that big after all.

The rest is complete nonsense and unrelated to whether posts are files or not. You are proposing some unholy hybrid abomination between Reddit and a mailing list.

It would also get rid us of the "whom are you quoting" dude.

Kill yourself.

>>16
Whom are you quoting?

>>15
lets code this in racket? we could meet on the progrider irc?

>>18
I'm game

Why not just make an API? It can be in JSON format or something similar which can then be parsed in your programming language of choice. After that, you can interpret or do whatever else you want with it. Also, the "who are you quoting" meme needs to die.

#### SchemeBBS: protocol version 1

## Introduction: The SchemeBBS server works as a regular TCP server. It is communicated to and responds with s-expressions.

## Errors
If a query fails the server well return (error <e>) where the form e contains some information about the problem.

## Posts: Posts are assoc lists of the following form:

((id . <int>)
(date . <date>)
(reply . <int or #f>)
(post . <string>))

all these fields must be present except reply, which is optional.
clients should ignore extra unknown fields.

## Commands:

(version) ;=> 1

(get <int>) ;=> returns the post of that id or (error "No such post") if there is no post of that id.

(post <assoc-list>) ;=> the assoc list should be a post without the date, if a client sends date it will be ignored. The server should return the post id on success.

(posts> <int>) ;=> return a list of all posts whose id is larger in ascending order of post id.

>>20
And making a script that interacts with said API would be the rite of passage for every potential /prog/lodite? _{^{Great! I've always wanted this place to be filled with appers and web devs!}}

>>22

/prog/lodyte

high-five

Here's a really trivial client repl type thing which might be useful for testing a server

#lang racket
(require racket/tcp)

(let-values (((in out) (tcp-connect "localhost" 7777)))
(let loop ()
(let ((command (read)))
(displayln command out)
(flush-output out)
(let ((form (read in)))
(displayln form)
(loop)))))

>>21
what should happen if someone replies to a post that doesn't exist (yet)?

>>25
Nothing. GETing that post would make the server respond with an error. Clients don't need to GET such posts since they can know the last post id.

#lang racket

(define (go)
'yep-it-works)

(define (error e)
e) ;; for now

(define (version)
1)

(define post-count 0)

(define (index)
post-count)

(define post-list null)

(define (get id)
(memf (lambda (post) (assoc post 'id))
post-list))

; ((id . <int>)
; (date . <date>)
; (reply . <int or #f>)
; (post . <string>))

;; make-post creates the server post from the client post
(define (make-post post)
(list
(cons 'id (index))
(cons 'date (current-seconds))
;; no (reply . <int>) yet
(assoc 'post post)))

;; post takes the server post and simply appends it to post-list
;; also incrementing post-count
(define (post alist)
(begin
(set! post-list
(cons (make-post alist)
post-list))
(set! post-count (+ 1 post-count))))


>>27
get fixed
(define (get id)
(car
(memf (lambda (post) (= id (cdr (assoc 'id post))))
post-list)))

>>27-28

define
define
define

Just use def, ya faggots.

>>29
but we are defining things, not deffing things

the easiest way to do this is to write a fastcgi wrapper around some embeddable scheme you're complicating things, just use SIG alert and fork to timeout and limit resources

>>31
Whom are you quoting?

>>13

CL-BBS (/clēbs/)

Do you also pronounce NNTP "neenootup"? Moron.

>>15

It would also get rid us of the "whom are you quoting" dude

There's a better solution: you could stop being an meme-spewing imageboarder. Hard to believe there was another solution, I know.

Here's some server code: http://pastie.org/10208782

now we just need a little interpreter to connect between this and >>27

Heres a rough explanation

a client connects to the server
then it just sends s-expression in plaintext (e.g. (version) to find server version, (post "blah blah") t opost a message)
and the server replies in plaintext
its essentialy a remote REPL, where your limited to very basic text board functions (listing posts, posting etc.) not general computation

>>36
no, your limited

>>37
what about my limited?

> (display '(ayy "goo tee"))
(ayy goo tee)
> (print '(ayy "goo tee"))
'(ayy "goo tee")
> (write '(ayy "goo tee"))
(ayy "goo tee")

lesson learned: we need to use WRITE.

client fixed up. Server should appear on the fossil repo soon.

I put everyone's code and the specification together with a few simple changes and made a working prototype. It's in the progrider fossil repo at https://progrider.org/fossil/tree?ci=tip&name=schemebbs .