that’s already in the cheatsheet

Nice, mypath.open() is a more semantic alternative to open(my path)

when i had to do it, they could only be exported to another google auth via QR code. I was forced to recreate the codes on every service.

Previously, you long-pressed on those six digits in the account list to copy to your clipboard.

With last week’s Google Authenticator update, a simple tap is how you copy those codes. (That being said, we’ve noticed that a long-press sometimes still works in version 7.0, but it’s inconsistent and the single tap is clearly the intended behavior.) A single touch is definitely simpler, but users have to adjust to this.

Google Auth and Authy lock you in, consider migrating to Aegis or Ente Auth.

I’ve seen plenty of grad student code, abundance of OOP concepts was never an issue. Complete lack of any structure on the other hand…

Tbh if the average grad school student overused object oriented stuff they would produce vastly better code than the status quo.

does

man touch

yeah, discord the the true black hole of information

nah, I just misunderstood the call to action, I was expecting a link for each app.

colleague of the marketing guy that just makes up metrics to pretend to his boss and stakeholders that their work on ads makes any difference

laudable professionals

ok, but how to donate to an app? I only see a link to become a supporting member of KDE itself

I’ll assume you’re asking for Linux; I have tried several ways of blurring the background of Firefox window components with page content in the back without success. It seems they’re rendered in entirely separate contexts, as blur effects don’t apply; nor does any other filter that would combine window and page content.

My use case was to blur the background of collapsible vertical tabs when expanded, and blur the bg of the URL bar dropdown. Changing background opacity works, however.

thankfully Python seems to be moving away from the “activating your venv” nonsense. If you use poetry or uv, you don’t necessarily need to “activate” it before running your code; though a lot of people still try to do it because of learning inertia I guess.

uv

Everything else feels 4 to 15 years behind.

basically sums up the opencv experience in Python.

great lib, very mediocre Python wrapper.

the least I’ve seen was 6 months. If I had to change passwords every 90 days I’d spam them with articles showing this is idiotic every month.

and only because the system forces users to renew passwords every year and this is his third year

some forks have outdated commits, the latest one recorded by wayback machine last month is e935959d2f9cc642bcbb5e7759b2b1e7196b0947, which can still be found in a few repos:

https://github.com/search?q=e935959d2f9cc642bcbb5e7759b2b1e7196b0947&type=commits

btw, the mirror linked in the github conversation is also out of date in relation to the original repo.

where hand?