krystophny/slopask

slopask

Anonymous Q&A tool for university lectures, deployed at ask.sloppy.at. SQLite + go-chi HTTP server with embedded static UI. No tracking: no cookies, no IP logging, no analytics.

Use this skill when the user mentions running a Q&A room for a lecture, listing rooms, or working with the slopask admin/student URLs.

Repo: ~/code/sloppy/slopask. Binary: slopask.

Commands

make build

slopask serve --bind 127.0.0.1 --port 8430 --data-dir ./data --uploads-dir ./uploads
slopask create-room --title "WSD SS2026"
slopask list-rooms

URL shape

| Audience | URL | |---|---| | Students | /r/{slug} (12-char lowercase alphanumeric) | | Admin | /admin/{admin_token} (24-char mixed-case alphanumeric) | | External API | /api/v0/rooms/{admin_token}/... (used by slopcast) |

Voter identity is a client-side localStorage UUID — not a server cookie.

Architecture pointers

• cmd/slopask/main.go — CLI entry (serve, create-room, list-rooms).
• internal/store/ — SQLite (modernc.org/sqlite, pure Go).
• internal/server/ — chi router, SSE broker, file uploads, embedded static under internal/server/static/.

Notes

• For programmatic question pulls or stats from another tool, use the /api/v0/rooms/{admin_token}/... REST surface with curl. Don't bypass the admin token.
• Admin and student URLs are sensitive — admin_token grants full room control. Treat the admin URL like a credential; don't paste it into shared chat or commit it.