You don't need to use the brick, but you must have one
| github | https://github.com/knoopx |
| personal website | https://knoopx.net/ |
| github | https://github.com/knoopx |
| personal website | https://knoopx.net/ |
Couldn’t agree more with the sentiment and arguments here. The FSF is failing hard at making any impact on anything.
https://drewdevault.com/2023/04/11/2023-04-11-The-FSF-is-dying.html
#InfoSec FYI: There's a massive #typosquatting campaign targeting PyPI. Someone's clearly reached the automation section of "Black Hat Python" 🙄
This is the same actor as highlighted by Phylum yesterday - currently they're pushing a cryptostealer everywhere they can, but who knows what's next.
Recently, they've started typosquatting the following packages (& showing example typosquat):
* xlsxwriter (ex. xlsxwwriter)
* urllib3 (rllib3)
* simplejson (simplejsn)
* requests-toolbelt (requests-toollbelt)
* discord-webhook (disocrd-webhook)
* discord-py (discod-py)
* websocket-client (weebsocket-client)
* openpyxl (oepnpyxl)
* pillow (pilloow)
* click (clickk)
* pysocks (ysocks)
* psutil (psuil)
* gitpython (gitpythn)
* pycodestyle (pycodestye)
* prompt-toolkit (prompt-toolkiit)
* beautifulsoup (baeutifulsoup)
Edit: PyPI has removed the above!
If your company uses your own PyPI mirror, I'd recommend disallowing new packages released within the past ~week (as a general precaution, tbh).
Here’s some blunt truth — I haven't seen a single North American city with a stated policy goal of mobility "balance" that has actual street standards/designs, budgets, supporting land use decisions etc that would actually ACHIEVE mobility balance. Not yet at least. It’s usually code for some version of the status quo, only slightly better — still cars first.
Monty Python and the Search for #COVID19 Sanity.
Inspired by @penguinpete