bjorney

Do you think an open Hario switch basically IS a v60?

It is. It’s just a glass v60 with a seal at the bottom

That assumes that an adversary has control of the browser

No it doesn’t, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account

The big reason you don’t want to send passwords over https is that some organizations have custom certs setup

What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways

It is better to just not send the password at all.

How would you verify it then?

If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in

Client side verification is just security by obscurity, which gains you very little.

If someone is capable of MITM attacking a user and fetching a password mid-transit to the server over HTTPS, they are surely capable of popping open devtools and reverse engineering your cryptographic code to either a) uncover the original password, or b) just using the encrypted credentials directly to authenticate with your server without ever having known the password in the first place

deleted by creator

You are acting like someone checked off a “log passwords” box, as if that’s a thing that even exists

Someone configured a logger to write HTTP bodies and headers, not realizing they needed to build a custom handler to iterate through every body and header anonymizing any fields that may plausibly contain sensitive information. It’s something that literally every dev has done at some point before they knew better.

deleted by creator

lol. Did this in my old building - the dryer was on an improperly rated circuit and the breaker would trip half the time, eating my money and leaving wet clothes.

It was one of the old, “insert coin, push metal chute in” types. Turns out you could bend a coat hanger and fish it through a hole in the back to engage the lever that the push-mechanism was supposed to engage. Showed everyone in the building.

The landlord came by the building a month later and asked why there was no money in the machines, I told him “we all started going to the laundromat down the street because it was cheaper”

You can just put an aeropress filter above the grounds before you screw the top on your mokapot (assuming you don’t have one of the super size ones)

Mine died after 9 years or so. Did that thing where the rubber breaks down and gets super sticky and oily. Never had an issue with it losing its shape - you just have to make sure you store it fully pressed in so the lip pops out the far side of the tube

Too bad it still can’t figure out how to do dead ass simple things the old assistant had no problem with, like setting a reminder or alarm

You can just point your domain at your local IP, e.g. 192.168.0.100

Right? it screams wayyyy pre-y2k but MySQL was only release in 95

will it become a relic of the past?

Probably

why YEAR in the first place, who would actually make use of it?

Accounting systems in the 90s that needed to squeeze out every drop of performance imaginable

I expect it won’t

The year datatype is a 1 byte integer, but the engine adds/subtracts 1900 to the value under the hood and has special handling for zero.

If you need to store more than 255 years range, you can use a 2 byte integer, which doesn’t need that special handling under the hood, because with 2 bytes you can store 65000+ years

tl;dr

We find that men who are more dissatisfied with the size of their penises are less likely to personally own guns across outcomes

There are like 10,000 different solutions, but I would just recommend using what’s built in to python

If you have multiple versions installed you should be able to call python3.12 to use 3.12, etc

Best practice is to use a different virtual environment for every project, which is basically a copy of an existing installed python version with its own packages folder. Calling pip with the system python installs it for the entire OS. Calling it with sudo puts the packages in a separate package directory reserved for the operating system and can create conflicts and break stuff (as far as I remember, this could have changed in recent versions)

Make a virtual environment with python3.13 -m venv venv the 2nd one is the directory name. Instead of calling the system python, call the executable at venv/bin/python3

If you do source venv/bin/activate it will temporarily replace all your bash commands to point to the executables in your venv instead of the system python install (for pip, etc). deactivate to revert. IDEs should detect the virtual environment in your project folder and automatically activate it

Not with 64gb ram and 16+ cores on that budget

So the “biologists and pharmacologists” you are citing are just armchair scientists in the Lemmy comment section

You could set it up in docker whilst still on windows, and then all you need to do is copy/paste your compose file onto your new Linux machine, that way you aren’t struggling to learn two things at the same time (alleviates the “I don’t know if the problem is with my docker config or my host OS”)

“how dare they use the right tool for the job without taking the time to learn how to do it sub optimally first”