/**
 * file: karbytes_09_september_2023.txt
 * type: plain-text
 * date: 09_SEPTEMBER_2023
 * author: karbytes
 * license: PUBLIC_DOMAIN 
 */

Today karbytes published a new web page which is assumed by karbytes to be closed off to future changes at the following Uniform Resource Locator (URL):

https://karbytesforlifeblog.wordpress.com/m_disc_karbytes_2023_data_files_list/

That web page whose URL is the previous line of text is not obviously discover-able just by visiting the home page of the website named Karbytes For Life Blog dot WordPress dot Com because its contents are not listed visibly on any web pages which are opened as a result of a website visitor first visiting the home page of that website and then clicking on hyperlink text links to arrive at a specific web hosted document.

Note that web pages can be looked up using the built-in WordPress dot Com search feature of the website named Karbytes For Life Blog dot WordPress dot Com at the following "nonexistent web page":

https://karbytesforlifeblog.wordpress.com/666

The following URL features a screenshot of the web page whose URL is the previous line of text:

https://raw.githubusercontent.com/karlinarayberinger/KARLINA_OBJECT_extension_pack_1/main/page_not_found_search_form_karbytes_for_life_blog_dot_wordpress_dot_com_09_september_2023.png

* * *

The only major limitation which I am currently aware of concerning the search function in my websites (i.e. Karlina Object dot WordPress dot Com and Karbytes For Life Blog dot WordPress dot Com) is the fact that not all karbytes blog content is hosted on WordPress servers. 

(If a file which is part of karbytes' blogging is not hosted on WordPress dot Com servers, then that file is hosted on GitHub dot Com servers in a public karbytes-created GitHub repository. Only files which are stored on WordPress dot Com servers (and within the website's domain) are searchable via the search function on that WordPress website).

I think that future content which karbytes publishes to its blog (i.e. GitHub and WordPress (and eventually the WayBack Machine at Archive dot Org)) will be more succinct, orderly, non-redundant, and cost-effecient (in terms of minimizing subjective suffering especially from karbytes' point of view) such that the future content will be easier to navigate and more enjoyable to produce and to consume (according to karbytes' point of view) than was karbytes' past content (i.e. the stuff which has been backed up to M_DISC under the label karbytes_2023).

karbytes tentatively plans on creating another set of M_DISCs approximately one year from now of the content which would be considered to be the sequel to karbytes_2023. karbytes plans on naming next year's M_DISCs karbytes_2024.

* * *

Right now, there is only approximately 28 megabytes worth of data to back up to the hypothetical M_DISC named karbytes_2024 (and an M_DISC has a data storage capacity of approximately 4 gigabytes). 

karbytes_2023 contains 76 zip files (and a total of 3.9 gigabytes of data). If what I amassed for karbytes_2024 is smaller than 2 gigabytes by the time I am ready to burn the karbytes_2024 discs, then I will just add karbytes_2023 to karbytes_2024 (and include the missing fie which did not get copied correctly onto the karbytes_2023 discs: KARBYTES_JOURNAL_2022_PART_0_05_september_2023.zip)

* * *

I found a screenshot of what I consider to be decent listening quality black metal:

https://raw.githubusercontent.com/karlinarayberinger/KARBYTES_JOURNAL_2023_PART_30/main/youtube_black_metal_compilation_songlist_07_june_2023.png