moved a few todo item from GTD to operational

* COMMENT -*- mode: org -*-

#+Date: 2018-05-04

Time-stamp: <2023-10-18>

Time-stamp: <2024-04-06>

#+STARTUP: content

* notes                                                               :entry:

** 2022-03-14 project dir structure

* current                                                             :entry:

** 

** 2024-04-06 rd client: log should use local datetime not UTC time.

** 2024-04-06 rd client: when server side doesn't support GET /rd/ api.

give a more clear msg to client side.

it's not client side's fault.

#+begin_quote

root@pve:/wh01/share/tv-series/Kingdom# rd http://1.116.206.228:8082/kingdom.tar

2024-04-06T07:14:31  E  GET /rd/ api failed: "No redis connection, GET /rd/ disabled"

2024-04-06T07:14:31  E  1 urls failed/skipped.

#+end_quote

** 2024-03-12 rd-api, if file is already transferred block by block, I can support

live compress easily. If the client request compress as param such as

?compress=zstd. default is no compress.

- when the source file is just tar, not compressed format like squashfs or

  zip, this can speed up transfer by delaying compress.

** 2024-03-12 rd, add an DL remaining time estimate, based on estimated DL speed.

each block has a block size. I know when it is started and when it is

finished. I know how many more blocks to fetch. it should be easy to

estimate. calculate a moving avg speed using the last 5 blocks DLed.

** 2023-11-12 rd-api unicode path bug. rd ipv6 URL bug.

SCHEDULED: <2024-04-08 Mon>

- on de05,

  rd-api -h :: -p 8083 --redis-host 10.96.195.242

  on pve,

  cd /wh01/share/songs/

  rd http://[2a01:4f8:c0c:9c42::1]:8083/可一儿歌.tar

  BUG nope. rd doesn't support ipv6 URL.

  rd http://49.12.207.182:8083/可一儿歌.tar

- rd-api: .: openBinaryFile: inappropriate type (is a directory)

  2023-11-12T06:07:53  I  user request rd metadata for "."

  BUG: unicode character in PATH is not properly supported.

** 2022-03-15 rd client, is there a built-in repeat/loop function?

IO () -> IO ()