A while back I said something on the Fediverse :

In re people bypassing infosec policies at work, I feel that infosecshould understand that "getting your job done" is everyone's firstpriority, because in this capitalistic society, not getting your jobdone gets you fired. You might get fired if you bypass IT security,but you definitely will if you can't do your work. Trying to persuadeeveryone that it's IT's fault, not yours, is a very uphill battle andnot

Recently I read Avoiding Emacs bankruptcy, with good financialhabits ( via ), which sparkedsome thoughts. One of them is that I feel that GNU Emacs is aneditor that winds up with personal customizations from people whouse it, even if you don't opt to install any third party packagesand stick purely with what comes with Emacs.

There are editors that you can happily use in their stock or almoststock configuration; this is most of how I use vim . In theory youcan use Emacs this way

Like various other filesystems, (Open)ZFS can compress file datawhen it gets written. As covered in the documentation for the'compression=' filesystem property ,ZFS can use a number of compression algorithms for this, including Zstd . The zstd compressionsystem in ZFS exposes some information about its activity in theform of ZFS kstats; on Linux, these are visible in/proc/spl/kstat/zfs/zstd, but are unfortunately a little underdocumented.For reasons beyond the scope of this blog entry I

For reasons beyond the scope of this entry, we use our Prometheussetup to monitor if we can resolvecertain external host names, by doing Blackbox probes to various DNS servers, both our internalresolvers and external ones. Ever since we added this check, we'vehad weird issues where one of our internal resolvers would periodicallyfail the check for one particular host name for tens of minutes.This host name involves a long chain of CNAME records and ends withsome A records. According to more detailed Blackbox information,

Good IMAP clients will support the notion of a prefix the clientputs on IMAP paths under some name.When I've written about this in the past ( cf ) I've been abstract about how itworked at the level of IMAP commands, and in particular at the levelof the IMAP LIST command , which lists(some of) your folders and mailboxes. The IMAP LIST command isspecial here because it has two basic arguments, which in RFC9051 are vaguely described as 'the reference

Today, I had a little unhappy experience with Thunderbird and themodern Linux desktop experience :

Dear Linux Thunderbird, why are you suddenly starting to open linksI click on in Chrome? I do not want that in the least, and yourdocumentation on how you obtain this information is nonexistent (Iam not on a Gnome or KDE desktop environment). This worked untilrelatively recently and opened in the right browser, but now it isopaquely broken.

This is an example of why people want to set computers on fire

The sensible thing to do about the plague of nasty web spiders andother abusers is to ignore it unless it's actually affecting yoursite. There is always some new SEO optimizer or marketer or (thesedays) LLM dataset collector crawling your site, and trying to blockall of them is a Sisyphean labour. However, I am not necessarily a sensible person, and sometimesI have potentially clever ideas. One of my recent clever ideas wasto look for IP addresses that requested content here using severaldifferent HTTP '

To summarize, ZFS's System Attributes (SAs) are a way for ZFS to pack a somewhat arbitrary collection ofadditional information, such as the parent directory of things and symbolic link targets ,into ZFS dnodes in a general and flexibleway that doesn't hard code the specific combinations of attributesthat can be used together. ZFS system attributes are normally storedin extra space in dnodes that's called the bonus buffer , but thesystem attributes can overflow to a spill block if necessary.I've written

Go is working on allowing people to range-over function iterators , and currently this isscheduled to be in Go 1.23, due out this summer (see issue 61405 and issue 61897 ). The actual implementationis somewhat baroque and some people have been unhappy about that( for example ).My view is that this is about bringing user-written containertypes closer to parity with the special language container types , but recently another view of thisoccurred to me.