Ksable's Nest
= A blog about life & tech =
kissablecho
Kissablecho's personal blog — recording life, sharing technology, anime & white stockings enthusiast.
Posts
The third year of high school is really busy, time is really scarce. School started a month ago, and until now I've only had two days of vacation to rest. I managed to squeeze in a bit of time to continue porting the Typecho theme, and now it's finally done. I'm starting to think about changing themes.
Readest is a modern open-source e-book reader designed for immersive reading. It has 10.1k stars on GitHub, making it an excellent project. However, the GitHub project page only provides a build guide without detailed instructions on how to configure the project. Then I scoured the entire internet and found that there is no deployment tutorial available anywhere online; all the content is just promotional articles introducing Readest. The content of these articles seems to be almost identical, with dozens of pieces appearing to be copied from each other. This article serves as my personal notes on private deployment, and so far I have only completed the web-based deployment, for reference only.
This article is a practical tutorial on creating a crawler for a comic website, detailing how to use Python to scrape comic resources from the site. The tutorial starts by analyzing the website's dynamic loading mechanism, then step by step explains the process of obtaining the comic ID (galleryid), parsing comic information (galleryinfo), and generating image download links. It focuses on how to construct image URLs by processing JavaScript functions (such as `url_from_url_from_hash`) and variables, and provides a complete Python script with features including exception handling, proxy settings, and safe file naming. Finally, it achieves batch downloading and local saving of comic images (supporting WebP format and metadata recording), making it suitable for crawler enthusiasts with some Python foundation to refer to and learn from.
0
I've spent half a day finally getting the website's Service Worker cache configuration set up. Previously, I always thought the website's speed wasn't fast enough, often having to wait several seconds for it to load. Background images would always take a delay before loading properly. I've already done my best to maximize the network loading speed, and the first load has been optimized to the fastest possible speed. I've also added cache-control response headers to all resources I can control. However, when opening the site again, some images and JS files still aren't cached, causing them to briefly appear white before loading. Today I went through the hassle of configuring the Service Worker...