OSINT: Smarmy Gorilla Niggers SoundPost - Sound off since you retard nigs can't flame right or read.

Why did you visit this thread?

  • Be a Gorilla Nigger

    Votes: 3 100.0%
  • Show up the useless retards to be even more retarded

    Votes: 0 0.0%
  • OSINT About Gorilla Niggers is a good investment?

    Votes: 0 0.0%

  • Total voters
    3

Chad Nasty

Optimus Faggot
True & Honest Fan
kiwifarms.net
Joined
Jan 8, 2019
I tried, not one single person could even question my stack, sticker queens like @Dialtone, useless bottom-bitches like @malt ipecac.

I've found it more enjoyable to mog you fat fucks than to try and spread knowledge.
You've all been absolute UNITS with peacocking how you're hot garbage. So keep on with it bby.

Keeping the repo, not care an example of what to do, but because ya'll fit right in.

The Glowing East German Secret Police Nervous System. Great.

Either you don't know what "facet" means or I don't.

Are you trying to grift money from the government or start a business? Do you consider a person who receives disability payments from the government to be engaged in business?

This objective seems orthogonal to your stated end goal (see below).

On which: could you rephrase this? That just doesn't make sense as it's written.
Fair enough.


I'm not asking to be a dick, but is English your first language?

As that definition states, "facet" is typically used as a synonym for "aspect" or "part". Here is what I think you're trying to communicate:
  • Your target customer is the DoD.
  • One facet (you could also say "part" or "aspect", for example) of your plan is to provide training to veterans as an alternative to college/trade school/shitty jobs.
  • Another facet (again, you could replace "facet" with "part" or "aspect") of your plan is to build this "nervous system".
It's the connection between these two facets that isn't clear to me. Is your plan to train these veterans to build this nervous system?


If you aren't trying to deceive or trick anyone, this isn't really a grift. It would be a grift if your plan were to trick the the government into paying you by dazzling them buzzwords or to trick the government into paying you upfront and then disappearing.



I'm still not sure what you mean by this, definitionally or conceptually.



It sounds like what you're getting at is the distinction between "strategy and tactics" or "objectives and implementations", which is one I understand and agree is important. Keep in mind, however, that you should expect to have an easier time explaining this all to me than jarheads and g-men. I still don't get it.

In the spirit of FOSS, I figured I should post a text version of your ethos statement so the curious don't have to bother with DMing you.

GLOSTASI ICARIAN ETHOS

What is the ‘Icarian Ethos’?
It is a reference to the story of Icarus in Greek mythology, an allegory of the consequences of “complacency and then of hubris”. What is usually taught with the story us neither fly too or too low. General, well accepted advice for general purposes. We aren’t general. The tale of Icarus in our conceptualization of is different. Man must test the limits to push onward into the future. Flying close to the sun is the only pathway to push the limits of our reality and out ability to interact with it. We ask not if we can, rather are we willing? Challenging personal incredulity is the only way to reach new heights. Prove incapability, not accept it as fact means untested. We look to better educate by utilizing conceptualization through practical experience. Open source and project-based learning is the most effectual and long-standing method to teach. We are an apprenticeship for the modern world. We operate under the following ideas:
  • We are tradesmen.
  • We fail upwards.
OUR APPROACH TO SYSTEM DEVELOPMENT AS AN ENTITY
  1. We break down our problem from top down and enforce README Driven Developmentinitial stages.
    • We don’t build the house if we don’t know what it looks like. To properly handle a problem, we must fully understand what the problem it. What is it? What does it mean? How will the near future impact it? Why is it a problem? Granulated detail about the Why/What/When/Where before asking ourselves: How?
    • We don’t use tools If we can’t explain their necessity. Technology adaptation under the auspices of “Google is doing it” is not a sound reasoning for architectural technology choices.
  2. We eat our Wheaties.
    • Criticism, and harsh criticism of our ideas is not an attack on the individual’s capability. It’s a gift from someone who took the time to find the holes in their idea so we can make it better. Pride and pedigree mean nothing here.. Keeping ourselves in check is ground up and top down Being a leader isn’t a title of self-importance, it is of overall importance.
    • If you’re the smartest man in the room, its time to find a new room. Never aim to be the best at a singular service, always find a next challenge. Be humble and focus on the idea and not the person delineating it.
    • We take breaks.
  3. We Learn Concepts Over Definitions
    • What have wrenches, we call them wrenches. The important knowledge about the wrench it’s utility. Same for our tech stacks. We know how to use our tools and bring the right ones to the job.
    • We work to engineer under the following concepts:
      1. Make it decoupled: Such as the wrench and the hammer are separate entities, so will the systems we build.
      2. Containerize it: A wrench fits a bolt. Our systems and subsystems are idealistically different wrenches to fit the bolts we fasten for the system.
      3. Archive all of it: When we build we in tandem document and archive our source material. We always have a paper trail for precedence and for reference,
      4. Make it scale: Planned obsolescence in our conceptualization is the lifetime the scale of our current system. We plan for it and code reusability is important. This is also why we don’t start until we understand what we want to accomplish,
      5. Make it simple: Simple and clean engineering is the best engineering. We don’t bring a skid-steer loader to garden a small plot, we don’t bring a trowel to move earth for a building. Over-engineering is bad engineering.
WHERE ARE WE GOING?

We are moving onward into the abyss. There is no better way to put it. We look for uncharted waters, chart them then find the next challenge. Every project we do aims to be a training path for people to learn, and more importantly be able to create. The training paths are meant to challenge, meant to take time and meant to give you the gift of knowledge through experience, not textbook. We have no NDA’s because our company secret is an open book. The environment we cultivate is what produces the best results, not our secret algorithms.

Last, we are embracing freedom of expression and are politically agnostic. Ideas can come in many forms and have different nomenclature. To police thought to impose our will over the agency and creative outlets our organization. Agency over our thoughts and ability to express them as we are is priority. Learn to handle the tides, don’t change them to fit your schedule. We build people to endure the nature of the world, not build a fortress for people to hide from is.

A. GLOWS
DRIVER OF THE STRUGGLE BUS, GLOSTASI

Thank you for the constructive criticism. I think that's what I needed: tough love. Anyway, I'm back and want to learn how to be useful, but I have a question about an edit you recently made to one of your posts.


Which state governments have you been corresponding with? And who are you talking to in the federal system?

It would be extremely impressive if this were all true, but I'm still skeptical. Could you post an example or two of this archived correspondence? Redacting names, of course.
Ok, I see what's going on here. You're breaking me down before you build me back up, stronger than before. This is just like the part of Fight Club where Tyler Durden yells at the prospective ephebe about how he isn't good enough and makes him wait outside the house.

It's okay that you're uncomfortable sharing your correspondence. We can move on to the next step when you're ready.

I can tell you're becoming frustrated with me, and that's okay. I see now that I've made an ass of myself and thrown away whatever credibility I may have had -- all because I wanted to be a fag. Makes me want to vomit.
Are you challenging me to a code-off?
Why do you edit your replies so often after you post them?

Before starting some basic tensorflow machine language transforms, I'd really like to see some proof of your government correspondence.
You guys can't do shit, not worth the effort, have 0 aptitude. So here's my new open source venture "Suck My Ass". And I'll open repo to you all can com and contribute to licking the shit stains off my coin-slot.

To those who did reach out, I'll keep you updated and make sure that you're in a good spot when you graduate or are retraining.

So sperg out. I changed to thread to fit you women: incompetent, lazy, no character and retarded candy ass attitude.
You are wreak of beta cum sluts too.

All the best, ladies.
HMU when you blow the sand out your vag and actually want to do something.
Snapchat-1792176652.jpg
 
Last edited:
Hire me if you need a Django dev. I'm Russian so you get white person code for pajeet rates.

(I've started my own tech company three years ago. I'm still miraculously afloat despite covid and sanctions but all I'm doing is unprofitable side projects of a DBA CTO, the funding coming from the soul sucking fortune 500 work his company does.)
 
It's all fun and games until your payment processor or bank cuts you off.
>assuming they're doing one of those "free speech" tech sites like Gab or Bitchute
ISHYGDDT
 
I have absolutely no interest in producing a 'technology company' per se, when I start a company I want to start a company for the purpose of accomplishing specific things not 'well we're a tech company lets write some code and see what happens'. If what I want to accomplish would benefit from code, that code will be written, anything else creates pointless zombie companies funded by random venture capital firms that don't understand business that go round in circles producing jack shit and wasting everyone's time or being an active detriment to society.
 
Im making tiktok but for liveleaks
It just skips to the funny parts where they get zapped or the chinaman in the factory dies. LOL.

Fuck, that might actually be worth doing.
 
  • Thunk-Provoking
Reactions: Clown College
It's all fun and games until your payment processor or bank cuts you off.
Payment for what? prime example of lack any critical thinking.
Thought about it, keep niggin bro, get the gibsl,

@ZombiefiedFerret I gotta know how intelligent you must be to make sure you mark everything as autistic in my thread. Lemme hear your hot take, don't be shy buddy.
 
Last edited:
I have absolutely no interest in producing a 'technology company' per se, when I start a company I want to start a company for the purpose of accomplishing specific things not 'well we're a tech company lets write some code and see what happens'. If what I want to accomplish would benefit from code, that code will be written, anything else creates pointless zombie companies funded by random venture capital firms that don't understand business that go round in circles producing jack shit and wasting everyone's time or being an active detriment to society.

Not exactly. These firms are often based in, or exposed to, CHYYYYYYYYNA. Locust investors are either raiding IP a la Disney or EA or just looking for an excuse to build properties (read: capital flight from the People's Republic or money laundering) or for mediocre family members to get visas and green cards.
 
  • Agree
Reactions: SickNastyBastard
Not exactly. These firms are often based in, or exposed to, CHYYYYYYYYNA. Locust investors are either raiding IP a la Disney or EA or just looking for an excuse to build properties (read: capital flight from the People's Republic or money laundering) or for mediocre family members to get visas and green cards.
This is a problem, one we can fix. I'm doing something cool. Smarmy bitches hate that.
 
Last edited:
SickNastyBastard said:
Company: GloStasi Nervous System
The Glowing East German Secret Police Nervous System. Great.
SickNastyBastard said:
Facet for development: Defense Department
Either you don't know what "facet" means or I don't.
SickNastyBastard said:
I've attached the sent business proposal to the fed hoping to grift some shit, its anon edited.
Are you trying to grift money from the government or start a business? Do you consider a person who receives disability payments from the government to be engaged in business?
SickNastyBastard said:
The objective of the company is give people the tools to do build insane and cool shit.
This objective seems orthogonal to your stated end goal (see below).
SickNastyBastard said:
My end goal is to create a "Nervous System" for the world utilizing wide band em spectrum analysis and a discretized process of pipelines with dynamic requirements and an intelligent pipeline which shows real-time jamming spots. I establish a "hive-mind" swarm as a means of info production decoupled from the process itself as a means to monitor or regulate better areas.
On which: could you rephrase this? That just doesn't make sense as it's written.
 
  • Autistic
Reactions: Dialtone
Make it simple: Simple and clean engineering is the best engineering. We don’t bring a skid-steer loader to garden a
small plot, we don’t bring a trowel to move earth for a building. Over-engineering is bad engineering.

Containerize it

Good luck, Chuck.

Oh, also:
The Icarian Ethos
We fail upwards

You do know how the story of Icarus ends, right? :lol:
 
Last edited:
  • Winner
Reactions: Yotsubaaa
Thank you for the feedback, here is my rationale.

The Glowing East German Secret Police Nervous System. Great.
What do you think the system that collects intelligence in areas to categorize people into threat assessment categories sound like? Secret police. I'm not dressing it up,

Either you don't know what "facet" means or I don't.

- "any of the definable aspects that make up a subject (as of contemplation) or an object (as of consideration)"
The make up the subject would be for the DoD, the project is defined and geared towards defense, hence the MOUT Ops references. What would be preferable?

Are you trying to grift money from the government or start a business? Do you consider a person who receives disability payments from the government to be engaged in business?

I wrote in an earlier post that the project was initially a concept to try and establish a training path for veterans who were in combat arms to get skills and practical experience, ground to sky, in an environment better suited to for them. It unfortunately has to become a company in which then I can sell back the training path to the government. It's a "unwanted" type of grift because now I am in the process of getting money for a project I would have done freely to sell back to the government what I told them I would give them freely. So, its a grift.

This objective seems orthogonal to your stated end goal (see below).

On which: could you rephrase this? That just doesn't make sense as it's written.

For the first point, the project is a ground to sky covering of software. From binary gates to advanced AI. You're looking at the project through the lense of definitions rather than concepts. I chose this because it will teach important concepts, not systems. It does not matter that I am using Apache Beam, it matters to understand a data orchestration pipeline. It does not matter that I use Cassandra as a warehouse, it matters to understand how the warehouse functions. All of these concepts are taught in a practical use case with a system as a whole rather than individualised areas.

Second: Your nervous system it truly general utility if you look at all the subsystems and complex processes that it carries out. Our body, brain to be more precise, has a latent understand of what our nervous system is saying and how to respond to the signals.
That, in essence is the goal and why I chose the nomenclature. Building out a 'Nervous System' is essentially the same concept. We want to be able to monitor, quantify and have a latent understanding of what happens and either react by will or have it dealt with automatically.

I hope that helps
 
  • Autistic
Reactions: Dialtone
Good luck, Chuck.

Oh, also:



You do know how the story of Icarus ends, right? :lol:
If you read the ethos, you'd also see the point of it. I defined exactly why. You have to push your limits to find how to break them. You may be completely content with stagnation and making REST apps, I'm rather not. I'm not that lazy.

Containerizing it? Good luck? Its not that hard. You don't need a master's degree for kubernetes, money grip

@Dialtone go learn how to read documentation. I don't know how retarded you are, but big platforms like the ones I'm using work in docker container images which can get deployed in k8 cluster. I doubt you know how lean flat-files or csv's are are. Too bad you can't understand my tech choices.
 
Last edited:
  • Mad at the Internet
Reactions: Dialtone
What do you think the system that collects intelligence in areas to categorize people into threat assessment categories sound like? Secret police. I'm not dressing it up,
Fair enough.

- "any of the definable aspects that make up a subject (as of contemplation) or an object (as of consideration)"
The make up the subject would be for the DoD, the project is defined and geared towards defense, hence the MOUT Ops references. What would be preferable?
I'm not asking to be a dick, but is English your first language?

As that definition states, "facet" is typically used as a synonym for "aspect" or "part". Here is what I think you're trying to communicate:
  • Your target customer is the DoD.
  • One facet (you could also say "part" or "aspect", for example) of your plan is to provide training to veterans as an alternative to college/trade school/shitty jobs.
  • Another facet (again, you could replace "facet" with "part" or "aspect") of your plan is to build this "nervous system".
It's the connection between these two facets that isn't clear to me. Is your plan to train these veterans to build this nervous system?

I wrote in an earlier post that the project was initially a concept to try and establish a training path for veterans who were in combat arms to get skills and practical experience, ground to sky, in an environment better suited to for them. It unfortunately has to become a company in which then I can sell back the training path to the government. It's a "unwanted" type of grift because now I am in the process of getting money for a project I would have done freely to sell back to the government what I told them I would give them freely. So, its a grift.
If you aren't trying to deceive or trick anyone, this isn't really a grift. It would be a grift if your plan were to trick the the government into paying you by dazzling them buzzwords or to trick the government into paying you upfront and then disappearing.


For the first point, the project is a ground to sky covering of software. From binary gates to advanced AI.
I'm still not sure what you mean by this, definitionally or conceptually.


You're looking at the project through the lense of definitions rather than concepts. I chose this because it will teach important concepts, not systems. It does not matter that I am using Apache Beam, it matters to understand a data orchestration pipeline. It does not matter that I use Cassandra as a warehouse, it matters to understand how the warehouse functions. All of these concepts are taught in a practical use case with a system as a whole rather than individualised areas.
It sounds like what you're getting at is the distinction between "strategy and tactics" or "objectives and implementations", which is one I understand and agree is important. Keep in mind, however, that you should expect to have an easier time explaining this all to me than jarheads and g-men. I still don't get it.
 
  • Autistic
Reactions: Dialtone
Fair enough.


I'm not asking to be a dick, but is English your first language?

As that definition states, "facet" is typically used as a synonym for "aspect" or "part". Here is what I think you're trying to communicate:
  • Your target customer is the DoD.
  • One facet (you could also say "part" or "aspect", for example) of your plan is to provide training to veterans as an alternative to college/trade school/shitty jobs.
  • Another facet (again, you could replace "facet" with "part" or "aspect") of your plan is to build this "nervous system".
It's the connection between these two facets that isn't clear to me. Is your plan to train these veterans to build this nervous system?


If you aren't trying to deceive or trick anyone, this isn't really a grift. It would be a grift if your plan were to trick the the government into paying you by dazzling them buzzwords or to trick the government into paying you upfront and then disappearing.

You have know clue what you are talking about and @DialtoneTone giving mass stickers. Yup, nothing of any value.
 
Last edited:
My startups' business model is like, uber for shitposts. Where do I have to go to receive my million dollars
 
My startups' business model is like, uber for shitposts. Where do I have to go to receive my million dollars
Try filming yourself fisting your asshole deep and email it to the FCC. Then cunt punch your mom for being retarded.

I gotta ask, how old are you? I'm pegging you as a 20-something.
My money is that your fat and out of shape too.
The low tier sarcasm is pretty telling you don't have much going for you, so my project wouldn't be a good fit.

In fact, since you likely wont reach a point to ever contribute value, you'd best serve as a cock sleeve for capable men. That's your million dollar path: brutal butt fucking for cheeto money.
 
Last edited:
In the spirit of FOSS, I figured I should post a text version of your ethos statement so the curious don't have to bother with DMing you.

GLOSTASI ICARIAN ETHOS

What is the ‘Icarian Ethos’?
It is a reference to the story of Icarus in Greek mythology, an allegory of the consequences of “complacency and then of hubris”. What is usually taught with the story us neither fly too or too low. General, well accepted advice for general purposes. We aren’t general. The tale of Icarus in our conceptualization of is different. Man must test the limits to push onward into the future. Flying close to the sun is the only pathway to push the limits of our reality and out ability to interact with it. We ask not if we can, rather are we willing? Challenging personal incredulity is the only way to reach new heights. Prove incapability, not accept it as fact means untested. We look to better educate by utilizing conceptualization through practical experience. Open source and project-based learning is the most effectual and long-standing method to teach. We are an apprenticeship for the modern world. We operate under the following ideas:
  • We are tradesmen.
  • We fail upwards.
OUR APPROACH TO SYSTEM DEVELOPMENT AS AN ENTITY
  1. We break down our problem from top down and enforce README Driven Developmentinitial stages.
    • We don’t build the house if we don’t know what it looks like. To properly handle a problem, we must fully understand what the problem it. What is it? What does it mean? How will the near future impact it? Why is it a problem? Granulated detail about the Why/What/When/Where before asking ourselves: How?
    • We don’t use tools If we can’t explain their necessity. Technology adaptation under the auspices of “Google is doing it” is not a sound reasoning for architectural technology choices.
  2. We eat our Wheaties.
    • Criticism, and harsh criticism of our ideas is not an attack on the individual’s capability. It’s a gift from someone who took the time to find the holes in their idea so we can make it better. Pride and pedigree mean nothing here.. Keeping ourselves in check is ground up and top down Being a leader isn’t a title of self-importance, it is of overall importance.
    • If you’re the smartest man in the room, its time to find a new room. Never aim to be the best at a singular service, always find a next challenge. Be humble and focus on the idea and not the person delineating it.
    • We take breaks.
  3. We Learn Concepts Over Definitions
    • What have wrenches, we call them wrenches. The important knowledge about the wrench it’s utility. Same for our tech stacks. We know how to use our tools and bring the right ones to the job.
    • We work to engineer under the following concepts:
      1. Make it decoupled: Such as the wrench and the hammer are separate entities, so will the systems we build.
      2. Containerize it: A wrench fits a bolt. Our systems and subsystems are idealistically different wrenches to fit the bolts we fasten for the system.
      3. Archive all of it: When we build we in tandem document and archive our source material. We always have a paper trail for precedence and for reference,
      4. Make it scale: Planned obsolescence in our conceptualization is the lifetime the scale of our current system. We plan for it and code reusability is important. This is also why we don’t start until we understand what we want to accomplish,
      5. Make it simple: Simple and clean engineering is the best engineering. We don’t bring a skid-steer loader to garden a small plot, we don’t bring a trowel to move earth for a building. Over-engineering is bad engineering.
WHERE ARE WE GOING?

We are moving onward into the abyss. There is no better way to put it. We look for uncharted waters, chart them then find the next challenge. Every project we do aims to be a training path for people to learn, and more importantly be able to create. The training paths are meant to challenge, meant to take time and meant to give you the gift of knowledge through experience, not textbook. We have no NDA’s because our company secret is an open book. The environment we cultivate is what produces the best results, not our secret algorithms.

Last, we are embracing freedom of expression and are politically agnostic. Ideas can come in many forms and have different nomenclature. To police thought to impose our will over the agency and creative outlets our organization. Agency over our thoughts and ability to express them as we are is priority. Learn to handle the tides, don’t change them to fit your schedule. We build people to endure the nature of the world, not build a fortress for people to hide from is.

A. GLOWS
DRIVER OF THE STRUGGLE BUS, GLOSTASI
 
Back