this blog clearly does not exist in linear time, which doesn't necessarily mean that i'm a trafalmadorian, so much as it means i blog like one. i post to here like it's a memory archive, because in many ways it actually is. however i did something this evening, so we can post it in real time.
you'll note a new banner on the page, which has the unusual quality of being clickable - it will launch you to the item, as stored at google drive, and as zoomable to a large amount of detail. you are opening a detailed google maps bitmap, pieced together very carefully.
places circled are places that i went to some adventure on, some of which are written about here, and others which will be written about in the future. that map is currently comprehensive, as i've only exited this broad region on two occasions:
1) to go across canada, in 2003. we actually went to new brunswick first, then went to bc, and then went back. we spent some time in bc, and barely any time in the prairies or northern ontario.
2) i went to florida twice as a kid (which is what scranton is about, as i specifically remember stopping there. i also specifically remember jacksonville, florida.)
i have not been to chicago yet, but probably will go to chicago. cleveland and buffalo are likely eventual destinations, whereas boston is less likely. if i make it to new york or pittsburgh, i'll increase the size of the map.
this map will update as i go on more adventures to more places.
9:13
aug 30, 2022
the nature of the internet is changing.
i've recently spent a lot of time editing posts here, under the realization that the writing is being altered somewhere deep on the backend. there is no way for me to prove this and i am unable to prevent it from happening.
google is also changing how it functions. i've always known that all of these services exist to extract data for advertisers, who are the actual consumers. that no longer seems to be enough for google, which is slowly beginning to charge for services and place ads on everything, whether people like it or not. it's also moving to random deletion for people that haven't purchased storage, for files that it deems are not in use. this is potentially catastrophic. in the long run, it indicates that this isn't a safe place to leave your data, unless you want to buy cloud space, which isn't even possible after you're dead. my expectation that this site would stay here for centuries as a time capsule would be something google is taking active steps to prevent from happening. expect google to get more aggressive about enforcing paywalls. you will probably even see paywalls come up at gmail.
it's not a question of whether i can afford to buy space here or not. while i won't pay to remove ads from youtube videos that i'm watching, i would in theory pay to remove ads from youtube videos that i upload for others to watch. this is ideological - i want the internet to be permanent and i want the internet to be free.
i don't know what the answer is, but there is increasingly not a way forwards in this space. the company hosting the space is actively scrubbing it with the eventual intent of putting ads on it; this is what i've deduced is actually happening, as i search for a motive in the edits. i would not accept the imposition of those ads; i would take the site down immediately. we're likely at the same kind of impasse that we had in the late 90s, when domains like fortunecity and geocities just evaporated as their free tiers started getting lathered with ads. i'm realizing i'm too reliant on google and need to find some way to prevent my data from being destroyed by paywalls, or getting deleted in one click when i'm dead.
the real function of the online front-end of this site is the search function on the side. the layout is efficient, but i can emulate it or get around it. what i would find almost impossible to do at any other site is that tree archive. the end format that this writing will exist in is not this blog, and that has not been my intent for some time. the end format is a linearly ordered journal in pdf format that you can download as a file, if you want. while you could search a directory of pdf files, the tree layout then becomes both a liability and an asset, because it's all written entirely backwards. it's helpful to pinpoint, but only to the point of finding the day.
this is a hard problem and i need to think about it. i have some ideas, though.
moving to microsoft or facebook would actually be less useful, and it wouldn't solve the problem of insecure data storage. nor do i want to put up a paywall like a site like substack does. i don't write "newsletters", i scrawl out thoughts; this isn't a magazine to be paid for, it's notes to be thought about, and it's mostly stream of consciousness, at that. i'm not a journalist. at best, i'm an essayist. really, i'm just a nerd. i suspect that many of the people that thought they could make substack into a job are now regretting it, but, again, that's not actually the point. sites like this that are just hosting things to read should be available entirely for free.
you're not the audience here, anyways. i write for the future. my audience isn't born yet; they'll want the pdfs. if i can't maintain the integrity of the data here, i'll have to find somewhere else to store it.
something i've been doing recently is combined posts where i put time stamps on the constituent posts that combine to build up the larger posts. these have been focused ideas, but if i were to generalize it, i'd get something like a digest. if i were then to write everything offline and only post a digest at the end of the day or the end of the week, instead of thousands of posts a month, i could maintain the basic functionality of the site while having a more reliable storage solution to maintain the integrity of the data from backend editing by governments, corporations or advertising executives. i tried to do this once before but i found it was actually more time consuming because i was constantly copying things back and forth. if i restrict the amount of posting to this blog to the digests, that should resolve that problem, and also allow me to actually post the journals as journals in other places in something closer to real time.
i am going to experiment with this approach a little and see how it goes. if i stick with it, the end result will be one post here at the end of each day.
sept 1, 2022
i've changed the settings on the blog so that it only displays one post per page. for now, it will front post the "internet is changing" post, which will eventually be backposted to the aug 30th digest. the reason i'm doing this is to ensure that the page is more directly navigable. right now, it will seem "broken"; in the long run, once the new format works it's way in, the forward and backward buttons will create a more readable, linear blog that is organized in digests that are better navigable by day.
when this is working properly, suppose that the front page has the digest for sept 20th, 2022. if i hit "previous posts", which i suspect nobody does, it will go directly to the digest for sept 19th. if i hit previous posts again, it will strictly show sept 13th. this will undo the backwards posting problem that is endemic to social media, which has long bothered me (see my twitter page fore a satire of it).
i need to temporarily break my silence.
i do hope that gorbachev's funeral is open casket.
it turns out that the downside of the scotch bonnets is that my hands are left viciously burning for hours after handling them.
i don't want to waste large amounts of plastic repeatedly discarding gloves for the single use of handling hot peppers. i've just been going commando on them. we'll see what else i can think of. i suppose i always have a few plastic bags on their way to the recycle drying in the sink. i could just reuse the same one over and over and put it in the freezer. yeah, that sounds like an easy answer, actually.
like, i want to wash my face right now, and i can't. i can barely even type. yet, i'm not tired. so, what to do, exactly?
another frequent undesired edit that i'm seeing as i archive posts here for better data integrity in storage is the replacement of assyria with babylon. i am sure i wouldn't make that mistake, as i understand the words i'm using (and the editor obviously doesn't, but is rather being driven by fuzzy, racist ideas of semitic supremacy through the perverse filter of ethnic nationalism).
the semitic babylonians had a different culture and religion than the non-semitic (and apparently caucasian) sumerians, and they clearly had a different language and were clearly of a different race, but they largely built their society on top of the existing sumerian one. while there are definite destruction horizons in both the archaeological record and the historical record (as we can reconstuct it from ancient cuneiform tablets), babylonian culture was largely developed out of continuity from sumerian culture, so there is a definite process of succession. i'm very clear to point that out and speak of it in those terms, especially in regards to the astronomy, which is about the only thing i really care about in regards to sumeria or babylonia.
the assyrians were half-literate barbarians that took over some cities in the north by the force of violence and created a brutal, draconian dictatorship responsible for immense destruction and widespread genocide. while the babylonians existed in succession to sumeria, the assyrians destroyed what was left of sumerian culture and substituted a wide-ranging dark age in it's place. the destruction of babylon by assyria was probably worse, in terms of data loss, than the destruction of baghdad by the mongols and is the direct reason we know so little about ancient sumeria beyond what we can reconstruct through fragments of clay found in abandoned 3000 year old buildings.
while the assyrians and babylonians were both semitic peoples, and that may be all that matters to the editor, you really can't substitute one for the other. one was an advanced civilization built on top of the alpha cradle of civilization, while the other was a barbaric monstrosity that ultimately completely destroyed it. the compare and contrast essay needs to be about the contrast.
the editor uses the term "babylon" in a vague, colloquial sense that implies a strictly judaic religious context. this isn't somebody with much understanding of secular history or the science of archaeology, but somebody that gets their naive "understanding" of history entirely from religious mythology. all the editor understands about babylon is what is written about it by the cultural conservatives that wrote the hebrew bible.
by switching to offline writing for data storage, i hope i can get around this unwanted editing to the point that i can actually prove it's happening. as stated repeatedly, all i can find is consistency in the emails, which are supposed to act as data redundancy, even when it comes to posts that i'm certain were edited. i've convinced myself this is happening by tricking the system, but it doesn't let me prove it (yet.), as it is self-correcting in my own editing to create a false, projected reality of manipulated stasis. worse, it's driving me bonkers trying to prove my writing is being altered, and being unable to do so. i'm either correct, or i've lost my mind; the fact that i'm lucid suggests the former.
i'm going to catch them soon, i'm sure of it. it will be easy enough to run the two sources through a diffchecker, but i can't do that when everything is online and nothing is certain, as a consequence of it; i can neither have confidence in the integrity of the emails, nor in the integrity of the blog posts, as accurate alpha sources. proving that corruption is happening requires having a source i can trust the integrity of.
for now, note yet another example of clear manipulation in the editor's confused use of assyria and babylonia as interchangeable terms, due to ignorance resulting from the racism that results from the supremacy inherent to ethnic nationalism.
glasnost.
i would support the existence of the climate police. that sounds like a great idea, if you ask me.
i mean, you're serious about this, or you're not. the reality is that pollution is a crime against humanity and that there should be an enforcement mechanism to enforce that reality. a climate police would be a proportionate, reasonable response to the challenge we face; conversely, tax cuts for the rich to try to influence their behaviour followed by slaps on the wrist for non-compliance in the name of "freedom" is not reasonable or proportionate, and is not taking the situation nearly seriously enough.
when somebody proposes a solution that might actually work, the government feels the need to debunk the idea. it's reflective of where we actually are as a society on this, and what the set of likely outcomes actually is.
if we're going to have police, this is exactly what they should be doing. instead, we send people out with guns to enforce property rights that allow people to pollute. we'll get what we deserve for it, in the end.
reference:
"environment canada says online reports of 'climate police' are false", cbc news, sept 1, 2022
an ye harm none, do what ye will
ok.
not only does pollution not harm none, but pollution harms all. it is not a lesser crime deserving of a lesser punishment, or merely a behavioural problem worthy of scolding, as one does a child; it is the worst type of crime that is deserving of the most severe penalties, and the most egregious form of anti-social behaviour, indicative of a severe deficit of basic decency and a depravity of character of the most irredeemable quality.
climate police are a wonderful idea. let's do it right away.
i don't think that it's likely that kiev will succeed in taking control of territory from the russians (at this point, nothing can be verified, as neither side is reliable. as was the case in syria, the most reliable source appears to be the british government, which is not very helpful.), but i think that it is likely that the destruction of infrastructure around the dnieper river (a massive river that splits ukraine in half) by kiev will have the outcome of partitioning the country in half. the media coverage is suggesting that this is a defensive act, intended to prevent russia from being able to move supplies from the eastern side of the river to the western side of the river, and this is a valid analysis. ukraine is half forest and half steppe, but it has several very substantive rivers flowing through it, and being able to control those rivers is key to controlling the country (something i pointed out months ago). the corollary of that, however, is that it also means that kiev would have no serious chance of moving supplies to the eastern side of the river, either, and consequently no chance of a successful counter-attack (if such an idea ought to be taken seriously, anyways). it's clear enough at this point that the destruction of infrastructure is an intentional tactic, indicating one of two possibilities:
(1) kiev is walking into the vacuum created by russian indecisiveness and unilaterally partitioning the country into east and west (this division is historical) or
(2) while kiev might succeed in preventing further russian advances for at least a little while by destroying the region's infrastructure, it will do so at the unintentional permanent loss of the eastern and southern half of the country, which it will now not have the infrastructure in place to retake (if such a thing was ever likely in the first place). this would be a short term pyrrhic victory at the long term loss of an unintentional partition of the country.
these options aren't strictly mutually exclusive. i would suspect that they realize that what they're doing is going to partition the country, and potentially for a very long period, and that they don't like that outcome and will seek to undo it, but are doing it because they realize it's their last chance to prevent a full scale invasion of the whole country. it's also a scorched earth policy, in function and intent.
what can moscow do?
moscow has, for obvious reasons, been attempting to avoid inflicting the kind of damage in ukraine that kiev has been inflicting since they got those yankee rockets. moscow is not invading ukraine to topple a foe or control a small area of resources like the united states did in afghanistan or iraq; russia is intending on assimilating as much of the region back into russia as it can, and has rightfully been arguing that the area is historically russian, and consequently a kind of lost territory, an argument that only pertains to some abstraction of the country's east and south, although exact boundary lines are not entirely clear. however, if kiev decides to essentially resort to terrorism by destroying all of the infrastructure across the dnieper in an attempt to forcefully partition the state as a defensive manoeuvre (at least in the short run), russia is left with the need to reciprocate, or face troops and resources cut off on the other side of the dnieper. they could destroy the infrastructure over the bug, then, but how helpful that would be is not clear, and it may leave them with the same pyrrhic outcome.
looking at a map, kiev may very well succeed in defending itself by bombing out all of the bridges over the dnieper, and moscow would be left with no real alternative but to invade from a different direction.
if the ukrainians want to do this, then, perhaps the russians should help them and bomb out the bridges across the river all the way north to belarus. this would have the effect of making it impossible for ukraine to resupply it's own troops, leaving stranded divisions in territory contiguous to russia, and facilitate the russian advance to the dnieper across the northeast of the country. the situation would then need to be re-evaluated, once that is finished.
so, this is day one of the new digest format. i hope my intent is a little more clear. i have this stored in both doc and html format in a secret location, which will make it easier to print to pdf in a 5x8" format for journal publication, or viewed on a pc or laptop. throw your phone in the garbage.
what am i doing with the recent posts that i don't trust the integrity of?
first, i'm taking it all down. then, i'm copying it over to the secret location. after that, i'll need to inspect it, probably rewrite the bulk of it and eventually repost it. it will come up in a 5x8" printable format as i repost it.
this process won't be very fast, and the last few months of posts might consequently be offline for a long time.
it is worth noting, though, that i'll be updating the other blogs now as digests as well.
when this is working properly, suppose that the front page has the digest for sept 20th, 2022. if i hit "previous posts", which i suspect nobody does, it will go directly to the digest for sept 19th. if i hit previous posts again, it will strictly show sept 13th. this will undo the backwards posting problem that is endemic to social media, which has long bothered me (see my twitter page fore a satire of it).
2:08
i need to temporarily break my silence.
i do hope that gorbachev's funeral is open casket.
3:44
it turns out that the downside of the scotch bonnets is that my hands are left viciously burning for hours after handling them.
i don't want to waste large amounts of plastic repeatedly discarding gloves for the single use of handling hot peppers. i've just been going commando on them. we'll see what else i can think of. i suppose i always have a few plastic bags on their way to the recycle drying in the sink. i could just reuse the same one over and over and put it in the freezer. yeah, that sounds like an easy answer, actually.
like, i want to wash my face right now, and i can't. i can barely even type. yet, i'm not tired. so, what to do, exactly?
9:33
another frequent undesired edit that i'm seeing as i archive posts here for better data integrity in storage is the replacement of assyria with babylon. i am sure i wouldn't make that mistake, as i understand the words i'm using (and the editor obviously doesn't, but is rather being driven by fuzzy, racist ideas of semitic supremacy through the perverse filter of ethnic nationalism).
the semitic babylonians had a different culture and religion than the non-semitic (and apparently caucasian) sumerians, and they clearly had a different language and were clearly of a different race, but they largely built their society on top of the existing sumerian one. while there are definite destruction horizons in both the archaeological record and the historical record (as we can reconstuct it from ancient cuneiform tablets), babylonian culture was largely developed out of continuity from sumerian culture, so there is a definite process of succession. i'm very clear to point that out and speak of it in those terms, especially in regards to the astronomy, which is about the only thing i really care about in regards to sumeria or babylonia.
the assyrians were half-literate barbarians that took over some cities in the north by the force of violence and created a brutal, draconian dictatorship responsible for immense destruction and widespread genocide. while the babylonians existed in succession to sumeria, the assyrians destroyed what was left of sumerian culture and substituted a wide-ranging dark age in it's place. the destruction of babylon by assyria was probably worse, in terms of data loss, than the destruction of baghdad by the mongols and is the direct reason we know so little about ancient sumeria beyond what we can reconstruct through fragments of clay found in abandoned 3000 year old buildings.
while the assyrians and babylonians were both semitic peoples, and that may be all that matters to the editor, you really can't substitute one for the other. one was an advanced civilization built on top of the alpha cradle of civilization, while the other was a barbaric monstrosity that ultimately completely destroyed it. the compare and contrast essay needs to be about the contrast.
the editor uses the term "babylon" in a vague, colloquial sense that implies a strictly judaic religious context. this isn't somebody with much understanding of secular history or the science of archaeology, but somebody that gets their naive "understanding" of history entirely from religious mythology. all the editor understands about babylon is what is written about it by the cultural conservatives that wrote the hebrew bible.
by switching to offline writing for data storage, i hope i can get around this unwanted editing to the point that i can actually prove it's happening. as stated repeatedly, all i can find is consistency in the emails, which are supposed to act as data redundancy, even when it comes to posts that i'm certain were edited. i've convinced myself this is happening by tricking the system, but it doesn't let me prove it (yet.), as it is self-correcting in my own editing to create a false, projected reality of manipulated stasis. worse, it's driving me bonkers trying to prove my writing is being altered, and being unable to do so. i'm either correct, or i've lost my mind; the fact that i'm lucid suggests the former.
i'm going to catch them soon, i'm sure of it. it will be easy enough to run the two sources through a diffchecker, but i can't do that when everything is online and nothing is certain, as a consequence of it; i can neither have confidence in the integrity of the emails, nor in the integrity of the blog posts, as accurate alpha sources. proving that corruption is happening requires having a source i can trust the integrity of.
for now, note yet another example of clear manipulation in the editor's confused use of assyria and babylonia as interchangeable terms, due to ignorance resulting from the racism that results from the supremacy inherent to ethnic nationalism.
10:21
glasnost.
11:38
11:51
i would support the existence of the climate police. that sounds like a great idea, if you ask me.
i mean, you're serious about this, or you're not. the reality is that pollution is a crime against humanity and that there should be an enforcement mechanism to enforce that reality. a climate police would be a proportionate, reasonable response to the challenge we face; conversely, tax cuts for the rich to try to influence their behaviour followed by slaps on the wrist for non-compliance in the name of "freedom" is not reasonable or proportionate, and is not taking the situation nearly seriously enough.
when somebody proposes a solution that might actually work, the government feels the need to debunk the idea. it's reflective of where we actually are as a society on this, and what the set of likely outcomes actually is.
if we're going to have police, this is exactly what they should be doing. instead, we send people out with guns to enforce property rights that allow people to pollute. we'll get what we deserve for it, in the end.
reference:
"environment canada says online reports of 'climate police' are false", cbc news, sept 1, 2022
19:29
an ye harm none, do what ye will
ok.
not only does pollution not harm none, but pollution harms all. it is not a lesser crime deserving of a lesser punishment, or merely a behavioural problem worthy of scolding, as one does a child; it is the worst type of crime that is deserving of the most severe penalties, and the most egregious form of anti-social behaviour, indicative of a severe deficit of basic decency and a depravity of character of the most irredeemable quality.
climate police are a wonderful idea. let's do it right away.
20:07
i don't think that it's likely that kiev will succeed in taking control of territory from the russians (at this point, nothing can be verified, as neither side is reliable. as was the case in syria, the most reliable source appears to be the british government, which is not very helpful.), but i think that it is likely that the destruction of infrastructure around the dnieper river (a massive river that splits ukraine in half) by kiev will have the outcome of partitioning the country in half. the media coverage is suggesting that this is a defensive act, intended to prevent russia from being able to move supplies from the eastern side of the river to the western side of the river, and this is a valid analysis. ukraine is half forest and half steppe, but it has several very substantive rivers flowing through it, and being able to control those rivers is key to controlling the country (something i pointed out months ago). the corollary of that, however, is that it also means that kiev would have no serious chance of moving supplies to the eastern side of the river, either, and consequently no chance of a successful counter-attack (if such an idea ought to be taken seriously, anyways). it's clear enough at this point that the destruction of infrastructure is an intentional tactic, indicating one of two possibilities:
(1) kiev is walking into the vacuum created by russian indecisiveness and unilaterally partitioning the country into east and west (this division is historical) or
(2) while kiev might succeed in preventing further russian advances for at least a little while by destroying the region's infrastructure, it will do so at the unintentional permanent loss of the eastern and southern half of the country, which it will now not have the infrastructure in place to retake (if such a thing was ever likely in the first place). this would be a short term pyrrhic victory at the long term loss of an unintentional partition of the country.
these options aren't strictly mutually exclusive. i would suspect that they realize that what they're doing is going to partition the country, and potentially for a very long period, and that they don't like that outcome and will seek to undo it, but are doing it because they realize it's their last chance to prevent a full scale invasion of the whole country. it's also a scorched earth policy, in function and intent.
what can moscow do?
moscow has, for obvious reasons, been attempting to avoid inflicting the kind of damage in ukraine that kiev has been inflicting since they got those yankee rockets. moscow is not invading ukraine to topple a foe or control a small area of resources like the united states did in afghanistan or iraq; russia is intending on assimilating as much of the region back into russia as it can, and has rightfully been arguing that the area is historically russian, and consequently a kind of lost territory, an argument that only pertains to some abstraction of the country's east and south, although exact boundary lines are not entirely clear. however, if kiev decides to essentially resort to terrorism by destroying all of the infrastructure across the dnieper in an attempt to forcefully partition the state as a defensive manoeuvre (at least in the short run), russia is left with the need to reciprocate, or face troops and resources cut off on the other side of the dnieper. they could destroy the infrastructure over the bug, then, but how helpful that would be is not clear, and it may leave them with the same pyrrhic outcome.
looking at a map, kiev may very well succeed in defending itself by bombing out all of the bridges over the dnieper, and moscow would be left with no real alternative but to invade from a different direction.
if the ukrainians want to do this, then, perhaps the russians should help them and bomb out the bridges across the river all the way north to belarus. this would have the effect of making it impossible for ukraine to resupply it's own troops, leaving stranded divisions in territory contiguous to russia, and facilitate the russian advance to the dnieper across the northeast of the country. the situation would then need to be re-evaluated, once that is finished.
21:28
so, this is day one of the new digest format. i hope my intent is a little more clear. i have this stored in both doc and html format in a secret location, which will make it easier to print to pdf in a 5x8" format for journal publication, or viewed on a pc or laptop. throw your phone in the garbage.
what am i doing with the recent posts that i don't trust the integrity of?
first, i'm taking it all down. then, i'm copying it over to the secret location. after that, i'll need to inspect it, probably rewrite the bulk of it and eventually repost it. it will come up in a 5x8" printable format as i repost it.
this process won't be very fast, and the last few months of posts might consequently be offline for a long time.
it is worth noting, though, that i'll be updating the other blogs now as digests as well.
23:43
sept 2, 2022
so, that's now updated for the day.
today's digests include one 2-3 page post for the following blogs:
1) the dsdfghghfsdflgkfgkja politics/general blog, which has recently been the only blog i've been posting to. almost everything gets posted to that blog, with the exception of very targeted posts to the music blogs. this is listed as "rants" in the list on the side of the page.
2) the deathtokoalas "music review" blog, as it is listed on the side. this is a general cultural commentary blog that also features some sporadic commentary on lighter news sources. i included the posts on climate change and the historical analysis for the reason that these topics frequently overlap with cultural discussions from well known authors (although the post in question does not), and that qualifies as cultural commentary. my decision tree on this is rather complicated and there's going to be a lot of ambiguity around it. the only post i removed from this digest was the analysis of the recent ukrainian tactic of destroying infrastructure around the dnieper as a scorched earth policy to attempt to slow the russian advance into the rest of ukraine. this blog would generally exclude specifically political commentary or analysis, like statistical analysis of polling results, which was the real basis of separating it out, as i wanted my political and cultural commentaries split into different streams. in better times, it was directed at actual music reviews. i don't really know how much of an interest i have in that, moving forwards, but i have always had a sort of a hitchensian gossip streak and this blog will at the least allow for that.
3) the peculiar adventures of j, or the travel blog, as it is listed on the side, which was supposed to be the blog i used to narrate events in real-time while i was out with my chromebook in order to quarantine my main account from insecure networks but has instead become a general geography blog since i had to move to the chromebook for general network access, which led to me merging the two accounts. the scope of the blog has had to increase to be self-contained, but the idea is that this blog recollects events that occur somewhere outside, in the real world, from a first-person perspective. it isn't always, but it's supposed to be a little more narrative based. all posts posted to the general blog today were also posted to the travel blog, which may seem weird, but it just happened to be that all of the posts on this day fit into one of the categories that this blog touches upon. on other days, posting to this blog may be quite light.
i will not normally describe the contents of digest updates in detail, but this is a good opportunity to repost what the purpose of the various blogs is. i'm in the process of finally reconstructing my typing station, so it is time to get back to normal posting schedules at all of the various blogs. this systems collapse has been lengthy and deep, but i am rectifying it, even as i'm convinced i'm still under extreme surveillance, despite not understanding why.
there are a number of blogs that were not updated today:
- the inri records blog is intended to mirror my music archive at bandcamp. this has been left stranded for a while now, but i should be back to it shortly.
- the current music blog is a music journal that is maintained in order to document my recording process for future generations and is consequently only active when i am actually recording. soon. i hope.
- j's journal is the blog written from my perspective when i was a young child as a vehicle to explain influences on my musical development, while growing up. i will need to aggressively get back to writing this very shortly. i have just realized that the formatting on it has annoyingly broken for a second time, so i'll need to fix that, first. the first time, i just needed to clear cookies, so maybe it's not so bad.
- the alter-reality is the journal written from my perspective as a teenager, which is when my recording career first began. i will need to finish the childhood journal before i get back to that.
- the music timeline was created in order to replace my facebook music page, because i actually liked the timeline feature which got buried and destroyed by successive facebook updates, and remains a work in progress. the only reason i didn't delete my facebook page in 2013 is that i liked the timeline, as a way to present data historically.
4) as of right now, i have added a new blog on the side called the "diet blog". today's digest only includes one post to this new blog, about scotch bonnet peppers. this blog will eventually be constructed to include all of the posts that have been posted to the general blog about my diet, starting at the end of 2020. i may or may not decide to backdate this blog, but the intent is that it starts in late 2020 and runs until i have attained dietary perfection.
i served a document this morning and will need to get to the court house today to swear an affidavit for it. i will otherwise be continuing the archiving process overnight.
i wanted to get out today, swear an affidavit and take the 50k ride, but i didn't get to sleep until late in the afternoon because it took longer to get the august posts archived than i thought it would and i had to reserve the document because court staff misunderstood the direction provided to it and i decided it was easier to just put the attorney general's address on the document rather than argue about originating processes. this was pointless, ultimately, and it meant i lost the key part of the day, which forced me to lose the rest of it.
i at least do have all august posts taken down, now, and can get to removing july posts for the night.
i will not normally describe the contents of digest updates in detail, but this is a good opportunity to repost what the purpose of the various blogs is. i'm in the process of finally reconstructing my typing station, so it is time to get back to normal posting schedules at all of the various blogs. this systems collapse has been lengthy and deep, but i am rectifying it, even as i'm convinced i'm still under extreme surveillance, despite not understanding why.
there are a number of blogs that were not updated today:
- the inri records blog is intended to mirror my music archive at bandcamp. this has been left stranded for a while now, but i should be back to it shortly.
- the current music blog is a music journal that is maintained in order to document my recording process for future generations and is consequently only active when i am actually recording. soon. i hope.
- j's journal is the blog written from my perspective when i was a young child as a vehicle to explain influences on my musical development, while growing up. i will need to aggressively get back to writing this very shortly. i have just realized that the formatting on it has annoyingly broken for a second time, so i'll need to fix that, first. the first time, i just needed to clear cookies, so maybe it's not so bad.
- the alter-reality is the journal written from my perspective as a teenager, which is when my recording career first began. i will need to finish the childhood journal before i get back to that.
- the music timeline was created in order to replace my facebook music page, because i actually liked the timeline feature which got buried and destroyed by successive facebook updates, and remains a work in progress. the only reason i didn't delete my facebook page in 2013 is that i liked the timeline, as a way to present data historically.
4) as of right now, i have added a new blog on the side called the "diet blog". today's digest only includes one post to this new blog, about scotch bonnet peppers. this blog will eventually be constructed to include all of the posts that have been posted to the general blog about my diet, starting at the end of 2020. i may or may not decide to backdate this blog, but the intent is that it starts in late 2020 and runs until i have attained dietary perfection.
i served a document this morning and will need to get to the court house today to swear an affidavit for it. i will otherwise be continuing the archiving process overnight.
3:03
i wanted to get out today, swear an affidavit and take the 50k ride, but i didn't get to sleep until late in the afternoon because it took longer to get the august posts archived than i thought it would and i had to reserve the document because court staff misunderstood the direction provided to it and i decided it was easier to just put the attorney general's address on the document rather than argue about originating processes. this was pointless, ultimately, and it meant i lost the key part of the day, which forced me to lose the rest of it.
i at least do have all august posts taken down, now, and can get to removing july posts for the night.
23:23
sept 23, 2022
while i'm annoyed by the unwanted editor's insistence on corrupting the content of my posts, they are mostly interested in politics. i am moving to offline writing, strictly, but i would at the least like to maintain a personal narrative in real time, and the more appropriate place to do that is in this space.
if the unwanted editor interferes, i'll have to take this down, too.
let's give it a try.
1:52
sept 27, 2022
no. i don't have confidence in posting here, either.
i've taken down the entire blog.
it will rise again.
22:56