Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Remove ineffectual assignment & log error | Andinus | 2020-04-05 | 1 | -0/+10 |
| | |||||
* | bpod: Re-enable cache & fix issues with v0.6.2 | Andinus | 2020-04-02 | 1 | -1/+21 |
| | |||||
* | Drop response caching on bpod | Andinus | 2020-03-26 | 1 | -83/+7 |
| | | | | | | | | | | | | | | Caching on bpod was full of assumptions and very hacky, this commits removes it all. Images are still cached and we prepend the date to their file name so that it becomes easier to work with them later. Also they are seperated by a colon so it's easy to remove the date too with a script or something. BPOD is not even an official api and it can get closed anyday, bing uses this to get bpod on bing.com and we are just using it. They still have pretty pictures though and so I'll still keep it. If users want to get all information then they can just use -dump flag and save it to a file. | ||||
* | Unmarshal after dump | Andinus | 2020-03-26 | 1 | -8/+5 |
| | | | | | dump no longer exits the program, this doesn't make any different. We are still doing the same thing. | ||||
* | Fix dump logic | Andinus | 2020-03-26 | 1 | -1/+1 |
| | |||||
* | Disable caching on random (bpod) | Andinus | 2020-03-25 | 1 | -67/+11 |
| | |||||
* | Disable cache when random is not passed (bpod) | Andinus | 2020-03-25 | 1 | -8/+19 |
| | |||||
* | Enable random flag and fix issue with body and res not in sync (bpod) | Andinus | 2020-03-25 | 1 | -21/+31 |
| | |||||
* | Disable random flag on bpod & warn in readme | Andinus | 2020-03-25 | 1 | -3/+17 |
| | |||||
* | Describe bug in program | Andinus | 2020-03-25 | 1 | -0/+7 |
| | |||||
* | Add bpod support | Andinus | 2020-03-25 | 1 | -0/+203 |
| | |||||
* | Reinitialize project and change module url | Andinus | 2020-03-24 | 1 | -148/+0 |
| | |||||
* | Add notify functionality to cetus | Andinus | 2020-03-23 | 1 | -0/+13 |
| | |||||
* | Put the functions into seperate files & fix compile time error | Andinus | 2020-03-19 | 1 | -0/+135 |
Splitting the program into seperate programs will cause the binary size to double if the end user wants both services. Instead splitting the functions in seperate files will keep the binary size small for both services combined & also the program will be maintainable. |