796 karma · joined August 10, 2017
I thought about using fail2ban but every login is a different IP (using my eyeballs, I didn't parse the logs).
It's entirely possible that the Alpine user base isn't as big/important as I would think but this seems like something that needs to be solved.
At least a few months ago, you needed to install an entire compilation suite if you wanted to install a pure-Python source distribution (sdist) that was created with Poetry on Alpine. Somewhat by design, sdists created with Poetry require Poetry to install. Poetry itself is dependent on the cryptography package which, like all like all packages that use native-C extensions, suffers from a lack of musl-compatible wheels.
There is also a version for Chrome: https://chrome.google.com/webstore/detail/dont-fuck-with-pas...
EDIT: Made the link locale independent and censored the name better.
If a forum's owner/admin participates in the forum, does that mean it's no longer a platform?
Python 3.8 added TypedDict which finally helps this particular shortcoming.
What is probably happening is that this is some sneaky way of introducing facial recognition in schools and something benign like attendance was the excuse. That, however, is a separate conversation from my original post of how would you automate attendance without using facial recognition.
If you want to add in the Play Store into the mix, things change slightly.
I am, however, in complete agreement that logging should adopt at least the same formatting used by .format
To be clear though, FPI is the real weapon here against things like Facebook tracking.
Private information isn't private if you have to give it out.
- Names: this is public information
- Addresses: this is public information
- Bank Account Details: this is on every check you've ever written
- SSN: this is on so many applications for things and compromised so many times it can't be realistically called private
- Account Login Details: not to be pedantic but this is a shared secret and should be treated as such
I know there have been some rumblings about actually trying to change the financial identification system in the US but really this needs to be the focus. We've been pretending that we have any sort of "secure" identification system for too long and now it's finally catching up to us. Solutions exist for a majority of these problems:
- For stolen credit card numbers: Force the issuers to add one-time CC number generation and have that one-time number locked to a merchant. Discover had this years ago and got rid of it; I'm sure others had it as well. This effectively solves the online merchant problem. Things like Visa Checkout and Masterpass also can help here by eliminating the need to give merchants your actual number (as can Android Pay, Apple Pay, Samsung Pay, PayPal, etc)
- For stolen credit cards: Actually change over to chip and pin
- For online financial identification: Issue smart+national ID cards like Estonia that can provide digital authentication. Is it perfect? No. If people don't like the concept of a smart+national ID card, put the risk of doing anything online on them. https://www.login.gov/ is a baby step in this direction.
I then tried adding a Bitcoin donation link in markdown in my README (before the transaction fees got silly) but the GitHub and NPM don't know what to do with it.