A fellow said "Yes, let you, my dearest friend, stream your screen to my screen." and in reply "What an excellent idea, do you know of a commonality in such a trivial matter?", and he was sure of it, absolutely so.

One program, which will not be named as to protect the authors from dogooders and the irrationally sane among us, was brought forth. In its execution, which was quick and shrimple, however I, considering myself a rather tepid and benign person, noticed that there was no configuration file on disk, perhaps after I installed it, it must be ran! So it was executed, and by my hand, again executed, lethally. However it was not dead, it was remained and alive even after I pkill'd it. Alas, I tended to my filesystem and noticed there was no mention of a configuration file, yet again. This was rather troubling. I checked the website, and there was no mention of such a file existing for this streaming daemon for which any person could intuitively point their OBS at and expect a video output at some URL or in directory. At this point, I became suspicious.

I opened the webpage yet again, to ensure that I hadn't made a simple halfblind mistake and realized something quite horrible: You would need to start the daemon, and utilize the program's !Web Interface! to configure the administrator details. This sent shivers down my spine and all the way down out of my ass requiring several hours of cleanup and heavy usage of desmellination agents. This would be no problem, I knew this from the moment the cubable cannable disgust passed, NGINX was set reverse proxy to the "locally" secured daemon hosted on a port 8080, a commonly utilized port which can not be changed on the command line or by the non-existent configuration file, it was simply a fact of the brilliant design set by these unclean web developers! Surely it would just work if it was so confined to not even need a configuration file, no?

I go to the website, I restricted it to only send and receive from my explicit IP, I quickly open to a half-rendered page - it's not setup, after all! The administration page ready to fix all the issues I see forth. It- Does- Not- Load. I C-C the browser, surely I'm the retarded one here! Half of the page loads perfectly fine, the HTML, one or two images! All the Javascrit, has seemed to have gone missing! Perhaps I thought, if I had braved my way through this shit, it could create a file on disk that would let me use Emacs text editing instead of Emacs web browser, but no. The webdeveloper laughs in his hellish palace knowing that yet again the first result from Google or Sir GPT has convinced some poor fool that this was well and truly the first pick and most supported and intuitive option out there yet! At this point, I became unsure of this tool's legitimacy, and so I vaporized it from my server.

There was Docker version. I would have to clone another man's used devirginated computer, to run a program for streaming, which certainly can be accomplished in a single python script, as any fine Paedophile would tell you. Let it be known, I did not use Docker, and ideally never ever ever will. I also doubt that it would work, because the developers were obviously beyond Jeetscrit retarded.

The next, logical step would be go off of my fine fellow's advice, "NGINX has a way to do it I think, here's a link to the documentation, I'm gonna go take a shit and be back in ten or so," he shocked me into action, checking and reading at a below average speed, I managed to comprehend so much as to copy some commands into my server, as any good serverowner does. Alas, the Debian package advised could not be received, perhaps it is only Bullseye, or perhaps it misparsed by distribution in the command? Thusly, I realized, it was not so accessible. Reading, at the same speed, but with more reading comprehension than before, I noted that it, NGINX, was not pushing me to download a privately handled upstream variation of NGINX, but a Paid Subscription. I should have known the moment I reading comprehensioned the word "PLUS"! I was fooled and I was certainly a fool for it. I cast myself away.

In any such event, one must console oneself and find peace, so I went to my digital pastor, Jean. P. Tomlinson, and inquired about such things as streaming. Here is where I learned of rtmp, a thingy (this is a technical word used by technical people, do not mistake it for the common dumbasses way to refer to things he doesn't know the name of because he's a retard/dumbass/dumbfuck/know nothing loser) that enables you to stream to it and then that will appear as a set of files or something (common technical wording, per. Saar P.) that can then be viewed as a real time video stream locally. Howeverso, I found out that I must also setup HLS, this was simple, and done very quickly. After all this nonsense, streaming was a breeze, however the latency was quite extreme. DASH is a higher-speed alternative to HLS. That worked very simply. I also read that WebRTC exists for this purpose but I didn't feel like setting it up.

After the fact, streaming was successful, on HLS, > 15 second delay, on DASH, ~ 10 second delay, overall, this was almost acceptable. Ideally I could reach realtime speeds that even a retarded (technical relative term) Paedophilic Python/Batch Programmer could with peertopeer screen sharing. Alas, he died of AIDS probably, and can no longer clean up this shit. Audio, was another problem. In OBS it takes more than three seconds (technical time intervals used among web developers, troons, chuds, etc.) to figure out how to capture audio from a particular window so we just didn't, the most classical solution.

Overall, streaming wasn't excessively painful, however I did experience excessive amounts of pain due to filthy web developers, NGINX (which is derived from Apache, no wonder why it's so tiresome), and my shear inability to look things up for OBS.

"Surely," "Naturally," "It's broken" "I know.", Of course.

I hate Dovecot.

I HATE Dovecot. if the word HATE was inscribed on every Dovecot developers peeled and pressed skull it would not pile to be high enough to even pretend to be one one billionth the mountainrange of hate I feel for Dovecot developers whenever I glare into the configuration files bloodied guts. HATE. HATE. Etc. So I upgraded Debian (this is the start of a practical joke on me), ten thousand questions which I took plenty of time to look through and make the best decision on. Thereafter I noticed something strange, my mail was pinging out, presumably everything's broken because I've yet to restart the server. Reboot, everything seems fine, issue persists. Restart dovecot, it doesn't work. Check the logs: "lol lmao dude, the configuration needs a new line to specify the version of the configuration for backwards compatibility, man." I, as man obligated to serve the Machine God, do as I am told. Thereafter I restart, it seems it has a new complaint. The first thing I tried, after I set the version, was the assumption, "I'll set the prior version and be done." This would turn out to be utterly pointless and nothing changed. I had to update the entire file whether I liked it or not.

This continues. For a long time. It, Dovecot, does not do a general dump of all the problems at once so that larger or repeat issues can be solved at once, it simply finds a problem, and dies. Over, and over again. Perhaps I'm retarded and there's a way to do a configuration check with an option that does this, but it's not in the default runnings so fuck me I suppose. Programs were never designed to be used by people. After many many pointless stupid changes, I finished it off and it was up again, having suffered for no good reason. Perhaps I was retarded and set the wrong prior version, alas, there was no information for me to go on. Many of the changes to the configuration were simply renaming variables. Some were outright redesigns. This could of all been in parallel to the prior names and implementations, but they decided to deliberately and maliciously exhume my configuration from its eternal rest in the casket of prehistoric versions.

Sick fucks.

I updated Bake on 9/11.

Bake is now slightly better featuring the -q option and not including the -c option (replaced with https://no-color.org/). It only outputs to stderr. subprograms continue to output whatever they want whereever they want to.

©opyright Emil $CURRENT_YEAR Public Domain