Since I prefer verbose command-line arguments (you can find them at the [Wayback/Archive] curl – How To Use on-line man page) especially in scripts this HTTP GET request is what works with Twitter:
Note that these do not perform client side redirects, so they do not return the ultimate originating URL https://x.com/jack/status/20 (which was the first ever Tweet on what was back then called twttr) as Twitter on the client-side overwrites window.location.href with the final URL. Similar behaviour for getting the Twitter user handle of a Twitter user ID, more on Twitter tricks below.
Every now and then you make a typo when accessing remote systems through UltraVNCvncviewer.exe (I did the worst: thinking I had hit Enter to select the most recent connection, but typing a password instead).
I could not find settings in the registry, nor a vncviewer.ini file, so I used Process Monitor and filtered all events for the most recently started vncviewer.exe to figure out where it would store configuration files.
De Afdeling vernietigt de uitspraak van de rechtbank en overweegt hiertoe als volgt. Volgens de Afdeling volgt uit de systematiek van de Awb dat indien een ambtshalve beslissing om het register te wijzigen een beschikking is, het verzoek van een belanghebbende om een zodanige beschikking te nemen een aanvraag is in de zin van artikel 1:3 van de Awb. De afwijzing van de aanvraag is hiermee ook een beschikking. De ambtshalve wijziging van het Rijksmonumentenregister is een ambtshalve besluit waartegen wel kan worden opgekomen bij de bestuursrechter. Als de afwijzing van een verzoek tot wijziging niet wordt aangemerkt als een besluit op een aanvraag, dan staat tegen de weigering alleen de gang naar de burgerlijke rechter open. Dit vindt de Afdeling onwenselijk.
Migrating from Chrome to Edge was way easier than anticipated: it imported my account, bookmarks and my extensions automagically. With one exception (uBlock Origin), most of them were enabled too, apart from a few that Edge needed extra permission confirmation for and the ones that Chrome had disabled. All of these could be enabled/installed after installing uBlock Origin manually.
Then I had go to through the tedious process of re-signing in various accounts (like mail, blogging, social media, etc).
These things did not import automatically and needed manual adjustment:
As the burden on maintainers (not just Chocolatey ones) is high, not all packages get updated soon after new underlying software versions arrive.
Which means the maintainers are often very happy when an occasional user helps and preferably sends in a pull request.
That brings me to the an important point IN DOCUMENTATION DO NOT LIMIT EXAMPELS TO ONLY ABBREVIATED PARAMETERS OR VERBS as that scares away occasional and novice users of your software.
Chocolatey documentation is no exception on this, hence this blog post meant for people other than maintaining chocolatey packages on a day to day base.
I try to stay on the default shells of environments as much as possible, especially as that makes life easier when needing to work on an non-customised system.
Apple switched back from an ancient latest GPLv2 version 3.2 of bash (they regard newer GPLv3 as toxic to their revenue stream¹), introduced MIT-license based zsh and introduced a bash nag screen a few years ago forcing users to switch. Suppressing that message reliably is trickier than you might think².
This is a zsh feature that prints a percent-and-newline after a command completes if that command does not already include a newline at the end of its output. If zsh did not do this, you would either not ever notice the fact that the command didn’t print a newline – or you’d see zsh’s command prompt not start on the margin and think it was a bug in zsh.
Since the above example now writes a redirect messages (good bye HTTP, welcome HTTPS), and I very much dislike short command-line parameters, here is version with the long form of the [Wayback/Archive] curl -w or --write-out parameter :
The Wiert Corner - irregular stream of stuff 