Recent comments in /f/explainlikeimfive

candlestick_maker76 t1_j22iayo wrote

Reply to comment by Weary-Lie-3581 in ELI5: Does period flow level impact how you feel while pregnant? by UnashamedLiar

To add to your data set: my flow has always been light, and I've never had cramps. Pregnancy was awesome. No morning sickness, no depression afterward. The ONLY unpleasant part was stupid childbirth.

I, like your wife, have only done it once. So now you have a sample of two, which is double what you had (hooray!) but...still a ridiculously small sample.

1

bloode975 t1_j22dsnw wrote

Reply to comment by police-ical in ELI5: How does "acquired taste" work? And how are some tastes able to be acquired no problem, while others will never be acquired? by PuzzleBrain20

On the vomiting with a food you used to like, when I was a kid I'd had a bunch of chocolate in the morning, like alot of chocolate, turns out I'd gotten food poisoning the night before and spent the entire day vomiting up chocolate and shitting myself, once you've tasted partly digested chocolate mixed with bile lemme tell you chocolate loses most of its appeal.

23

TipEffective3625 t1_j229oce wrote

Reply to ELI5: Does period flow level impact how you feel while pregnant? by UnashamedLiar

No.

There are some health conditions that can cause abnormal or irregular periods and also affect fertility. For example, PCOS and hypothyroidism can cause heavy periods and make it harder to conceive, or increase the risk of miscarriage. Endometriosis can cause heavy periods and increase the risk of complications in pregnancy.

But there is no known connection between the rate of flow in normal periods, and the intensity of pregnancy symptoms.

6

egoalter t1_j228faf wrote

Reply to ELI5: What is a network port? by Brianprokpo456

All communication on a TCP/IP network needs a socket pair for communication for destination and source. This means IP/PORT for both sender and receiver. They are equally important to make communication work because a computer representing an IP run more than one thing at a time, but each process that runs need a unique transmission pipe. That's the sender port. The destination is "what service" do you want - in general servers have many programs running to handle different incoming traffic. In other words, an IP by itself doesn't work. Just like the type of protocol can be different. Some protocols use different ways of addressing the service (such as ICMP) but in general the sender specifies what service the data is meant for.

A bit more technical, when you write server code that responds to incoming network traffic you bind/select a given port, telling the OS that traffic that comes in to this port is responded to by your process. Only ONE process can do this at a time. Some ports are restricted and a lot of ports have been standardized (see /etc/services on Linux) but to the computer the number is arbitrary. You can easily make your web-server respond to incoming requests to port 7777 if you want. It's just a number.

The sender's port number is very rarely specified manually (but you can). The OS provides a pool of free sender port numbers and assigns a "random" port number when you open a connection. Every time you open a connection a new port is created, and if the programmer forgets to close the connection the OS will quickly run out of port numbers in the pool. But the IP/port of the source/destination stays the same throughout the whole communication. A lot of this is small/quick communication - when you browse a web-page you're often directed to 10,20 or more sites for style, scripts and more - each of them the browser creates a separate connection to (although modern protocols can share connections to the same server). Point is, that the socket pairs are key to identify the connection.

1