* 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.
9,053 karma · joined September 29, 2014
* 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 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.
* https://posteo.de/en/news/munich-court-google-liable-for-ai-...
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 .
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.
* 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. (-:
* https://mailgun.com/products/validate/
* https://documentation.mailgun.com/docs/validate/oas/openapi-...
* 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.
* 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.
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...
* https://meta.wikimedia.org/wiki/User:Larry_Sanger/Why_I_am_n...
Still there after 23 years.
* https://youtube.com/v/mLdB5s7-h0w
* https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...
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.
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.
* 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.
: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.
* (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.
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.