@pluralistic PSA: #Brave has started indexing and presenting results from #grokipedia , a known #disinformation source which uses #LLMs unethically. I am very disappointed by this development; #Grok pollutes public discourse in a very #toxic way, similar to #Meta 's use of LLMs, for example. There is a way to filter these out: use the #NoGrok extension. https://github.com/403-html/NoGrok #grandtheftautocomplete #enshittification

@jcoglan Thanks for this, I am currently refactoring a legacy C++03 code base and bringing it kicking and screaming into the present. I won't be using the executors-ts for Reasons(tm) though but E and JS promise behaviour is interesting to me at the moment, my first foray into true async was hacking an HTTP server on Solaris in 1999 using async signals and FSMs. https://blog.jcoglan.com/2026/03/23/uses-for-nested-promises/

For the #FreeBSD #Google Summer of Code #GSoC 2026 programme, we now have 3 shortlistees for the #EFI MonotonicCounter project, and 1 shortlistee for #multicast snooping in #if_bridge . There is less than 36 hours until the gate closes. Be swift about it!

@pluralistic I published my workplan for FreeBSD today, you may be interested in some of the anti #enshittification clauses ca. pg4-pg5: https://people.freebsd.org/~bms/devsummit/bms-devsummit-2026.pdf And a big shout out to Ed Zitron!

OK, I made the #FreeBSD #DevSummit CFP deadline with my 2026 work plan, so it is time to look for additional funding (HPE #Juniper might be up for us finishing off #TCP AO): https://people.freebsd.org/~bms/devsummit/bms-devsummit-2026.pdf Some mention is made of #GenAI countermeasures. #freesoftware

@emilymbender I found @HalvarFlake 's take on anthropomorphization of LLMs hits nail directly on head, and provides some scentifically grounded explanation for @pluralistic 's sarcastic quip "If we teach the word guessing program enough words, maybe it will wake up": "To me, wondering if this contraption will "wake up" is similarly bewildering as if I was to ask a computational meteorologist if he isn't afraid of his meteorological numerical calculation will "wake up"." https://addxorrol.blogspot.com/2025/07/a-non-anthropomorphized-view-of-llms.html

@pluralistic @HalvarFlake seems to be recapitulating what you were saying, Cory, when you sarcastically quipped "If we teach the word guessing program enough words, maybe it will wake up": https://addxorrol.blogspot.com/2025/07/a-non-anthropomorphized-view-of-llms.html

GenAI risk management: limit #GitHub exposure and switch to #sourcehut where @drewdevault has committed to protecting developers. #Microsoft allegedly trained GitHub #Copilot on #copyleft material code, when we all know #RAG #LLMs cannot cite like humans. Potentially massive IP violation. My PhD is #ccbysa and if the RAG LLMs can't abide by the terms, then the people who are using them are in violation. And yes, I will enforce terms. There's pending case law for this. Lots and lots of it!

To migrate #FreeBSD guest VMs from #Hyper-V to #libvirt/#KVM:
* Convert to .qcow2 from .vhdx at host, using #Cloudbase.it #qemu-img.exe.
On import:
* Choose FreeBSD 14.2 as OS.
* Choose Q35 as chipset.
* Choose BIOS.
* Import disk image as #VirtIO disk; change to SCSI.
* Add missing virtio-scsi controller.
* Apply "stateless" #EFI <os> from libvirt docs, to enable EFI non-secure boot without XML schema errors.
* Boot the FreeBSD guest.
* Edit /etc/rc.conf to use #vtnet(4), not hn(4).

If you want a hard example which is everyone's daily driver now, consider Jason Donenfeld's WireGuard(tm): https://www.wireguard.com/trademark-policy/ #wireguard #bsd

PSA and IANAL: If you want to maintain control of your open source project, and the right to commercialise the fruits of your own labour, don't use the GPL; the moat is very weak Instead, incorporate in England, use a 2/3 clause BSD license, keep the really valuable stuff proprietary, and then copyright APIs. In the light of Oracle vs Google, violation in England does not enjoy the USA's "Fair use doctrine". So, you can sue when GenAI hilarity ensues: https://www.phoronix.com/news/Chardet-LLM-Rewrite-Relicense

Kudos to the #IETF finally ratifying #TLS 1.3 Encrypted Client Hello (#ECH): https://datatracker.ietf.org/doc/html/rfc9849