Update SECURITY.md#614
Conversation
Security vulnerability of single point of failure. Why you store home addresses and sensitive data of engineers on GitHub in open source? Those engineers operates billion dollars of money, idiots. You are monkeys.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a large amount of unrelated, philosophical text concerning algorithms, video rendering, and magnetic relay logic into the SECURITY.md file. The reviewer correctly points out that this content is completely irrelevant to the repository's security policy and vulnerability reporting guidelines, and recommends removing it entirely to maintain professional and clear documentation.
| https://transitional-writes.dreamwidth.org/52172.html | ||
|
|
||
| Basically the idea is that exist program that render picture that you see | ||
| in the front of you. | ||
| There is a sequence of programs that render every frame that you see in the front of you. | ||
| This is the formal spec for a program for memoirs of every software engineer. | ||
|
|
||
| Are you software engineer or not? | ||
| That could be the beginning of the lectures on algorithm theory and inductive logic. | ||
| Is it right? | ||
|
|
||
| Something strange. | ||
| Is there difference between russian and english? | ||
|
|
||
| Let's try to describe it in english. | ||
| Maybe it can help in understanding. | ||
|
|
||
| There is a set of all procedures (algorithms) that generates all possible | ||
| frame streams from IP cameras. | ||
| That could be C programs, OpenGL shaders or POVRay scripts for example. | ||
| Self extracting ZIP files and H264 encoded movies with attached decoder are | ||
| also useful. | ||
|
|
||
| Each movie has its own backstage. That IP camera is attached (maybe virtually) to one person. | ||
| There are 7 999 999 999 other persons on Earth. You don't see their records. | ||
|
|
||
| What you really see (your IP camera see) acts as xdelta utility. | ||
| Movies that are rejected frame by frame by this xdelta application are | ||
| removed from the infinite set. | ||
| The real set that is operated by human is really simple and maybe finite of course. | ||
|
|
||
| Then shorter that procedure that generates video stream - then more probable this scenario is. | ||
|
|
||
| Looks like english version is shorter and more procedural. | ||
| It looks more like a program that I describe. | ||
| Maybe it is an ancestry from latin language? | ||
|
|
||
| Maybe it's just a game but it is very simple game. | ||
|
|
||
| There is an infinite set of all procedures that generates all IPcam movies. | ||
|
|
||
| There is an xdelta procedure that cut all movies that don't appear on IPcam | ||
| that is attached to you. | ||
|
|
||
| There are other 7 999 999 999 persons on Earth. | ||
|
|
||
| Then shorter is the procedure in the infinite set then more probable associated movie is. | ||
|
|
||
| That's it. | ||
|
|
||
| There is an infinite set of all procedures that generates all IPcam movies. | ||
|
|
||
| but all that procedures are not black boxes in general. | ||
| we can extract some subprocedures. | ||
| physics for example. | ||
|
|
||
| but what are the other elementary subprocedures? | ||
|
|
||
| procedural hypno? | ||
| how to generate it? | ||
| is it the basis of modern LLMs? | ||
|
|
||
|
|
||
| It seems for the safety reason we have to switch on the magnetic relay logic. | ||
| All other ways are leading to the situation when criminal is heading toward | ||
| GNU FTP mirrors, Java maven mirrors, GitHub source code of LLM models and enginners home addresses. | ||
|
|
||
| Magnetic relay logic ladies and gentlemens! |
There was a problem hiding this comment.
The added text is unrelated to the repository's security policy and vulnerability reporting guidelines. A SECURITY.md file should remain focused on providing clear instructions for reporting security vulnerabilities. It is recommended to remove this section entirely to maintain professional and clear documentation.
1 participant
Security vulnerability of single point of failure. Why you store home addresses and sensitive data of engineers on GitHub in open source? Those engineers operates billion dollars of money, idiots. You are monkeys.