They obviously look at child porn. If they had nothing to hide, they would volunteer!

I say it's time to investigate each politicians phones and computers and then install monitoring software.

For the children.

Jesus would be crucified again by the very people who where his cross around their necks.

I love how it's always "immigrants stole our jobs" and never "the rich CEO hired the cheap labor".

That's cheating. Anything will taste great with butter and garlic.

I can't remember which comedian said this but he absolutely loves talking to flat earthers. Whenever they bring up the moon being too small, etc., he bursts out laughing and says, "You believe in the moon?!"

This should read as:

Regulators: allows the meat industry to put creatures in the filthiest conditions possible

disease starts spreading and affecting the industry

Regulators: 😧

If you simply want to allow people to view your code, you can just upload it to GitHub or something similar.

By default, your work is copyright and you hold all rights, excluding those you give up to GitHub.

Open-Sourcing your project is all about choosing the license that you want your users to use.

Please, for the love of God, choose an existing license. Don't go out and try to make one yourself or mix and match. Not only do you open yourself up to liability but it just makes it harder for you to keep track of it.

Choosing a license is all about your personal preference and what your goals are. The two ends of the spectrum:

• MIT License: do whatever you want, so long as you attribute me. Most libraries use this license.
• GPL/AGPL: if you use my code, you must also release using GPL/AGPL or similarly appropriate license. Linux Kernel famously uses version 2. Linus Torvalds has issues with some of the terms in V3.

There is a lot of middle ground between these two philosophies. Most of the major licenses have seen some level of court cases. I personally use AGPL, which is often seen as one of the strongest, most restrictive, licenses.

I do not recommend releasing code to public domain. This often is a point of contention between OSS purists and OSS "spirit". I personally believe we're entering a new world of AI-driven content and I don't want more code feeding that beast.

The license is then copied and pasted to a LICENSE file at the root of your repo and, boom. You've open sourced your code.

Keep in mind: that commit (and all future commits) will be available under that license until your copyright expires, so long as that license exists in your repo. You cannot claw it back.

One word of advice: you aren't likely going to see a bunch of people downloading your stuff. So don't get your hopes up that you'll have people submitting bug reports or making PRs, etc. All of my projects are just for me to use with one or two people reviewing it for fun. All but one, anyway.

Yeah I rewatched this not too long ago, hoping that running it at 2x speed would make it better. It did for the most part.

I never saw the last season and when I saw it, I found I was right that the show was "How I Met Your Mother, starring Aunt Robin"

For me the issue is that coupons are often for brand name items and the coupon rarely makes it more cost effective than buying store brand.

Your passkey is an encrypted message that authenticates you, the service you're trying to reach, and your computer.

If you go to a phishing site, the passkey won't even come up because the browser doesn't recognize the site. Granted a dumb user could still use their user/pass but ideally the user has MFA set up so they can't get far.

The goal of a passkey is to replace username and passwords entirely so that phishing becomes less common.

The main issue with passkeys is that unless you have something like a YubiKey or an authenticator (like bitwarden), the passkey is tied to the browser which means if the device gets lost you can't log in anymore.

Either with a pin or thumbprint

If you're entering a u/p along with a passkey, then it's MFA.

There are only a few sites I know of that do passkey correctly. CVS works wonderfully on my phone. Requires a username and then the passkey on my browser.

My company is working on a passkey only for login and it's really really slick.

You basically click "login" and then authenticate your passkey and you're in.

A time machine, at its very very core, is a literary device. You wouldn't bring up this nuance unless it was important to the plot of the story.

It's like warp drives. The point of warp or any FTL travel is to skip the boring parts. You only learn about warp drives when something goes wrong.

I actually really liked the book over the movie. I felt like the book did a much better job of describing the dystopian world and how the MC (can't remember his name and too lazy to look it up) and the world at large more or less dealt with it.

Iirc the movie doesn't even go into the history of the digital world and why the MC was obsessed with it. I get that movies and books are different but it seemed like the movie was "inspired" by the book and not based on it.

They may not know how it works, which is why it's fucking dangerous that they are getting "consulted" by the MPA.

Best case scenario: it's just a DNS level block.

Worst case scenario: it's a DNS level log capture so that the MPA can sue people who watch things on fmovies or similar sites, like the RIAA did in the 90s.