Better explanation about continuous updates (#7)

- Better explanation about continuous updates (eb5580619e9502d54c61ecfe465ef59e237eafa7)


Co-authored-by: Shih-Ying Yeh <KBlueLeaf@users.noreply.huggingface.co>

README.md

@@ -39,6 +39,7 @@ Images are provided in the full original form (be that JPG, PNG, GIF or otherwis
 
 The reason for the bucketing is that a single directory would cause pathological filesystem performance, and modulo ID is a simple hash which spreads images evenly without requiring additional future directories to be made or a filesystem IO to check where the file is. The ID is not zero-padded and files end in the relevant extension, hence the file layout looks like this:
 
+
 ```bash
 $ tree / | less
 
@@ -53,8 +54,23 @@ $ tree / | less
 │   │   │   ├── 210001.png
 │   │   │   ├── 3120001.webp
 │   │   │   ├── 6513001.jpg
+│   │
+│   ├── recent
+│   │   ├── 0000 -> data-1000.tar
+│   │   ├── 0001 -> data-1001.tar
+│   │
+│   ├── updates
+│   │   ├── 20240319
+│   │   │   ├── dataset-0.tar
+│   │   │   ├── dataset-1.tar
+│   │   │
+│   │   ├── 2024xxxx
+│   │   │   ├── dataset-0.tar
+│   │   │   ├── dataset-1.tar
 
 ```
+
+Where `data-{1000..1999}.tar` refer to recent update files (should be updated every few months) and `updates` refer to fast patches (should be updated every few days to few weeks).
           
 Currently represented file extensions are: avi/bmp/gif/html/jpeg/jpg/mp3/mp4/mpg/pdf/png/rar/swf/webm/wmv/zip.