The DM just has an unshakable, deep devotion to the Rule of Cool.
Even more impressive when someone lops his hand off and presents it to the machine and gains access to his multiple gigabytes of Stallman x Jobs fanfic.
That implant needs to be the second factor so that the bad guys also need a wrench.
That movie was way better than I expected it to be.
Unfortunately you still have to give Google money to run Graphene unless you already have a compatible Pixel phone.
On Android these are called Intents and yeah it sounds like Metaface is specifically using the Instagram intent when opening an Instagram URL rather than the default browser intent.
I want an hourly Konsi but I’ll settle for daily.
If this is from the perspective of a hobbyist or brand new Python dev, that’s a fair opinion to have, I suppose.
That said, if you’re using Python in a professional capacity, you really need to learn how to use the toolchain properly.
Python packaging and virtual environments are not difficult to understand, and I’d wager based on your comments elsewhere in this thread that your frustrations are born from not taking the time to understand why following the instructions from a fourteen-year-old blog post aren’t working.
99.99% of the time, the fault isn’t with pip, it’s with the maintainer of the broken package you’re trying to use.
I think that’s the purpose of the “next update” part. As long as the ability to refresh that timestamp is gated behind a passphrase (for 5A protection) then it functions as a deadman switch for the canary.
The 😐 button is my favorite part.
Ironically, if you buy a Google phone (Pixel 6 or later) you can load GrapheneOS and avoid the Google ecosystem entirely.
Sorry to doxx you but I know that’s just an alias address. Your real IP is 127.0.0.1