pjc09h
commented
11 months ago The solution is to embed gzuidhof/starboard-notebook instances on the wiki, with a threaded conversations similar to Kaggle. Also, using these threaded conversations on all major pages (torrent groups, collages, requests, and user profiles). The user profile conversations must be able to be disabled in the user settings.
The forums, comments, and wiki system is generally an intractable problem that must be rewritten in some form. I'd previously discussed outsourcing most of that stuff to a Discourse backend and have drafted up a system to store this data. Looking at Kaggle for inspiration, I wonder if it's better to not worry about where it's stored and instead focus on allowing executable code in user-generated text content. This open up security questions about how to isolate the execution environment (probably a separate API on a different host) but it aligns with the goal of creating a data repository that documents itself, studies itself, and generates its own data based on user input.