JdeBP

The wsconscfg problem with multiple screens, whatever it exactly is, is decidedly odd. According to this, the display is being driven as smfb0 in what is largely a dumb framebuffer mode, no acceleration, no GPU, no fancy high jinks whatsoever. wscons/wsdisplay should have no difficulty with multiple screens on that sort of thing.

The author doesn't actually cover the caveat (3 newly valid backslash escapes in BREs) at all, so that's not the case.

It isn't really primarily about organization oversight, though. The weird goings on are in practice usually at the behest of the people paying the salaries of all of the people involved (which includes law enforcement, which goes through corporate channels). There's no real independent oversight for that common case. Everyone is on the payroll. (-:

As a concrete thought experiment, consider if (say) a WWW/DNS hosting company providing such free proxy DNS service decided to covertly record the domain name lookups from the general public that fail in order to compile a list of domain names for the company to prospectively squat on. Having multiple employees handling the public service doesn't stop this if it is the company's actual business decision to sneakily do this.

It really is a statement of bus factor, not about oversight. To make a statement about oversight one has to take into account something else not covered by this list: which of the list entries has attempted to show some level of independent auditing or oversight of its data protection.

* https://blog.cloudflare.com/announcing-the-results-of-the-1-...

CloudFlare has had some independent auditing done, by an accountancy firm. DNS4EU holds itself subject to GDPR rules on Personal Data with respect to query data, and so is auditable by the Czech ÚOOÚ. AdGuard likewise, except that it holds Personal Data in Frankfurt. CZ.NIC likewise, except that it hasn't actually updated its legal doco since 2018 and it's only by implication that the Czech ÚOOÚ can audit the Personal Data handling under the GDPR. DNS.SB simply disclaims the existence of any Personal Data whatsoever, which as with AdGuard is overseen by the German BfDI and relevant Land authorities (HBDI for Frankfurt).

* https://legal-documents-dns4eu.s3.fr-par.scw.cloud/DNS4EU-Pu...

* https://uoou.gov.cz

* https://adguard-dns.io/en/privacy.html

* https://nic.cz/files/documents/20180525_Zasady_zpracovani_os...

* https://dns.sb/privacy/

* https://bfdi.bund.de/EN/Home/home_node.html

* https://datenschutz.hessen.de

Even Thomas Steen Rasmussen, who also claims zero Personal Data, would be subject to oversight by the Datatilsynet.

* https://datatilsynet.dk

The author is circling around, but not quite reaching, a statement that POSIX Basic Regular Expressions work everywhere, with the caveat that that not everyone has caught up with version 8 of the Single Unix Specification, which has slightly changed BREs.

Every time that this comes up, be it a general list like this or someone announcing a new service, my reaction, and that that I see of surprisingly many other people on Hacker News, is fairly unmoved. I've run my own proxy DNS service for about a quarter of a century at this point, using three different sets of softwares on six different operating systems, and every single point on the filter tab is something that I can (and do) just do for myself.

The list is not so much interesting for the options that it presents, as far as I am concerned, but for the things that it reveals. Every single entry that is explicitly marked 'China' also has 'operates under Chinese regulations'; which is, in 2026, something that is of concern for more than just the Chinese entries on the list, to people on my continent for starters.

'Run by one individual in Denmark.' is an interesting statement of bus factor, but I don't think that all of the other entries should be assumed to be better just because they are mute on the point. There's far less information about who is behind DNS.Watch than there is about Thomas Steen Rasmussen. And it appears that DNS.Watch went off the air at least once in recent years, so it is a legitimate concern.

Then there are all sorts of things not on this list that might matter to people, such as Quad101 looking like it has geographic restrictions on whom it is available to and Gcore being an AI company.

If your reaction is 'What the Hell is this?', read this for background:

* https://reuters.com/business/media-telecom/talk-bubble-is-an...

Then notice that the metal construction robot needs toe protectors on its boots.

Then notice that the slides have small print.

This is the same press release from the union as at https://news.ycombinator.com/item?id=48663861, and the same discussion points apply as there, including the fact that the press release is conflating 'Wikipedia Workers' and 'British-based employees at the Wikimedia Foundation'. The two are not the same.

This conflation appears to be the fault of the union. Certainly the people who write Wikipedia well know the difference between themselves and the Wikimedia Foundation staff.

Google isn't. A recent court decision in Germany laid the responsibility for the output of Google's 'AI' software, running on Google's machines, and conflating companies in pretty much this manner, squarely on Google's own shoulders.

* https://posteo.de/en/news/munich-court-google-liable-for-ai-...

Only Ritter vi is really a fork. All of the rest are clones, ground-up reimplementations not forked from the Joy+Horton code.

Of them, and discounting the extreme fringes like vi-likes that run on the BBC Micro, only STEVIE lacks :x, and its derivatives all added it in. All of the other clones from MKS onwards, even neatvi and nextvi, have :x .

* https://jdebp.uk/FGA/vi-family.html

I could have told the author that about the message of the day, thirty years ago. (-:

For the people asking what kind of DNS service this is, content or proxy: You have to look 'Bunny DNS' up in the products menu and from there follow the hyperlink to the doco.

* https://docs.bunny.net/dns

So it's content DNS service; with server-side resource record shuffling; and with JavaScript, and badly written examples that don't check the question type, just to make it weird.

I wouldn't be surprised if it is lurking in some part of (say) the TSS that you thought that you'd never have to implement.

So cycle insertion. I presume that the DLY was synthetic, and was not explicitly added to the microcode ROM.

If, as there, one swipe gesture per letter is allowable, rather than a gesture encompassing a whole word, then things like Thumb-Key become options.

* https://github.com/dessalines/thumb-key

It has a similar sort of 'It doesn't have to have 26 keys on something the size and shape of a mobile 'phone.' thinking as 8vim has, whilst raising a good 'You know 'phones worked fine with a 3 by 4 grid for 60 years, ne?' point, but adding a modern twist of 'We can swipe, in the 21st century.' to the old notion of multiple letters on a button.

There are still these people thinking outside of the typewriter-keyboard-on-a-'phone box. (-:

I should have guessed. Of course someone has done this. (-:

* https://github.com/sspanak/tt9

Mailgun's validation API, presumably the underpinnings of Pangram's, returns more than a simple yes/no validity. My educated guess is that this is part of figuring out all of those extra fields.

* https://mailgun.com/products/validate/

* https://documentation.mailgun.com/docs/validate/oas/openapi-...

I wonder how the logic worked in the previous version without early start. Was it relying upon the address calculation speed to settle the outputs really quickly? Was it inserting or stretching cycles?

That first one was not only never deleted, it was never even created in the first place. You've been misled by a redlink.

* https://en.wikipedia.org/wiki/Special:Diff/1359185792

And the second is being discussed, with at minimum 3 more days of discussion to go. It isn't pending anything yet. It only becomes pending deletion when the outcome of the discussion is a consensus to delete. Indeed, the discussion so far has a fair number of people arguing that it should not be deleted.

So still nope.

Fortunately, I don't have to write up an explanation of this, as Joy and Horton already did.

* https://ex-vi.sourceforge.net/viin/paper-7.html#section53

It's basically the answer to the question of how one does vi-like visual editing when the cursor cannot be moved to arbitrary locations on the terminal, or sometimes cannot even be moved upwards.

Amusing factoid: It's actually sort of the other way around. open mode was added to ex before visual mode was. visual mode is the answer to the question of how you can take advantage of an ability to move the cursor around arbitrarily.

* https://www.oreilly.com/library/view/learning-the-vi/1565924...

VIM and STEVIE never implemented it. VIM makes :open do the same as :visual . nvi and nvi2 issue a 'not implemented' error for the :open nex command. Watcom vi does not even have :open . Nor do NeoVIM, nextvi, neatvi, and viless.

Mortice Kern vi has open mode. So does elvis version 2.

The operating system was going to be called GNU.

Don't open this can of worms. (-: There were endless discussions of this in the 1990s. Years's worth.

Scroll down to the 'What Is the Hurd?' section of this announcement post from 1996 and pay particular attention to its first and last sentences. That's the allusion here.

* https://groups.google.com/g/gnu.announce/c/d0N2mLo5dxk/m/bDq...

Nope.

* https://meta.wikimedia.org/wiki/User:Larry_Sanger/Why_I_am_n...

Still there after 23 years.

On the other hand, some of the best is when a hoax written by a monk in the north of England some time around 1300 is debunked by late 20th century scholarship, and eventually someone makes Wikipedia no longer re-hash a propagandist revision of the Battle of Stirling Bridge re-set in Wales that stood unchallenged for almost 7 centuries.

* https://youtube.com/v/mLdB5s7-h0w

* https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...

Fun fact:

Sanger wrote the original version of that rule, and its change over the years has reflected a shift from people coming to Wikipedia in the very early years thinking that they could just do whatever the Hell they wanted, to in later years people coming to Wikipedia thinking that it is run like a legislature.

* https://en.wikipedia.org/wiki/Special:Diff/423054

There is a long history here, and if you are looking at just the WikiProject and the community ban discussion, you are missing a Hell of a lot.

Very short background:

Larry Sanger left Wikipedia in 2003.

* https://en.wikipedia.org/wiki/Special:Diff/707321

Sanger went on to set up Citizendium, a wiki encyclopaedia project organized the way that xe thought one should be organized, with an extensive rulebase and 'constables'. Sanger's edits on Wikipedia were sporadic from 2004 to 2023, and were almost exclusively focussed on Jimmy Wales's account talk page, the articles on Sanger and Wales, the article on Citizendium, and the articles on the history and criticism of Wikipedia. There was also a whole debate on whether Sanger was a co-founder or an employee.

Citizendium died 15 years ago. (Yes, you can see it now. It was resurrected in 2022, everyone having to start from scratch with new accounts.) I actually thought of getting an account there in its early years, but for several years prior to its effective death it sported an announcement that the new accounts process was temporarily not in service, come back later. The writing was on the wall for a long time.

Sanger re-gained interest in Wikipedia in 2025, but still far more interested in how an encyclopaedia should be governed, which motivated the creation of Citizendium in the first place, than in actually writing one. In the intervening years, xe had done a lot of punditry from the sidelines, concentrating everything through a lens of U.S.A. politics.

See infobox.

* https://jdebp.uk/FGA/vi-family.html#elvis (https://news.ycombinator.com/item?id=48132452)

I was just talking about a fun and largely forgotten feature of Joy+Horton vi elsewhere.

* https://mastodonapp.uk/@JdeBP/116793159030149624

You can see it here in Ritter vi on lines 83 et seq. of ex_vis.h . vi actually has three flavours of its 'open' mode, for cursor addressable video terminals, non-cursor addressable video terminals, and actual paper terminals.

There's an as-yet unfilled niche for the retrocomputeristas with genuine ADM-3s or (as someone pointed out) TI Silent 703s and suchlike to do a YouTube video showing Joy+Horton vi in its 3 open modes.

Incorrect.

:x is a vi feature, that was introduced by Mary Ann Horton to actual Joy+Horton vi in February 1980.

* https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs...

Ritter's vi is derived from Joy+Horton vi. Illumos has the original.

There was a Microsoft operating system for protected mode 80286 in 1983. It was Xenix 286; it was basically 7th Edition Unix without the branding; and it was touted as the multiuser operating system that MS-DOS would be the gateway to. How would the world look if Microsoft had won the race? (-:

This sort of thing has always been tricky. There are a number of issues at play here:

* (Mentioned in the bug report) clock resolution may not be precise enough for that part of the timestamp on some platforms.

* Counters are hard to get right, especially if multiple processes may be calling this language library function and using the UUIDs side by side somewhere. So the implementation is sidestepping the whole problem of counters by not using them.

Alas, the fix for the problem only does the GOOS == "js" test when filling in rand_a. Unfortunately, it then checks for timestamp uniqueness always using rand_a as part of the timestamp value, which is not correct. The fix needs a little more work to not end up taking the extra 12 bits of random data as part of the timestamp, and potentially incrementing them, when the timestamp only has millisecond precision.

> It can aid web crawlers in understanding the semantic structure of your site, qualifying you for richer link previews, and even potentially improving your search ranking.

This is fighting the last war, to stretch a metaphor.

As far as I and my WWW site are concerned, Google has nowadays switched to giving people lengthy LLM-generated versions of my stuff, with errors, above pointing people to my actual stuff. 'Breadcrumbs' and getting a pretty display name instead of the domain name, don't address the fact that Google de-prioritizes all of that, pretty tweaks or no, nowadays.

This is a lot of effort for stuff that people visiting my actual site directly will never see, and which people using Google will not find above the fold of its own massively LLM-ized version of stuff.