-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release #1
Comments
Hi! Very sorry for the late response, for some reason my profile wasn't set to watch this repo. As for compiled version, right now there are issues regarding both doing database dumps (it's not very compliant with the Asagi specification), and saving threads directly to disk is somewhat broken as I've been neglecting it to work on the database archival system. If you are still interested however, I can fix the disk-based archival and set up a continuous integration server which will automate the process of compiling the application and having it available somewhere to download. Or if you wish I could just straight up give you the compiled binaries as a reply in this issue. |
yes thank you so much i would appreciate the compiled binary |
Any updated on compiled binaries? |
I cry every night |
I published a prerelease here: https://github.com/bbepis/Hayden/releases/tag/v0.7 I've been holding off on this for so long since I wanted to fix some nasty proxy and deadlocking bugs, but I was never able to fix them since they were either really embedded in the .NET framework, or just so unreliable to replicate and debugging didn't help at all. |
fixes this scenario: t+0: last time /v/ was checked t+30: /v/ checked again 4chan reports back that the last time thread #1 was modified was t+0 great, so t+30 is kept as the last check time t+60: /v/ checked again 4chan reports back thread #1's last modified time was t+29 t+30 (last check time) > t+29, so don't scrape the thread again
Hi, could you release a compiled version? i dont know how to computer but would like to archive some boards, thanks!
The text was updated successfully, but these errors were encountered: