| Time |
Nickname |
Message |
|
03:17
🔗
|
pilgrim |
it would be nice if each project's dashboard showed the rate limit and the current rate, so people who have the ability launch multiple VMs would know whether doing so would be constructive |
|
03:18
🔗
|
pilgrim |
ability *to launch |
|
13:06
🔗
|
GLaDOS |
01[13seesaw-kit01] 15alard pushed 1 new commit to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/commit/1a7b54e81ef15939d6a4d339b329a5fcb5a7bf3b |
|
13:06
🔗
|
GLaDOS |
13seesaw-kit/06development 141a7b54e 15Alard: Add an explanation to the rate limiting message. |
|
15:45
🔗
|
Smiley |
why can't I ssh into my warrior o_O |
|
15:46
🔗
|
alard |
Because you haven't installed an ssh server? |
|
15:47
🔗
|
Smiley |
oh i thought it had one by default :P |
|
15:51
🔗
|
Smiley |
hmmm i guess it's hitting swap hard, I can't even login via terminal |
|
16:14
🔗
|
Smiley |
ouch all the memories :< |
|
16:25
🔗
|
Smiley |
k i'm gonna have to kuill this warrior and give it more ram |
|
16:44
🔗
|
GLaDOS |
01[13seesaw-kit01] 15alard pushed 2 new commits to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/compare/1a7b54e81ef1...ef88516ae4e4 |
|
16:44
🔗
|
GLaDOS |
13seesaw-kit/06development 1455ad687 15Alard: Reload web interface if warrior restarts.... |
|
16:44
🔗
|
GLaDOS |
13seesaw-kit/06development 14ef88516 15Alard: Try to ignore duplicate connections.... |
|
17:57
🔗
|
GLaDOS |
01[13seesaw-kit01] 15alard pushed 1 new commit to 06development: 02 https://github.com/ArchiveTeam/seesaw-kit/commit/b813b135f47ca5fca532bf30d6838a03d22fe510 |
|
17:57
🔗
|
GLaDOS |
13seesaw-kit/06development 14b813b13 15Alard: Remember collapse status when showing new items. |
|
20:01
🔗
|
Smiley |
[17:59:04] <@GLaDOS> seesaw-kit/development b813b13 Alard: Remember collapse status when showing new items. |
|
20:01
🔗
|
Smiley |
\o/ |
|
22:34
🔗
|
Mindless |
is www.happypenguin.org a candidate for archival? |
|
22:34
🔗
|
omf_ |
Mindless, It is already done |
|
22:37
🔗
|
Mindless |
oh, good |
|
23:15
🔗
|
Smiley |
errr |
|
23:15
🔗
|
Smiley |
new jobs are stil starting expanded for me :< |
|
23:47
🔗
|
alard |
Then you're probably not on the development branch. (And even if you were the seesaw kit is only updated if you reboot your warrior.) |
|
23:48
🔗
|
omf_ |
alard, I got some warc questions. I read the iso spec. Is there a conformance test for warc generation? |
|
23:48
🔗
|
alard |
omf_: No, not that I know of. There are a few warc-reading tools that you can use to see if they work. |
|
23:49
🔗
|
alard |
There's just been a message on the Wget mailing list with a warc-related problem that caused problems for IA's warc reader. |
|
23:52
🔗
|
omf_ |
In terms of warc support these are the apps I know of wget, warcproxy, warcindex and heritrix |
|
23:52
🔗
|
omf_ |
I dug around on github some already |
|
23:55
🔗
|
alard |
There is (or there was, I see) https://github.com/internetarchive/archive-commons |
|
23:56
🔗
|
alard |
The hanzo warc-tools library does warc parsing in Python. |
|
23:57
🔗
|
alard |
(But that's also the library that warcproxy uses.) |