😾
Oskar
Yeah, I can put some work in. There are few problems however. We don't know roadmap for subreply so it very well may be that we will be reinventing the wheel along @lucian. It would be great if some parts of it could be open sourced. Anyway, do you have something particular in mind? I am for discussing it openly here, maybe somebody will chip in.
😾
Oskar
dvaun, you collected anything? I am thinking about topic/reply discovery for subreply. This probably should be internal feature, but nevertheless - setting up crawler on _Search_ every N minutes, collect post, categorize as topic/reply, measure activity (no. replies, time, other metadata), present in some minimal-style dashboard (maybe put on github and just run locally to simplify things?). Thinking about it now, every _scrapable_ tab can provide potentially useful metrics.
🤔
David
(RE: subreply.com/ow/hgb) ~ $: I'm not scraping yet--I've been swamped at work. Planning on getting up and running this weekend. As for the crawler scheduling that seems simple enough! I'm happy enough to get a server up and running to host this; I even thought it might be a fun project to experiment with some lower-level server frameworks (the 2 on my mind are actix/rust and drogon/c++). Are you interested in that? And what about publicizing the code?