Principia Discordia

Principia Discordia => Think for Yourself, Schmuck! => Topic started by: ivan on March 24, 2015, 07:46:57 AM

Title: Source code
Post by: ivan on March 24, 2015, 07:46:57 AM
There is no government, no industrial-military complex, no economic system, no mass media that can ever reduce us to puppets and robots as thoroughly as the biological and enviornmnetal dictatorships have - F.M. Esfandiary (FM-2030 (https://en.wikipedia.org/wiki/FM-2030)), Upwingers

Hello friends! In this post, I will tell you about a model that someone can possibly find an effective instrument of social interaction. And in order to get used to this model, we must first discuss some concepts related to the field of information technology.

The computer software is:
A program (from Greek programma, "a written public notice") – in computer science, this is a set of instructions intended for execution by a machine. In general, we call a program some application provided with a user interface (https://en.wikipedia.org/wiki/User_interface).
A process (https://en.wikipedia.org/wiki/Process_%28computing%29) – typically, this means a program that lacks any graphical user interface, while repeatedly accessing the physical memory and hardware resources, and performs some operations in the background mode.
An operation system (https://en.wikipedia.org/wiki/Operating_system) – a computer's main program that defines the scope and the procedures for running all other programs and processes.

Hereon, we need to consider the following two kinds of operation systems:
A proprietary system (https://en.wikipedia.org/wiki/Proprietary_software) (from Medieval Latin proprietarius, "owner of property") – this is a system developed and distributed by a specific proprietor (e.g., Apple or Microsoft). The source code of a proprietary system is sealed and inaccessible to anyone, except for the proprietor itself.
An open-source system (https://en.wikipedia.org/wiki/Open_source_hardware) – it is available for public access, does not belong to anyone, has all its source code accessible and open to change.

It is also worth mentioning that there are two levels in an operation system:
The user level – this includes a conventional desktop, end-user applications, the input and output of data via the graphical interface. A user is allowed to install, run and restrict the access to resources for programs to which he or she has access.
The core, kernel (heart) level (https://en.wikipedia.org/wiki/Kernel_%28operating_system%29) – this level is unavailable to a user, it typically lacks any visual representation and hosts a multitude of system processes. In proprietary systems, only the owner has access to the core level, while in open-source systems this may be a special user granted with extended authority, named Root (https://en.wikipedia.org/wiki/Superuser). We have almost finished explaining the terminology by now...

So, in proprietary systems, background processes that consume the processor resources and physical memory are called "Services (https://en.wikipedia.org/wiki/Windows_service)":

(http://is3.soundragon.su/wp-content/uploads/image002.jpg) (https://en.wikipedia.org/wiki/Windows_service)

Meanwhile, in the proprietary systems users do not have access to the core services. A user cannot reduce the consumption of resources, release the memory or disable a system service; only the proprietor can gain the access to core services.

Now, in the open-source systems, the background processes that consume the processor resources and the physical memory are called "Daemons (https://en.wikipedia.org/wiki/Daemon_%28computing%29)":

(http://is3.soundragon.su/wp-content/uploads/image001.jpg) (https://en.wikipedia.org/wiki/Daemon_%28computing%29)

If a user of an open-source system knows the Root password (of a super-user), he or she becomes enabled to kill/freeze any daemon, limit its consumption of resources and memory, and even reassemble the core with applying to it the necessary custom settings.

And finally, let's take a look at an effective model:

Replace the "computer software" at the beginning of this post with "bio-computer software" and read the article anew. Next, try to answer the following questions:

   are you authorized to command the core of your biocomputer?
   is the source-code of your system open, or is it locked by a proprietor behind seven seals?
   how many services/daemons must be attended by your biological hardware every day? Do their actions cost you memory and resources?
   who is the specific proprietor of your services: parents, professors, priests, officers, mates, or somebody else?
   would you like to obtain the Root password enabling you to personally exercise control over your own heart daemons, or would you rather like to continue relying upon the proprietor services?

Links:
J.C. Lilly. Programming and Metaprogramming in the Human Biocomputer (http://www.shroomery.org/11839/Programming-and-metaprogramming-in-the-human-biocomputer)
R.A. Wilson. Discussion How to Brain-Wash Friends & Robotize People (http://www.reddit.com/r/PsychonautReadingClub/comments/1pmlee/prometheus_rising_chapter_10_discussion_how_to/)

ODD# V/(a)/1,v;24Afm3180
Title: Re: Source code
Post by: Cainad (dec.) on March 24, 2015, 12:54:03 PM
"I shall never tire of underlining a concise little fact which these superstitious people are loathe to admit--namely, that a thought comes when 'it' wants, not when 'I' want..."
-Nietzsche

And many other quotes I could find from multiple sources, but I'm on mobile and can't be arsed.

So how, pray tell, do you propose that we take ownership over the source of our own thoughts?
Title: Re: Source code
Post by: Pæs on March 25, 2015, 01:16:37 AM
Calling a daemon a service is a matter of semantics and is a naming choice made by Windows in particular, not by proprietary operating systems in general.

Mind as a computer metaphors are seriously fucking annoying because prats like you get too caught up in making a 1 to 1 mapping between elements of either system and stress the comparison to the point of uselessness.
Title: Re: Source code
Post by: Pæs on March 25, 2015, 01:21:27 AM
Fucking biocomputer psychonaut bullshit. If I ever give shroomery.org as a reference, someone 'rm -rf /' my neural storage device and put me out of my misery.
Title: Re: Source code
Post by: Cain on March 25, 2015, 01:47:09 AM
Copying and pasting Paes' neural net at randon into my iPhone....
Title: Re: Source code
Post by: Eater of Clowns on March 25, 2015, 02:14:54 AM
 :lulz:
Title: Re: Source code
Post by: Doktor Howl on March 25, 2015, 04:14:00 AM
 :lulz:
Title: Re: Source code
Post by: The Wizard Joseph on March 25, 2015, 05:59:28 PM
In the farthest depths of the unconscious mind there is a little sticker label that reads:

"Warranty void if opened"

It is written in Enochian.
Usually right next to the "first circuit" access port.

Beyond are many Bamas And Beebers man aught not know.
Spoils the Surprise!  :fnord:
Title: Re: Source code
Post by: minuspace on March 25, 2015, 07:34:51 PM
Actually, one of the things pissing me off recently is just how inconsiderate people's daemons or subconscious processes can be toward others.  Driving is very interesting because some operators can be seen as only taking notice of what is in front of them, disregarding entirely information from side/rear view mirrors.  Actually, they do take notice of what is behind them, however, they treat the information differently because it belongs to a category of possibility toward which they consider themselves not as legally/technically responsible.  For example, as the flow of traffic slows, said driver may brake in order to avoid front collision, however, without compensating for the proximity of the car behind them, they will still cause a collision.  Of course, they could have reduced their rate of deceleration, but they will convince themselves that there was no way they could have known, because, really, their minds are not under their control.
Title: Re: Source code
Post by: ñͤͣ̄ͦ̌̑͗͊͛͂͗ ̸̨̨̣̺̼̣̜͙͈͕̮̊̈́̈͂͛̽͊ͭ̓͆ͅé ̰̓̓́ͯ́́͞ on March 26, 2015, 06:32:24 AM
Quote from: Pæs on March 25, 2015, 01:16:37 AM
Calling a daemon a service is a matter of semantics and is a naming choice made by Windows in particular, not by proprietary operating systems in general.

Mind as a computer metaphors are seriously fucking annoying because prats like you get too caught up in making a 1 to 1 mapping between elements of either system and stress the comparison to the point of uselessness.

If you don't STFU I'm going to astrally pastebin your root chakra passwords.
Title: Re: Source code
Post by: minuspace on March 26, 2015, 09:02:52 AM
Quote from: N E T on March 26, 2015, 06:32:24 AM
Quote from: Pæs on March 25, 2015, 01:16:37 AM
Calling a daemon a service is a matter of semantics and is a naming choice made by Windows in particular, not by proprietary operating systems in general.

Mind as a computer metaphors are seriously fucking annoying because prats like you get too caught up in making a 1 to 1 mapping between elements of either system and stress the comparison to the point of uselessness.

If you don't STFU I'm going to astrally pastebin your root chakra passwords.
Bootstrap Maxwell Proximity backdoor with ENtropicKeY Daemon master logs.
Title: Re: Source code
Post by: The Wizard Joseph on March 26, 2015, 03:15:16 PM
Quote from: N E T on March 26, 2015, 06:32:24 AM
Quote from: Pæs on March 25, 2015, 01:16:37 AM
Calling a daemon a service is a matter of semantics and is a naming choice made by Windows in particular, not by proprietary operating systems in general.

Mind as a computer metaphors are seriously fucking annoying because prats like you get too caught up in making a 1 to 1 mapping between elements of either system and stress the comparison to the point of uselessness.

If you don't STFU I'm going to astrally pastebin your root chakra passwords
.

:lulz:  :lulz:.....  :lulz:

:potd:

Title: Re: Source code
Post by: Pæs on March 26, 2015, 11:05:56 PM
HNNNNNGGGGG MY QUANTUM CONSCIOUSNESS FIREWALL WASN'T CLEANSING THE KARMIC INPUTS SUFFICIENTLY, SO I COMPRESSED IT INTO A ZIP FILE.

NOW IT'S A MORE POTENT DEFENCE BECAUSE OF HOMOEOPATHIC PRINCIPLES.
Title: Re: Source code
Post by: Doktor Howl on March 26, 2015, 11:50:37 PM
Quote from: Pæs on March 26, 2015, 11:05:56 PM
HNNNNNGGGGG MY QUANTUM CONSCIOUSNESS FIREWALL WASN'T CLEANSING THE KARMIC INPUTS SUFFICIENTLY, SO I COMPRESSED IT INTO A ZIP FILE.

NOW IT'S A MORE POTENT DEFENCE BECAUSE OF HOMOEOPATHIC PRINCIPLES.

Well, technically, all you have to do is put a 1 and a 0 in a glass of water.
Title: Re: Source code
Post by: ivan on March 27, 2015, 02:12:30 PM
Quote from: Cainad (dec.) on March 24, 2015, 12:54:03 PM
So how, pray tell, do you propose that we take ownership over the source of our own thoughts?

I don't know. As you wish.
Title: Re: Source code
Post by: Meunster on April 17, 2015, 05:11:55 AM
Quote from: N E T on March 26, 2015, 06:32:24 AM
Quote from: Pæs on March 25, 2015, 01:16:37 AM
Calling a daemon a service is a matter of semantics and is a naming choice made by Windows in particular, not by proprietary operating systems in general.

Mind as a computer metaphors are seriously fucking annoying because prats like you get too caught up in making a 1 to 1 mapping between elements of either system and stress the comparison to the point of uselessness.

If you don't STFU I'm going to astrally pastebin your root chakra passwords.

I feel smart getting that joke. God I hate myself.