I've never been thrilled about having a forum section, which is completely broken after Easter Monday 2023. The goal from the beginning has been to embed conversations in the actual data, similar to Wikipedia talk pages.
This depends heavily on having a unique contentId to query (UUID v7), since the implementation will likely use the Discourse API to automatically generate a thread based on a unique identifier. For example, to load a "forum thread" for a torrent group, query the API for the thread whose title is 0187921f-53fd-7358-920a-4f45aa2c9d6d.
Each core object in the logical schema (torrent groups, collections, requests, and creators) would have its own thread, which can easily be expanded to include, e.g., comments under news articles or user "talk" pages.
This would also greatly simply the various user comment and notification pages, collapsing them all into a single table of threads that could be searched, sorted, and filtered.
I've never been thrilled about having a forum section, which is completely broken after Easter Monday 2023. The goal from the beginning has been to embed conversations in the actual data, similar to Wikipedia talk pages.
This depends heavily on having a unique contentId to query (UUID v7), since the implementation will likely use the Discourse API to automatically generate a thread based on a unique identifier. For example, to load a "forum thread" for a torrent group, query the API for the thread whose title is
0187921f-53fd-7358-920a-4f45aa2c9d6d.Each core object in the logical schema (torrent groups, collections, requests, and creators) would have its own thread, which can easily be expanded to include, e.g., comments under news articles or user "talk" pages.
This would also greatly simply the various user comment and notification pages, collapsing them all into a single table of threads that could be searched, sorted, and filtered.