I heard it was due to greater blood flow to areas that routinely don’t experience that level of flow, kind of like how you really notice the breeze on your face after you shave off your beard. Now, I don’t have any proof this is it, but a month or so of regular brisk walks should be enough for your cardiovascular system to adapt to the new requirements, causing the sensation to vastly reduce if not disappear completely.

Related to that, and a line that just stuck with me: A boat is a hole in the water that you pour money into.

I’ll remember this whenever someone says you’ll run out of things to do when you retire.

There is nothing stopping a GPL project using MIT-licensed code except for lack of desire to do the work. They are one-way compatible.

It really depends. If the contract gives ownership of the work created to the purchaser, he has no rights to it whatsoever. Moreover, trying to do a clean room implementation of your own code is almost impossible without help. A permissive license would give the purchaser unlimited use of the product, including resale while still allowing the producer unlimited use, as well. If the contract is written correctly, the producer might even retain ownership, with the right to use different licenses, while the purchaser would have few or no restrictions.

I’ll throw my opinions in here.

If you’re publishing a standard or a reference application, a permissive license makes sense. What better way to guarantee compatibility than being able to use the reference code in your product. This is what happened with the TCP/IP stack, and it was used in its original form in Windows for years.

If you’re making something that you want to build a community around, something more akin to the GPL may be more aligned with your goals. The nice part is, you can include MIT licensed projects as part of your GPL project. This means there is nothing stopping you from building your standard with a MIT license while building your community-driven application using GPL, maximizing the reach of your standard while reducing the risk to your community.

Note that either option opens you to EEE (Embrace, Extend, Extinguish), the GPL option just takes an extra step (clean room implementation of a published standard).

I’m perfectly aware of how it works. My whole comment was a proposed way to manage it that doesn’t assume that everyone who uses outlook wants to use MS’s cloud service just because they also happen to use Outlook. I’m not sure how you missed that.

As for emphasis, “Press fucking backspace!” has a whole lot of it. I certainly would consider that, and not your hypothetical, as actively aggressive.

My qualifier for the 200 years or more is because we have some crops that we’ve only grown extensively for a couple hundred years, and the almost is because I don’t know the details for some new world crops such as quinoa and amaranth.

Philip K. Dick would either be proud or try to kill you for reading his mind.

There are a number of antiviral medicines, some of which work against influenza A and B. I’m pretty sure these are prescription medications in Canada.

If by “a lot” you mean “nearly all commonly grown crops in the last 200 years or more”, then yes. There are very few crops we haven’t altered in our quest to feed more people with less work, and even things such as heirloom produce are just varieties that breed true (and may have been around longer than the other varieties).

I have some concerns about GMOs, mostly because we aren’t very good at it yet. When we start producing things with the behavior of cucumbers producing cucurbitacin (not a desirable trait, but highly targeted), or if we’re adding benign genes that make something produce beta carotene, I’m all for it.

If you wish to talk about critical thinking, look at your own statements with respect to mine. Not once did I say cancel thenlink attachment, but this thing I didn’t say sure got you upset. Moreover, I wasn’t writing a formal specification. I’m sorry your assuming the worst and least likely meaning of what I thought was a pretty simple statement triggered you so badly.

Yeah, it sure does sound like it would be hard to have a notification if the attachment is going to fail due to size policies, and then have an option to use the link or cancel the attachment (and have you choose another way). It would also be unheard of for there to be a setting in that dialog to say to always do whatever action you take so it only inconveniences those who go with the default once.

User-hostile software is never a “you” problem. This applies to a number of FOSS products, as well.

It’s okay buddy, your definition of exodus was wrong. Just let it go.

As for the rest, I made a sarcastic comment based entirely on fact, they asked for proof of my statement, I gave them everything they needed to verify it. I’m sorry if my comment was too harsh for your sensibilities, but if that’s the worst you’ve heard on Lemmy, them I’m glad for you.

No definition I’ve ever heard requires an exodus to be initiated by the people leaving. Also, if you read the comment that started all this, I was explicit that I didn’t mean employee-led. So thanks for stopping by weeks later to display your ignorance and/or lack of reading comprehension.

the bidet temporarily connects my butthole

with a near infinite series of tubes

containing pure water and in that moment

I am the clean water and the clean water is me

That’s some wild poetry there.

This sounds like something you could fix with practice. Maybe try reading books out loud. People with pleasant voices can also make audio books, although I don’t know how much they pay.

I’m not entirely sold on the whole solarpunk thing, either, but I got more of an “increase your self-sufficiency, reduce your gratuitous consumption” vibe. Solar panels, high-efficiency lighting/energy usage, self-hosted computing, low-power computing. These kinds of things can add resiliency, not reduce it, especially if you live in a place with unreliable regional services such as statewide blackout/brownouts.

I’m not sure how to access monologs, and the Voyager app doesn’t support them. Give a noob a quick tutorial?

The case is clearly textured in the closeup. Grinding it down will definitely mar the surface, but sanding might be more effective.