You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My research on building a well-covered high-speed network for the future new house with focus on effortless Wi-Fi client roaming with 802.11ax (tri-band WiFi 6E with 8x8 MU-MIMO capabilities), 3 APs, 802.11r, 802.11k, 802.11v, 802.11s, 802.11w and 10GB-compatible CAT6 Ethernet backchannel
💭 Thoughts
I want to have:
3 APs that would approximately evenly cover:
ground floor
second floor
garage space
bonus: reach some of the backyard/garden
Multipath connections between the APs
Bonded channels between the APs and the managed network switches (LACP 1+1 = 2Gbps)
A few thoughts on enabling reproducible builds with PEP 517
Huh?
I've got an idea to fill the void of the non-existent PEP 517 build requirements provisioning. The problem is that
currently there's no first-class citizen support for reproducible builds in the PEP 517 world. People usually set
lower bounds on their build backend of choice and that's about it. Even if some will set exact pins in their
pyproject.toml, it's not enough because those entries may contain unpinned (transitive) dependencies. One way to
do this with python -m build is to set PIP_CONSTRAINTS environment variable (I haven't actually tested this yet
but I expect it to work).
That workaround is suboptimal and leaves the users with no answer on how to manage the invocations and the
DNS-01 challenge hook script of uacme for Cloudflare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Freenode resignation FAQ, or: "what the fuck is going on?"
IMPORTANT NOTE:
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
Update 3 (May 24, 2021)
A number of things have happened since the last update.
Here is the best setup (I think so :D) for K-series Keychron keyboards on Linux.
Note: many newer Keychron keyboards use QMK as firmware and most tips here do not apply to them. Maybe the ones related to Bluetooth can be useful, but everything related to Apple's keyboard module (hid_apple) on Linux, won't work. As far as I know, all QMK-based boards use the hid_generic module instead. Examples of QMK-based boards are: Q, Q-Pro, V, K-Pro, etc.
Most of these commands have been tested on Ubuntu 20.04 and should also work on most Debian-based distributions.
If a command happens not to work for you, take a look in the comment section.
Make Fn + F-keys work (NOT FOR QMK-BASED BOARDS)
Older Keychron keyboards (those not based on QMK) use the hid_apple driver on Linux, even in the Windows/Android mode, both in Bluetooth and Wired modes.
The user experience of Python on a minimal Debian or Ubuntu installation is bad. Core features like virtual environments, pip bootstrapping, and the ssl module are either missing or do not work like designed and documented. Some Python core developers including me are worried and consider Debian/Ubuntu's packaging harmful for Python's reputation and branding. Users don't get what they expect.
Reproducer
The problems can be easily reproduced with official Debian and Ubuntu containers in Docker or Podman. Debian Stable (Debian 10 Buster) comes with Python 3.7.3. Ubuntu Focal (20.04 LTS) has Python 3.8.5.
I’m thrilled to finally present attrs 20.1.0 with the following changes:
bug fixes
performance improvements
JUST KIDDING!
This release is HUGE and I'm stoked we can finally get it to you! It’s the result of more than a year of development and not only does it come with many great features that users desired for a long time, it also lays the foundation for the future evolution of this package.
Some more thoughts on soluttions to problems with python's present type annotations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OpenCV's :ocv: Sphinx domain, patched up for Sphinx 2.3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters