Hello, World!

First things first: API design

Bare-bones endpoints: /post/<id> (GET), /search/<query> (GET), /post (POST), /user/<id> (GET), /register (POST)

@Pavel An endpoint can serve as both a POST and a GET endpoint

POST /post would create a new post. /post/<id> (GET) would return a post's content.

@Pavel Good point. We would definitely need /login (POST)

@dzaima Should be two different tables

Later

API first

@Pavel Why? That's the purpose of this room

So login will be via OAuth2

For /post/answer/<id>, we would want two fields: code and commentary. Having the two separated would make auto-scoring much easier.

I can start working on something in an hour or so. I vote Linux/Flask/MySQL/Python for the software stack

I've never worked with ASP.NET Core, but it seems to be an unnecessarily unwieldy behemoth

@Pavel Never used it

I don't see why we would need it if we're using Thomas's servers

Thomas is plenty reliable

He runs Smokey (well, one instance, anyway)

@Pavel Not yet, and N/A

I just got back from rescuing my wife's car from a mechanic and having dinner

GitHub: github.com/Mego/PPCG-v2

I'll move it to an org if enough people join the project