36 / M / Germany
Pretty much spot on.
36 / M / Germany
Pretty much spot on.
They don't owe you anything. Not sex, not a kiss, not a hug, not a second date, not even a smile. If the date goes well, you will get some or even all of those but if you try to force them, you will get nothing. Sure it can be disappointing if you put in a lot of effort and get nothing back but you will have to live with that. Sometimes people just aren't compatible and sometimes a date just goes wrong because of a weird coincidence.
Be nice, even if the date doesn't go as you wanted. Open communication goes a long way and chances are that the person you're talking to is just as insecure as you are. Explain (not accuse) why you don't think this situation will work out. If you're lucky, you can turn the conversation around. If not, at least you're ending the date in a civil way. That also (and especially) applies to talking on online dating platforms. Sometimes you can tell just from a conversation that things won't go anywhere. Way too many people just drop the conversation and move on which can feel pretty rude. Be nice, explain what's up, give them a friendly goodbye and then move on.
Those rules apply to both sides. You don't owe them anything either, especially if they get rude. You should still try to be friendly in case there is a misunderstanding but try to get yourself out of an uncomfortable situation before it gets worse. Your safety is still priority number one.
Edit: some more
Don't expect a relationship to last. Chances are it won't. But this isn't as pessimistic of a tip as you might expect. Even a single day of joy can be worth it if you manage your expectations. I've had a relationship crash and burn after seven years, I've had ones that lasted a couple of months and I've had someone ghost me after the second date. And still, all of them gave me amazing memories that I wouldn't want to miss and they helped me grow as a person. Allow things to grow on their own and enjoy the process. Maybe you will marry that person. Maybe you'll date them for a few months or years. Maybe you will never get past second base but stay platonic friends. Maybe you will spend the most amazing day of your life with them and then never see them again because you accidentally spilled something over their favorite t-shirt.
Sure. I use it as a structured place to keep notes on anything that may be important later, not specifically tasks:
All of those get put into categories and the categories are displayed on the main page via the categorytree plugin. The nice thing about having a wiki is that you have a lot of options for linking or embedding related content while still keeping it somewhat organized.
One doesn't have to be a Trump voter to think openly discussing murder is not okay. Especially because normalizing murder of one's political opponents plays right into right wing extremists' hands.
Just because you have IPv6 enabled doesn't mean you don't have IPv4. Both can coexist on the same network and the same device so your router can be 192.168.0.1 and some IPv6 address at the same time.
On top of that, many routers can be reached by a well-known hostname or domain, depending on their manufacturer. For example, AVM Fritz!Box routers (extremely popular in Germany) automatically resolve http://fritz.box to their own IP address no matter what that IP address is.
In the end, read the manual or the sticker on the device, same as you would have to do with IPv4 to figure out which subnet it is configured with.
I'll give it a shot. Not quite ELI5 but "Explain like I know what a phone number is". For the most important answer, see the last paragraph.
IP addresses are a bit like phone numbers. To send data to some computer, your computer attaches that number and sends the data packet on its way. With IPv4, an address is four bytes long, usually represented as four numbers from 0-255 separated with dots. That gives us a bit under 4.3 billion possible addresses which seemed enough when the system was invented and larger organizations could even reserve entire address ranges and some ranges got reserved for special purposes (for example, all 127.x.x.x addresses mean "send this to myself" while 192.168.x.x and 10.x.x.x are meant for local, non-public networks). Reserving these ranges is convinient when you need multiple machines connected to the internet but is very inefficient as these ranges need to be a power of two in size (256 is common), so you may get more addresses than you need and the rest stays unused.
The first solution was "Network Address Translation" (NAT). Basically, every household or organization gets a single public IPv4 address and every device on your network has a private address. On outgoing connections, your router replaces the (private) sender address with its public address and remembers which private address belongs to that connection so it can correctly forward any replies. For incoming connections, the router needs a list of rules to tell it what to do. For example something like "Everything on port 80 goes to 192.168.0.42". This worked for a while as most people make only outgoing connections and even many organizations can simply decide locally what to do with an incoming connection based on the received data so they wouldn't need multiple addresses.
After a while, it was clear that even with this workaround we would run out of addresses sooner or later. Providers tried giving their customers a different address every time they connected to the internet so they could reuse the address for someone else when the customer disconnected. This worked well when people only connected when they needed it but these days we're usually online 24/7.
So in the end, the only solution was to add more addresses. For our current needs, doubling the length would be more than enough but to be on the safe side, it was decided to quadruple the address length to a total of 16 bytes. This gives us about 340 undecillion unique addresses. Still not enough to give a unique address to every atom in the universe, not even enough for every atom on earth but still a lot. We can give every human an address range many times larger than the total address space of IPv4.
Does this mean that NAT is dead or that all your devices are visible from outside your network? Absolutely not. It means you can do that if you want. If your provider gives you a large address range, you can give each of your devices a different one and tell your router to forward everything. But you can also still use a single public address and/or tell your router to apply certain rules for what to do with incoming connections. There are also still address ranges that are meant purely for local use, equivalent to what 192.168.x.x and 10.x.x.x were in IPv4.
The expectation that people in office jobs can be productive for 8 hours per day.
Anyone upset that xkcd is supporting Harris probably hasn't been paying attention for the last 19 years. I wonder if this header image is a foreshadowing for XKCD 3000 (!) tomorrow.
When reading a long text, disconnect from the internet as soon as it has loaded so you don't pay for the time you spend reading.
I feel like a lot of answers here are dancing around why people find it offensive without really addressing it.
As an adjective "female" is completely fine to distinguish between genders when applied to humans. As in "a female athlete" or when a form asks you to select "male" or "female" (ideally with additional options "diverse" and "prefer not to answer").
Where it's problematic is when it's used as a noun. In English "a male" and "a female" is almost exclusively reserved for animals. For humans we have "a man" and "a woman". Calling a person "a female" is often considered offensive because it carries the implication of women being either animals, property or at least so extremely different from the speaker that they don't consider them equal. This impression is reinforced by the fact that the trend of calling women "females" is popular with self-proclaimed "nice guys" who blame women for not wanting to date them when in reality it's their own behavior (for example calling women "females") that drives potential partners away.
So in itself, the word "female" is just as valid as "male" and in some contexts definitely the right word to use but the way it has been used gives it a certain negative connotation.
Sources on literacy in Medieval Europe seem to be all over the place, reaching from the popular "Almost nobody could even sign their name" to "There was at least one person in most households who could read and write". Here's a discussion on Stackexchange that lists some sources.
The sad truth is, we may never know how literate people actually were. We can be relatively sure that especially poor people didn't have any formal education and couldn't afford expensive handwritten books. But that doesn't necessarily mean people couldn't read and write at all. A basic level of literacy was useful for a lot of people, especially craftsmen and traders. Not so much that they'd read and write whole books but enough for basic bookkeeping or passing notes to someone who lives in a neighboring village. The thing is, those are not the kind of things that would be preserved until today. Paper and parchment were too expensive for such trivialities but we have evidence from Russia that people wrote everyday correspondence on birch bark. With no need to store these writings, most people would have probably just reused whatever they were written on to light fires or just thrown them outside where they would decompose within a few weeks.
(this kind of ties into a fun fact about why so few authentic chainmail shirts have survived until today. Not because they got destroyed by rust but because after they lost their usefulness in early modern times, they were cut up and reused to scrub pots)
Wanna bet if Tesla gets an exception?