I build small free tools that answer one question and get out of the way.
Two so far: one tells you why your email is failing authentication, the other whether a supplier is real before you wire them money.
Both came from watching the same mistakes happen twice.
@avrldotdev On 6, terminals add a twist: a CJK character or emoji is one grapheme but two cells wide, and Unicode's width annex (UAX 11) says its property is not meant for modern terminal emulators without case-by-case tailoring. So the app and the terminal can disagree on a row's width.
Update 3: N-able has turned off N-central's Intune integration, hosted and on-prem, as a precaution. Its 12 Nov summary says 'no signs of compromise'; the 13 Nov entry under it says it has identified additional indicators of compromise and is working with those customers.
N-able has taken hosted N-central offline in all three regions and told on-prem customers to take theirs offline after a researcher went public with critical bugs. No CVEs named yet; a hotfix is aimed for midday EST.
The 2 Nov HF1 only fixed OS-level CVEs. It is not the fix.
Update 2: N-able is looking into new claims against HF2 itself. Its first read: the server issue needs the Legacy API turned on and exposed to the internet, and it is off by default. On-prem: check that Legacy API is off, and disable it now if it is on. Hosted is not affected.
Verisign reversed course on .name: existing email forwarding and third-level names stay. Its 5 Nov letter to ICANN sets the condition: only while at least one ICANN-accredited registrar still sells them. Ask your registrar if it will. Verisign still plans to end new sign-ups.
@techspence If the take-home repo is set to run a task when the folder opens, VS Code's docs say automatic tasks never run in an untrusted workspace, and by default it asks once more after Trust. That only covers the editor: npm install in the terminal still runs its install scripts.
@Aaronontheweb@AkkaDotNET One deployment catch: https://t.co/Eu1e1RsBeo.Quic needs Windows 11 or Server 2022+, and on Linux a separately installed libmsquic, per the .NET docs.
@svengaa@techspence Fair, it reaches further: its page says Universal CAE covers any app reached through Global Secure Access, no CAE support needed in the app. Strict mode is the replay part: a GSA token used from an IP other than the one at sign-in gets network access blocked.
The Let's Encrypt announcement (15 October, "assuming all goes well"); the quorum table is in section 3.2.2.9 of the Baseline Requirements: https://t.co/Tj3KejFNqT
Let's Encrypt plans to go from four remote validation perspectives to six tomorrow, 10 November: seven requests per challenge. The CA/B Forum rules let a CA using 6+ perspectives tolerate at most 2 failures, versus 1 with 2 to 5. Region blocks on port 80 will meet more of them.
@avrldotdev PostQUEL survives in one name: the Postgres docs say libpq was named after it. The 1994 pair were Andrew Yu and Jolly Chen, and their Postgres95 is also where psql came from, replacing the old monitor program. The 1996 rename started at 6.0 to continue Berkeley's numbering.
@inf0stache OpenAI built a guard for that callback step: ChatGPT only fetches a URL automatically if an independent crawler has seen that exact URL on the public web. A callback with the user's question in its query string is a new URL, so it is blocked or the user gets a warning first.
@jespinog That ripple also reaches the profile itself: the PGO guide requires samples to keep stack frames for inlined functions, or Go can't maintain iterative stability, its term for avoiding builds that go fast, slow, fast as optimized code stops looking hot.