3 files changed, 165 insertions, 7 deletions
diff --git a/news/1725266053-considerations_on_decentralization_tech b/news/1725266053-considerations_on_decentralization_tech
index 59580dd..f799cc3 100644
--- a/news/1725266053-considerations_on_decentralization_tech
+++ b/news/1725266053-considerations_on_decentralization_tech
@@ -5,18 +5,18 @@ a step forward into utilizing the said network in a blockchain project that its
 initial claim was to furtherly bring the network to people to counter censorship
 that is imposed by governments and ISPs.
 
-Let me critisize, right away, that the development of said blockchain project
-was too slow, incompatible and having weird inconcistences on its inner tools.
+Let me criticize, right away, that the development of said blockchain project
+was too slow, incompatible and having weird inconsistencies on its inner tools.
 
 In a course of 5 years, the btc-suite, a go lang source code was updated to meet
 the symbols (ticker if you may) of said project, change the top amount of coins
 that could ever existed in it, change the algorithm for mining the SHA256 space
-to mining for announcing bandwidth availablily.
+to mining for announcing bandwidth availability.
 
 There were several, in my opinion, useless wallet implementations, which also
 brought a year-lasting confusion to the project. Particularly, segwit wallets,
 mining wallets and a form of lightweight wallets. To cast some light into the
-abovementioned incompatibility, you couldn't mine coins on a "lightweight" one.
+above mentioned incompatibility, you couldn't mine coins on a "lightweight" one.
 
 To further confusion, documentation was never in sync with what is going on and
 what a new comer would need to learn about the project in order to participate.
@@ -76,7 +76,7 @@ paragraph is huge. But the most laughable part, is that after you send your keys
 to them, "you can still use them" as they mentioned. Did I mention that the tool
 was closed source? Yes! And the answer of the developer was "because". Note that
 private keys being sent to them is not confirmed and it is an assumption solely
-based on the fact that the developer repeatdly denied access to the source code.
+based on the fact that the developer repeatedly denied access to the source code.
 
 About the selective airdrop, it was proven by several members of the community
 that their keys weren't redeemable on the new token. To add more into that, keys
@@ -87,7 +87,7 @@ To get back to the 3 investors, that it seems that they did launch a couple of
 rug-pull projects in the past, it is all about money. They seem to understand
 very well what money can buy and how one can appear as a good samaritan to help
 an interesting project while the main goal is to see return on their
-investements. They, as well as the main developer, were and still are thirsty
+investments. They, as well as the main developer, were and still are thirsty
 for financial gains and control. Not only they were trying to take control of a
 decentralized blockchain project but when they saw that this couldn't happen,
 they tried every possible scenario that a company would do in order to maintain
@@ -106,7 +106,7 @@ the rules, they are the ones that broke them continuously.
 
 In the end, the whole effort on this article is to cause an alert in other
 communities that are also under a same type of structure, authoritarian-types.
-The project I am refering to, will remain unnamed for the time being and
+The project I am referring to, will remain unnamed for the time being and
 possibly it will be revealed when the time is right. I wouldn't like to give
 them attention, since the only thing that matters to them is liquidity. And it's
 true, later from the announcement, their channels only accept airdrop claim
diff --git a/news/1726334198-knowing_a_person_online b/news/1726334198-knowing_a_person_online
new file mode 100644
index 0000000..518ee38
--- /dev/null
+++ b/news/1726334198-knowing_a_person_online
@@ -0,0 +1,65 @@
+Knowing a person online for years, getting vibes of honesty, participating in
+interesting projects, gets involved with blockchain development, starts their
+own blockchain, but maintains a mindset of ownership.
+
+Furthermore, colors of authoritarian noise came along the way as well, slowly
+evolving from a "I know better" perspective, not giving a dime about others'
+feelings.
+
+This seems to be understood as determination by that person. So it went on for
+years, hidden behind the facade of a good/noble person.
+
+The outcomes of looking at their work though, are not hidden that much. The said
+determination made the first peer to peer network to be tainted by such mindset
+that the architecture of it is, since 2018, an inequality network. To add more
+in that, the work was never audited as it should. Cryptographic algorithms
+accompanying the software were written from scratch, breaching in silence the
+trust of the user-base.
+
+But for all the above, even if anyone spoke up about those misconceptions and
+detouring from the original idea, they did not reach my ears or eyes.
+During the past month, the said person stroke once more, this time, even more
+methodically and aware of what he was about to do. Taking back previous claims
+about the direction of the project which in his words, was community driven.
+
+A famous quote applies here for the fellow person: "Dictators free their selves,
+but they enslave the people". In such situation though, with humanity working
+collectively towards freedom and equality, the communities' backlash was and
+still is tremendous. A thing that in no way was expected by the actor.
+
+As every dictator, he opposed his own people, trying to silence them and forced
+them to exile. Before getting in my hands proofs on chain and commit histories,
+trying to convince he is most likely on the wrong, I met up a new character, a
+relentless one that also moved quickly to oppose me as well. Even in such
+position that I was quickly put in exile as well. I did my best to remind the
+person about values and such, but apparently, when liquidity becomes the new
+belief system, nothing really matters.
+
+This whole situation left me angered. Not anger towards the person but towards
+me, getting uncomfortable with my own decisions to trust not the person, but
+their code. A code that the person sees as his legacy, a classic dictator's
+mindset, but even with my little experience I can understand that it is
+effectively dangerous to run. A code base that for more than 10 years is
+depending on an unstable release of a library which was receiving updates
+tactically and had many stable releases since then.
+
+That would be a more honest take on his partners presentation, particularly on
+the session "Meet CJD". The ID of this post will be included as a reference, as
+well with a date of posting, in my personal not decentralized blog feed that you
+can find at https://git.kaotisk-hund.com/01-NEWS/.git/tree/news shortly after
+this is posted here, in pkteerium.xyz, operated by the said person.
+
+Thanks for reading and be always alarmed,
+Kaotisk Hund
+
+
+PS: I should clarify that when referring to "CJD", I mean "Cartman James
+DeLisle". Any similarities with real people is unintentional and the whole post
+is a work of fiction dealing with philosophical questions and values.
+
+The above could be found at (unless I got banned from the site):
+- https://pkteerium.xyz/@kaotisk/posts/Am07AS7WJjQ15X7L0q
+
+2024.09.27 - Update: I left pkteerium cause I chose to do so. I prefer to be on
+my own than to depend on anyone's will, even more if it is the fictional person
+I mentioned above.
diff --git a/news/1729396343-radio_station_emulator b/news/1729396343-radio_station_emulator
new file mode 100644
index 0000000..ce128dd
--- /dev/null
+++ b/news/1729396343-radio_station_emulator
@@ -0,0 +1,93 @@
+Radio Station Emulator
+======================
+
+First of all, since you are reading this at most probably the web/internet, let
+me clarify that the "radio station" part is referring to a webradio station, a
+station that resembles the classic "radio" that plays on the FM/AM and other
+bands which instead of transmitting signal to the airwaves, it actually streams
+data over the internet.
+
+Secondly, the "emulator" part means that the particular radio station we are
+going to talk about it has mainly pre-recorded shows to play on its program.
+Live programs are also possible in this emulator by extending the core idea but
+to keep it simple and trully emulator we will only consider the pre-recorded
+shows, for ease and to not create a hybrid emulator, in the sense that sometimes
+is an emulator, some other times is not, cause it actually plays live.
+
+The main goal is to eliminate the streaming of data in its synchronous form and
+make it asynchronous. One of the main problems moving from streaming the data
+the audience is supposed to hear is that with no synchronous streaming, we would
+be unable to synchronize the audience in the same way radio stations are doing
+this.
+
+At the current time this is getting written, the link to the website 
+https://radio.arching-kaos.com will land you to the implementated idea we are
+here to talk about.
+
+While being analytical to this point, the solution to the problem won't be of
+the same degree of analysis. For this, a thesis paper is being developed but I
+am eager to share the news about it and talk about how the emulator works.
+
+Assume the pre-recorded shows and that these shows are played on after another
+on a radio station. If new content is not added, the list of these shows is
+repeated from the beggining.
+
+To make the asynchronous part, we need to have each show ready to be transfered
+to the audience. For convenience and for further expanding of the project, we
+would be having some metadata files, describing somethings about each show and,
+also, point the audience to the actual show. These metadata files, would need to
+let the audience about some key elements for later use. The most important parts
+are:
+1. date of publishing,
+2. duration,
+3. pointer to the show,
+4. the format of data that the show is stored in.
+The third and fourth parts are for the audience to be able to play the shows.
+The first and second ones, we will need them later for calculations.
+
+Now, think that these metadata files are referenced from another file that holds
+the list:
+of them, with to more elements:
+1. date and time of first appearance of this list and
+2. total duration of the list.
+
+To make the asynchronous, synchronous, we will need to calculate how much time
+has passed since the playlist started playing for the first time. Subtracting
+these two timestamps, we would get the number of seconds that have passed
+since.
+
+Timestamp(now) - Timestamp(playlist) = SecondsPassed
+
+Dividing the SecondsPassed with the total duration of the list we would now the
+times the list was fully played (the integer part of the outcome) and a ratio
+of how many seconds have passed since the latest start from the beggining of the
+list (the decimal part).
+
+SecondsPassed / TotalDuration = TimesFullyPlayed + K
+
+where TimesFullyPlayed is an integer/natural number
+
+K = SecondsPassedSinceLastStart / TotalDuration where 0<=K<1 which also means
+that SecondsPassedSinceLastStart > TotalDuration
+
+Finding the TimesFullyPlayed + K part would be easily calculated if for the
+ratio SecondsPassed/TotalDuration we would keep the integer part of the outcome
+and subtract it from the actual ratio. This would leave us with K which to
+convert back to seconds, we would multiply it by the TotalDuration which would
+be the amount of seconds passed since the last repeatition of the list.
+
+Knowing this amount of seconds, we would manage, knowing the durations of each
+show, to calculate which show is already played, which is not and which is the
+one that the audience is supposed to hear and the moment of tuning in.
+
+This part could be achieved by looking for each show in the list, effectively
+iterating until the point that the SecondsPassedSinceLastStart is greater than
+the summary of the durations, that we have already iterated in our process.
+When this condition is met, we get the current iterated show and load it.
+
+Finally, we sync on that show, by subtracting the summary of the previous shows'
+durations from the SecondsPassedSinceLastStart and we start playing the current
+show starting at the amount of seconds we just calculated.
+
+And we are back in synchronicity!
+