Welcome to Incels.is - Involuntary Celibate Forum

Welcome! This is a forum for involuntary celibates: people who lack a significant other. Are you lonely and wish you had someone in your life? You're not alone! Join our forum and talk to people just like you.

Tip #35: The Matrix is Real in the Here and Now - how to reduce Internet usage

Knajjd

Knajjd

Admiral
★★★★
Joined
Sep 2, 2021
Posts
2,817
In the film, The Matrix, humans are wired into an operating system that runs an app for each person. An app is code.

Now, as we use a laptop or a smartphone code is stored in the RAM and run by the CPU.

Everytime we use an electronic device, code is run. Our minds are interfaced to this running code via a screen and keyboard. It's not hard wired to the brain like in the film but it's still a connection.

The running code effects us. Look, for example, at the porn sites. Coomers are being controlled by running code. They can't see this but if you stop and think the brower code is connecting to the web server code and it's all definitely running on the CPU/RAM, both local and remote. The coomer, a human, is under control of the code.

If you could see this code running on the coomer's browser and the web site that streams the porn you would think the world has gone mad. On one side is the coomer fapping on the bed and on the other side is code running down the screen. Surely this is exactly what The Matrix film shows with the green characters scrolling down. We are not connected 24/7 but in the modern world but many of us do interact with running code for most of the day. We are input/output devices that the code controls.

Now if you're trying to use the Internet less, try thinking that you're interacting with mindless code. Imagine the streaming code, just like in the film. All of a sudden using the Internet doesn't seem so interesting.

Here is a little bit of C code, for those unfamiliar what code looks like, that I copied from the tcpdump program. Imagine millions of lines running.

static void
pcap_set_parser_debug(int value)
{
#ifdef HAVE_PCAP_DEBUG
extern int pcap_debug;

pcap_debug = value;
#else /* HAVE_PCAP_DEBUG */
extern int yydebug;

yydebug = value;
#endif /* HAVE_PCAP_DEBUG */
}

#define HAVE_PCAP_SET_PARSER_DEBUG
#endif // HAVE_PCAP_SET_PARSER_DEBUG, HAVE_PCAP_DEBUG, HAVE_YYDEBUG

#if defined(HAVE_PCAP_SET_OPTIMIZER_DEBUG)
/*
* We have pcap_set_optimizer_debug() in libpcap; declare it (it's not declared
* by any libpcap header, because it's a special hack, only available if
* libpcap was configured to include it, and only intended for use by
* libpcap developers trying to debug the optimizer for filter expressions).
*/
#ifdef _WIN32
__declspec(dllimport)
#else /* _WIN32 */
extern
#endif /* _WIN32 */
void pcap_set_optimizer_debug(int);
#endif // HAVE_PCAP_SET_OPTIMIZER_DEBUG

static void NORETURN
exit_tcpdump(const int status)
{
nd_cleanup();
exit(status);
}

/* VARARGS */
static void NORETURN PRINTFLIKE(1, 2)
error(FORMAT_STRING(const char *fmt), ...)
{
va_list ap;

(void)fprintf(stderr, "%s: ", program_name);
va_start(ap, fmt);
(void)vfprintf(stderr, fmt, ap);
va_end(ap);
if (*fmt) {
fmt += strlen(fmt);
if (fmt[-1] != '\n')
(void)fputc('\n', stderr);
}
exit_tcpdump(S_ERR_HOST_PROGRAM);
/* NOTREACHED */
}
 
Last edited:
@fukurou thoughts?
 
Why did you use C as an example when that is high level and in reality things are running on assembly instructions executed in the CPU logic circuits.

Here is assembly and it looks more like the matrix

    • ADD,1,GPR3,R1;
    • ADD,GPR15,255,R7;
    • SUB,128,GPR3,R3;
    • JMPZ,5;
    • JMP,0;
    • ADD,GPR15,128,R7;
    • MOV,GPR15,R0;
    • ADD,0,127,R5;
    • ADD,0,0,R0;
    • MOV,GPR1,MAR;
    • LOAD,GPR0,GPR0,R0;
    • ADD,MDR1,MDR2,R1;
    • DIV,GPR3,GPR3,R1;
    • ADD,MAR,128,MAR;
    • LOAD,GPR0,GPR0,R0;
    • ADD,MDR1,MDR2,R2;
    • DIV,GPR5,GPR5,R2;
    • ADD,GPR3,GPR5,R1;
    • DIV,GPR3,GPR3,R1;
    • MOV,GPR3,MDR2;
    • ADD,GPR1,GPR15,MAR;
    • STORE,GPR0,GPR0,R0;
    • SUB,GPR11,GPR1,R4;
    • JMPZ,26;
    • ADD,GPR1,1,R0;
    • JMP,9;
    • ADD,GPR1,129,R0;
    • ADD,GPR11,255,R5;
    • ADD,GPR11,1,R5;
    • SUB,GPR11,GPR15,R4;
    • SUB,GPR9,127,R4;
    • JMPZ,33;
    • JMP,9;
    • MOV,GPR1,R0;
 
Why did you use C as an example when that is high level and in reality things are running on assembly instructions executed in the CPU logic circuits.

Here is assembly and it looks more like the matrix

    • ADD,1,GPR3,R1;
    • ADD,GPR15,255,R7;
    • SUB,128,GPR3,R3;
    • JMPZ,5;
    • JMP,0;
    • ADD,GPR15,128,R7;
    • MOV,GPR15,R0;
    • ADD,0,127,R5;
    • ADD,0,0,R0;
    • MOV,GPR1,MAR;
    • LOAD,GPR0,GPR0,R0;
    • ADD,MDR1,MDR2,R1;
    • DIV,GPR3,GPR3,R1;
    • ADD,MAR,128,MAR;
    • LOAD,GPR0,GPR0,R0;
    • ADD,MDR1,MDR2,R2;
    • DIV,GPR5,GPR5,R2;
    • ADD,GPR3,GPR5,R1;
    • DIV,GPR3,GPR3,R1;
    • MOV,GPR3,MDR2;
    • ADD,GPR1,GPR15,MAR;
    • STORE,GPR0,GPR0,R0;
    • SUB,GPR11,GPR1,R4;
    • JMPZ,26;
    • ADD,GPR1,1,R0;
    • JMP,9;
    • ADD,GPR1,129,R0;
    • ADD,GPR11,255,R5;
    • ADD,GPR11,1,R5;
    • SUB,GPR11,GPR15,R4;
    • SUB,GPR9,127,R4;
    • JMPZ,33;
    • JMP,9;
    • MOV,GPR1,R0;
Assembler looks better, I agree. At the end of the day it's all about transistors changing states.

This link shows a CPU executing code and gives a better idea of what's going on. Press the play button on the right hand panel.


Transistors are solid state devices so quantum effects are at work which means even more mystery.
 
Last edited:
I remember a different knajjd
 
Print fuk niggs
 
In the film, The Matrix, humans are wired into an operating system that runs an app for each person. An app is code.

Now, as we use a laptop or a smartphone code is stored in the RAM and run by the CPU.

Everytime we use an electronic device, code is run. Our minds are interfaced to this running code via a screen and keyboard. It's not hard wired to the brain like in the film but it's still a connection.

The running code effects us. Look, for example, at the porn sites. Coomers are being controlled by running code. They can't see this but if you stop and think the brower code is connecting to the web server code and it's all definitely running on the CPU/RAM, both local and remote. The coomer, a human, is under control of the code.

If you could see this code running on the coomer's browser and the web site that streams the porn you would think the world has gone mad. On one side is the coomer fapping on the bed and on the other side is code running down the screen. Surely this is exactly what The Matrix film shows with the green characters scrolling down. We are not connected 24/7 but in the modern world but many of us do interact with running code for most of the day. We are input/output devices that the code controls.

Now if you're trying to use the Internet less, try thinking that you're interacting with mindless code. Imagine the streaming code, just like in the film. All of a sudden using the Internet doesn't seem so interesting.

Here is a little bit of C code, for those unfamiliar what code looks like, that I copied from the tcpdump program. Imagine millions of lines running.

static void
pcap_set_parser_debug(int value)
{
#ifdef HAVE_PCAP_DEBUG
extern int pcap_debug;

pcap_debug = value;
#else /* HAVE_PCAP_DEBUG */
extern int yydebug;

yydebug = value;
#endif /* HAVE_PCAP_DEBUG */
}

#define HAVE_PCAP_SET_PARSER_DEBUG
#endif // HAVE_PCAP_SET_PARSER_DEBUG, HAVE_PCAP_DEBUG, HAVE_YYDEBUG

#if defined(HAVE_PCAP_SET_OPTIMIZER_DEBUG)
/*
* We have pcap_set_optimizer_debug() in libpcap; declare it (it's not declared
* by any libpcap header, because it's a special hack, only available if
* libpcap was configured to include it, and only intended for use by
* libpcap developers trying to debug the optimizer for filter expressions).
*/
#ifdef _WIN32
__declspec(dllimport)
#else /* _WIN32 */
extern
#endif /* _WIN32 */
void pcap_set_optimizer_debug(int);
#endif // HAVE_PCAP_SET_OPTIMIZER_DEBUG

static void NORETURN
exit_tcpdump(const int status)
{
nd_cleanup();
exit(status);
}

/* VARARGS */
static void NORETURN PRINTFLIKE(1, 2)
error(FORMAT_STRING(const char *fmt), ...)
{
va_list ap;

(void)fprintf(stderr, "%s: ", program_name);
va_start(ap, fmt);
(void)vfprintf(stderr, fmt, ap);
va_end(ap);
if (*fmt) {
fmt += strlen(fmt);
if (fmt[-1] != '\n')
(void)fputc('\n', stderr);
}
exit_tcpdump(S_ERR_HOST_PROGRAM);
/* NOTREACHED */
}
I like networking any recommendations where should I start (judging from the pcap example)
 
I like networking any recommendations where should I start (judging from the pcap example)
They are 3 networking parameters that are key; IP, netmask and default gateway (aka default router).

A network defines a set of IP addresses. A router is a host with 2 (or more) network cards that connect networks. You can set up a Linux VM to act as a router.

Start with tcpdump. Examine the packets on the wire between two machines on a local switch.

Look up the structure of an Ethernet packet. Look for packet fields in tcpdump.

I've used tools like tcpdump to troubleshoot problems like if a firewall is between the client and server, or the server is down or the server is up but broken (as in it's in an error state but still running) from the TCP 3-way handshake.

Say you have two process sending/receiving information on a local RAM. That's local Inter Process Communication (IPC). Now say you have a RAM in NY and a RAM in London and they are communicating. This is remote IPC or comms over a network.

Here is a post about a very short implementation of TCP/IP in C. Even if you don't know C you'll be able to follow the code.
https://incels.is/threads/heres-a-minimal-tcp-ip-implementation.543170/

I learnt networking from the book Practical TCP/IP by Niall Mansfield. The main lesson I learnt from working at a telecoms company was to create network diagrams. Mansfield has examples. Start off with a horizontal line (a switch) then slowly add a square to represent a host. Add the host IP to the host square and the network address at the end of the line. Build up the diagram as you learn about my hosts and other networks. Firewall are the diode symbol and routers the cake symbol. Diagrams can get very large but they are *extremely*useful. Often I'm the only one who knows how the structure of a network because of the diagrams.

About client server. Think of when you go to a MacD to buy some tendies. You make a request (tendies) and the server behind the counter response is to give you a box of tendies. They might be others behind you in the queue, all clients wanting to make requests to the server. This is how client/server comms is setup. As request/response You can see all this in tcpdump. It's a great diagnostic tool.

Buy a cheap wired Ethernet card and look at the components on it. It will have a MAC address ROM, Ethernet tx/rx and controller. The device driver (software in the kernel) drives the controller which in turn drives the tx/rx device.

You might know all this already. I learnt from the Mansfield book (read some of the chapters many many times) and reading the source of simple Linux network commands. Read some of the RFC's written by Jon Postel.

Also don't run nmap to troubleshoot at work without permission (an email) as it's usually an instant dismissal.

Tagged Caesercel who might be interested .

@Caesercel
 
They are 3 networking parameters that are key; IP, netmask and default gateway (aka default router).

A network defines a set of IP addresses. A router is a host with 2 (or more) network cards that connect networks. You can set up a Linux VM to act as a router.

Start with tcpdump. Examine the packets on the wire between two machines on a local switch.

Look up the structure of an Ethernet packet. Look for packet fields in tcpdump.

I've used tools like tcpdump to troubleshoot problems like if a firewall is between the client and server, or the server is down or the server is up but broken (as in it's in an error state but still running) from the TCP 3-way handshake.

Say you have two process sending/receiving information on a local RAM. That's local Inter Process Communication (IPC). Now say you have a RAM in NY and a RAM in London and they are communicating. This is remote IPC or comms over a network.

Here is a post about a very short implementation of TCP/IP in C. Even if you don't know C you'll be able to follow the code.
https://incels.is/threads/heres-a-minimal-tcp-ip-implementation.543170/

I learnt networking from the book Practical TCP/IP by Niall Mansfield. The main lesson I learnt from working at a telecoms company was to create network diagrams. Mansfield has examples. Start off with a horizontal line (a switch) then slowly add a square to represent a host. Add the host IP to the host square and the network address at the end of the line. Build up the diagram as you learn about my hosts and other networks. Firewall are the diode symbol and routers the cake symbol. Diagrams can get very large but they are *extremely*useful. Often I'm the only one who knows how the structure of a network because of the diagrams.

About client server. Think of when you go to a MacD to buy some tendies. You make a request (tendies) and the server behind the counter response is to give you a box of tendies. They might be others behind you in the queue, all clients wanting to make requests to the server. This is how client/server comms is setup. As request/response You can see all this in tcpdump. It's a great diagnostic tool.

Buy a cheap wired Ethernet card and look at the components on it. It will have a MAC address ROM, Ethernet tx/rx and controller. The device driver (software in the kernel) drives the controller which in turn drives the tx/rx device.

You might know all this already. I learnt from the Mansfield book (read some of the chapters many many times) and reading the source of simple Linux network commands. Read some of the RFC's written by Jon Postel.

Also don't run nmap to troubleshoot at work without permission (an email) as it's usually an instant dismissal.

Tagged Caesercel who might be interested .

@Caesercel
Thanks mang i will definitely give give a go for the book.
 
That's all very interesting, but you see, I'm interacting with other humans through code.
 
Basically, useless bullshit....
 

Users who are viewing this thread

shape1
shape2
shape3
shape4
shape5
shape6
Back
Top