about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-08-101-0/+2
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* .Kartik K. Agaram2021-08-106-2/+2
|
* slack: parse usersKartik K. Agaram2021-08-101-3/+103
|
* slack: import some test dataKartik K. Agaram2021-08-102-3/+6453
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* new tool: creating a data diskKartik K. Agaram2021-08-102-1/+19
|
* slack: fix abort after loadKartik K. Agaram2021-08-101-1/+8
| | | | I forgot about the null bytes that come from loading sectors.
* slack: takes almost 3 minutes to load 55MBKartik K. Agaram2021-08-101-3/+5
| | | | | | | | | This is with KVM on a pretty fast Thinkpad. If I exclude images, 14MB takes 45s to load. There's also a bug in parsing at the moment; it aborts after loading all records.
* .Kartik K. Agaram2021-08-103-0/+104
|
* .Kartik K. Agaram2021-08-102-9/+42
|
* slack: emit comment parent indices in converterKartik K. Agaram2021-08-101-8/+15
| | | | | | | They're easier to process when loading the data disk. In the process we lose a few more items because they're comments to items we were dropping earlier.
* .Kartik K. Agaram2021-08-101-3/+3
|
* undo my stupid format for post/comment idsKartik K. Agaram2021-08-101-9/+6
| | | | Now items just have a field for parent id.
* .Kartik K. Agaram2021-08-101-2/+0
|
* .Kartik K. Agaram2021-08-101-22/+16
|
* .Kartik K. Agaram2021-08-101-6/+2
|
* .Kartik K. Agaram2021-08-101-3/+1
|
* .Kartik K. Agaram2021-08-101-1/+0
|
* .Kartik K. Agaram2021-08-101-5/+3
|
* .Kartik K. Agaram2021-08-101-7/+4
| | | | | Vestige from when we were scanning all files in the current directory rather than channels.json.
* .Kartik K. Agaram2021-08-101-4/+2
|
* .Kartik K. Agaram2021-08-101-1/+1
|
* .Kartik K. Agaram2021-08-101-6/+5
|
* .Kartik K. Agaram2021-08-101-15/+9
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* .Kartik K. Agaram2021-08-101-2/+2
|
* .Kartik K. Agaram2021-08-101-8/+1
|
* .Kartik K. Agaram2021-08-101-27/+27
|
* .Kartik K. Agaram2021-08-101-9/+0
|
* .Kartik K. Agaram2021-08-083-5/+28
|
* .Kartik K. Agaram2021-08-071-0/+1
|
* .Kartik K. Agaram2021-08-074-10/+111
|
* .Kartik K. Agaram2021-08-061-3/+9
|
* .Kartik K. Agaram2021-08-061-8/+15
|
* beginnings of a Slack archive readerKartik K. Agaram2021-08-062-0/+105
| | | | | | | | I'm hackily depending on Python (3.something) to prototype the disk image creator. But no non-std libs. Once the disk image is created, I've validated that it can be loaded from disk without too much latency (assuming KVM).
* .Kartik K. Agaram2021-08-021-0/+4
|
* better error handling on stray commasKartik K. Agaram2021-08-012-0/+47
|
* .Kartik K. Agaram2021-08-011-13/+16
|
* .Kartik K. Agaram2021-08-011-1/+3
|
* support non-line-oriented processing in next-wordKartik K. Agaram2021-07-2916-36/+73
| | | | Immediately this simplifies support for comments in image data.
* maintain aspect ratio when rendering imagesKartik K. Agaram2021-07-293-8/+43
|
* .Kartik K. Agaram2021-07-291-0/+2
|
* downsampling photos makes the dithering seem worseKartik K. Agaram2021-07-291-2/+2
| | | | We support 128px, so let's use the whole 128px.
* .Kartik K. Agaram2021-07-291-1/+1
|
* shell: reliable image renderingKartik K. Agaram2021-07-291-0/+1
|
* shell: rendering image definitionsKartik K. Agaram2021-07-291-1/+68
| | | | | | Not quite working yet. Only the very first rendering succeeds. After that any keypress triggers a second render which aborts. Image is getting corrupted in memory somehow.
* shell: support loading 128x128px imagesKartik K. Agaram2021-07-286-10/+10
| | | | | | I'm loading them in uncompressed ASCII format, and all streams and gap buffers all over the place need to get massively scaled up to 256KB capacity. But the tests don't yet run out of RAM, so I'll keep going.