21 Commits

Author SHA1 Message Date
a3644cce8f changed url to uri 2020-12-07 15:47:44 -05:00
f7dd23bc55 normalizing additions + light reorg 2020-12-06 18:05:17 -05:00
7f293b9dd3 removed comments 2020-12-06 00:16:04 -05:00
0342844a52 partial implemented host banning 2020-12-05 23:59:32 -05:00
a4fa8a48c8 added authentication 2020-12-05 23:47:12 -05:00
003de16e2b checking for crawling boolean 2020-12-03 17:23:52 -05:00
279e2e7441 minor stuff 2020-11-30 19:50:21 -05:00
911c30b409 more stability and retries
changed min_id to since_id due to bug in mastodon
2020-11-28 11:42:31 -05:00
53279ff649 intermediate commit, node type determination, working on time format
lots of crashing
2020-11-25 18:24:56 -05:00
a81c61d5dc removed cruft 2020-11-24 21:19:39 -05:00
97bef269b8 restructuring and cleanup 2020-11-24 21:02:37 -05:00
58d63dea93 added web receiving scaffolding
changed pprof port to 7777
added received_at post column
2020-11-24 00:00:04 -05:00
27cc6a5d9a alternate way to check server + authorization failure checks 2020-11-19 00:38:40 -05:00
4cead30ea5 missed a lock 2020-11-18 12:53:25 -05:00
5807616992 removed some cruft 2020-11-17 22:35:59 -05:00
a54c241970 timing + client updates 2020-11-17 19:57:39 -05:00
ab8e0182bb blood sweat and tears later, memory leak is gone
restructured how the engine works
some communication is through a shared object, perhaps I will revisit
this problem in the future. Until then, this is stable and works...
2020-11-17 18:28:59 -05:00
94334b710b memory issues galore 2020-11-16 00:10:33 -05:00
aab707eab0 trying to fix memory leak... 2020-11-15 00:12:25 -05:00
4c51cd861a basic linting 2020-11-13 20:13:13 -05:00
8a12f277b1 oh yeah, go can do that multiple file thing 2020-11-10 21:53:46 -05:00