Error 666: Software does not exist yet - exiting
This crash was annoying so many people - finally BMD did something about it!
184 karma · joined April 26, 2022
Error 666: Software does not exist yet - exiting
This crash was annoying so many people - finally BMD did something about it!
"On 2022-02-14, we decided to abandon the current path of using X11/KDE desktop components and write from scratch a new UI that will align better with our goals."
Do you have a good QA for incoming components? If yes, you will see a pattern.
In any case, you need throttling / DDOS protection or a similar mechanism that will stop video download when you get too many requests - this risk is very real and when you can not stop some bot downloading videos a trillion times you can be killed financially in one day.
This must be implemented in some hard technical limitation on the server / service provider site and should not be some soft agreement like e.g. "we will find a solution, just go ahead".
Also very important is to implement all video streaming costs in a pre-paid fashion - put the max amount of money you are ready to pay for monthly delivery into the account in advance, but make absolutely sure that delivery stops when that money is burned. It is better to be offline for some while (or deliver some reduced quality content that is much less traffic intensive) than to go broke in one night.
But you do not only have to prepare for abuse and errors, you also have to see that in the long run, when the number of subscribers get bigger and bigger, you need a good solution to guarantee that the ongoing downloads of (old) subscribers will not accumulate to astronomical numbers - we could speak of an "inverted long tail" here that will eat more and more money. Plan ahead!
There are many more problems with selling video content and this was just a small introduction, but contained the most important points.
Sometimes it turns out that it will be a much safer solution to NOT sell the video content but sell additional services around your videos - put your videos on YT, forget about all problems with video hosting and focus on selling many much less intense products and services, while your videos generate lots of subscribers, because you will never deliver to as many people as YT can.
Good luck!
This one looks interesting: https://github.com/emcrisostomo/fswatch
Question 2: does exist some kind of optimization-per-usecase service for such a fixed cost scenario? E.g. "Optimize for Website" or "Optimize for Database" and you can download a Terraform file?
Also you should give some advice about how to deploy when the default for deploying apps in an organization is K8S, what might be not too exotic nowadays. Will Plane need it´s own cluster? Does it run on top of K8S? How is the relation to K8S in general for a deployment scenario?
THANKS!
All printing workflows use proprietary formats as input and bind you to one tool or producer. Could Scribus help with that?
See recent success for "Sweden Democrats" and take a look at the votes in Italy next week.
Also you have to always remember that Ursula von der Leyen could only get into her position with the help of the vote of far right - she will never be against far right for that reason alone.
There is a huge theater going on re "european values" - this is not reflected by reality. E.g. the current "measures" taken against Hungary are seen as a joke.
We, as Hacker community, need to speak up - these practices must be stopped.
A very interesting series of articles would be "How to take down your K8S cluster" describing the many ways a cluster can be [mis]configured to easily be brought down by one single error / pod / application.
It would be great if you took some time to write about the question of climate change and energy waste.
In this regard it would be very interesting to better understand the impact tools like K8S have on global warming. Just from a pure practical POV I see many clusters burning a lot of CPU cycles with K8S processes that do nothing else than providing some kind of infrastructure for the real computing task.
I have seen K8S burning 50% and more CPU time - this with not one single payload operation, just doing its cluster thing!
This is a horrible waste of energy and we can not go ahead establishing such a bloated monstrosity as default data center OS of the future.
Not all data centers are 100% solar - I guess people in the field are LOL at this point knowing the realities. So I personally come to the conclusion that a thing like K8S is the opposite of what is needed in a world that is heading to a climate disaster. So many hours spent into optimizing the Linux kernel (successfully!) are nullified by a tool that wastes energy recklessly.
We need more than one article to help programmers of these tools understand why they should do their jobs with more love for future generations.
Also we need lots of articles about how to write efficient code that does not waste CPU cycles.
It would be great if you would like to finish the work on this project and make it part of the Caddy default distribution.
Honestly I do not understand how people run high-traffic sites without rate limiting. [D]DOS attacks and other misuse (e.g. spambots etc.) are daily issues on the internet, do you just ignore that?
How do you know how many requests are silently lost?
I would like to read more about how reliability is actually measured on high-traffic sites.
As developer and systems engineer you should have been aware of that before starting your work. Now you are chained to the Windoes world and real computing environments are out of reach for your project.
As a first hint also read this:
https://revealnews.org/article/private-report-shows-how-amaz...
"Correction - The figure ‘Too close for comfort’ in this Comment incorrectly synthesized and interpreted information from the IPCC. The graph labelled the temperatures as absolute, rather than rises; misrepresented the levels of risk; misinterpreted information as coming from a 2007 IPCC report; extrapolated the focus of a 2018 report; and was not clear about the specific sources of the information. The graphic has been extensively modified online to correct these errors."
This is a top level publication, an article by the leading scientists in the field of climate change. It is so frustrating to see these errors happening on that level. One such little error generates more damage than 100 fake reports produced by the oil industry. Very sad.