Probably old, but there is an embedded [WayBack] css color picker – Google Search that on each refresh switches colours:
–jeroen
Posted by jpluimers on 2021/08/12
Probably old, but there is an embedded [WayBack] css color picker – Google Search that on each refresh switches colours:
–jeroen
Posted in Color (software development), CSS, Development, Google, GoogleSearch, HTML, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/08/11
Using [WayBack] Free Clocks for Your Website, I created this clock for a 1920×1080 web dashboard which is a web page hosted on [WayBack] raw.githack.com with an iframe hosted at www.timeanddate.com
I know that is a risk, but that is OK for now: that site has existed for a very long time and probably will last a while.
There is a truckload of options you can use, despite the clock being simple. Luckily the [WayBack] FAQ: Free Clocks for Your Website explains these options.
This is the gist of the above “this clock” page:
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta http-equiv="content-type" content="text/html; charset=UTF-8"> | |
| <meta name="robots" content="noindex, nofollow"> | |
| <meta name="googlebot" content="noindex, nofollow"> | |
| <style type="text/css"> | |
| body { | |
| margin: 0; /* override browser setting for body `margin: 8px;` */ | |
| overflow: hidden; /* remove scroll bars; does not work for iframes */ | |
| } | |
| .box { | |
| float: left; | |
| width: 100vw; /* Firefox/Chrome outside Mac OS X: force viewport-width */ | |
| overflow: hidden; /* remove scroll bars; does not work for iframes */ | |
| background-color: azure; | |
| } | |
| iframe { | |
| border-width: 0; /* override browser setting for iframe `border-width: 2px; */ | |
| height: 100vh; | |
| width: 50vw; | |
| } | |
| .clock_iframe { | |
| float: right; | |
| height: 30vh; | |
| width: 16vw; | |
| } | |
| </style> | |
| <title>Clock in frame</title> | |
| </head> | |
| <body> | |
| <div class="box"> | |
| <iframe class="clock_iframe" src="https://freesecure.timeanddate.com/clock/i6xvy9ve/n16/szw300/szh300/hoc000/cf100/hgr0/fiv0/fas34/fdi74/mqv0/mhc000/mhs3/mhl20/mhw1/mhd84/mmv0/hhs1/hms1/hsc000/hss1" frameborder="0" width="300" height="300"> | |
| <!– https://www.timeanddate.com/clocks/free.html –> | |
| </iframe> | |
| </div | |
| </body> | |
| </html> |
–jeroen
Posted in CSS, Development, HTML, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/07/06
Even though RIVM twitter-care did not respond at all on my raised issue that the production environment leaded an acceptation environment URL, it did gain me some knowledge on their systems and the (then upcoming) European QR code systems.
[Archive.is] Jeroen Wiert Pluimers on Twitter: “Onhandig op de #CoronaCheck site van het @rivm de link hier (1) wijst nog naar de acceptatie omgeving en daar heb je authorisatie voor nodig. Zonder “.acc” werkt het ook niet: (2) Dit werkt wel: (3) CC @locuta… “
The problem digging into it was that it only reproduces when inside the [Archive.is] Coronacheck Print Portaal after you have logged on via DigiD, so you cannot save it in the WayBack machine nor Archive.is.
This print portal isn’t a straightforward hierarchy of web-pages, but an actual Vue.js app that injects itself into [Wayback/Archive.is] nl-covid19-coronacheck-website/index.html at main · minvws/nl-covid19-coronacheck-website and dynamically changes the URL depending on the application state.
It also means that you cannot archive pages like coronacheck.nl/nl/print/vaccinatie-ophalen or coronacheck.nl/nl/print/keuze-papieren-bewijs as the Vue.js app will not understand state from those sub-URLs and go back to coronacheck.nl/nl/print/
The only other results of [Wayback] “acc.coronacheck.nl” – Google Search were:
I had a hunch the CoronaCheck code would be open source, though finding it through the most obvious [Wayback] open source coronacheck app – Google Search failed. Since the web-site and app look very similar to the CoronaMelder web-site and app, I tried [Wayback] open source coronamelder app – Google Search and found the page with links: [Wayback] Colophon – Stop the spread of the coronavirus, download CoronaMelder.
Note that [Wayback] Open-Source Project Corona-Warn-App is a different beast. Though internationally available and released way earlier than the Dutch apps, the Dutch government has a huge ego (maybe even abbreviatable to Hugo) resulting in severe “not invented here” syndrome despite having had to be bailed out when “code black” happened in hospitals.
One thing that I learned is that there is one version of the code behind coronacheck.nl/nl/print/print-vaccinatie in the main branch of github.com/minvws/nl-covid19-coronacheck-website that has only acceptance URLs. They are in these locations:
Apparently, replacing these with production URLs is done during deployment, but I could not find the code that does it in the main repositories at [Wayback] github.com/minvws
One answer to my tweet was [Archive.is] Joel Haasnoot on Twitter: “gir.st/blog/greenpass.html… “ which provides more information on the European
These are the links I thought were interesting:
–jeroen
Posted in Development, JavaScript/ECMAScript, Scripting, Software Development, Vue.js, Web Development | Leave a Comment »
Posted by jpluimers on 2021/06/02
Almost every company I know has more than one subdomain, but while researching why support.microsoft.com could not be archived in the WayBack machine, I realised how many they have and bumped into a few sites listing most of them:
All via microsoft.com subdomains – Google Search.
–jeroen
Posted in Development, DNS, Internet, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/06/02
I run in too many sites that keep creating new cookies, but never delete the old ones, ultimately leading to 5xx errors.
Every site should have a page like [WayBack] web.archive.org/cleancookies.html that cleans non-current cookies.
So I copied toe source to [WayBack] Copy of https://web.archive.org/cleancookies.html · GitHub for inspiration to look at.
–jeroen
Posted in Development, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/05/12
Quite a while back, @NS_Online (Dutch railroads) did not accept plus signs in email addresses. I verified a few times over the years and not much progress.
This is a reminder to myself to re-check.
Edit 20230418: it has started working, see further below.
Below the fold the Twitter thread that started with [WayBack] Jeroen Pluimers on Twitter: “Toch jammer dat @NS_online valide email adressen met een plus-teken erin weigert.… “
Hopefully by now they retraced themselves from the bad company of many other parties failing to adhere to clear and long existing internet standards: [WayBack] User:Me at work/plushaters | Mozilla Community | FANDOM powered by Wikia.
Their web care team and their developers made some very inexcusable assumptions there:
Some links on email addresses and their validity:
Posted in Development, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/05/11
I wonder how you can programmatically open a Hangouts link from Chrome?
These dit not help:
So did some more digging.
TL;DR: did not find a solution; so any help is appreciated.
I found the IDs of then in [WayBack] extensions/common/constants.cc – chromium/src.git – Git at Google
namespace extension_misc { const char kPdfExtensionId[] = "mhjfbmdgcfjbbpaeojofohoefgiehjai"; const char kQuickOfficeComponentExtensionId[] = "bpmcpldpdmajfigpchkicefoigmkfalc"; const char kQuickOfficeInternalExtensionId[] = "ehibbfinohgbchlgdbfpikodjaojhccn"; const char kQuickOfficeExtensionId[] = "gbkeegbaiigmenfmjfclcdgdpimamgkj"; const char kMimeHandlerPrivateTestExtensionId[] = "oickdpebdnfbgkcaoklfcdhjniefkcji"; const char kProdHangoutsExtensionId[] = "nckgahadagoaajjgafhacjanaoiihapd"; const char* const kHangoutsExtensionIds[6] = { kProdHangoutsExtensionId, "ljclpkphhpbpinifbeabbhlfddcpfdde", // Debug. "ppleadejekpmccmnpjdimmlfljlkdfej", // Alpha. "eggnbpckecmjlblplehfpjjdhhidfdoj", // Beta. "jfjjdfefebklmdbmenmlehlopoocnoeh", // Packaged App Debug. "knipolnnllmklapflnccelgolnpehhpl" // Packaged App Prod. // Keep in sync with _api_features.json and _manifest_features.json. }; // Error returned when scripting of a page is denied due to enterprise policy. const char kPolicyBlockedScripting[] = "This page cannot be scripted due to an ExtensionsSettings policy."; } // namespace extension_misc
The odd thing is that the source does not match the Chrome web store designation:
Hangouts ExtensionId Source name Web store name nckgahadagoaajjgafhacjanaoiihapdkProdHangoutsExtensionIdGoogle Hangouts ljclpkphhpbpinifbeabbhlfddcpfddeDebugGoogle Hangouts (Extension, Beta); GOOGLE CONFIDENTIAL – FOR INTERNAL USE ONLY ppleadejekpmccmnpjdimmlfljlkdfejAlphaGoogle Hangouts (Extension, Debug) eggnbpckecmjlblplehfpjjdhhidfdojBetaGoogle Hangouts (Extension, Alpha) jfjjdfefebklmdbmenmlehlopoocnoehPackaged App Debug404 error knipolnnllmklapflnccelgolnpehhplPackaged App ProdGoogle Hangouts; Hangouts Chrome App is deprecated. Please switch to the Hangouts Chrome Extension.
You can not start the extensions in a tab; they need to start their view through the extension.
So these links do not work:
chrome-extension://nckgahadagoaajjgafhacjanaoiihapd/mainapp.html?uv_main_windowchrome-extension://ljclpkphhpbpinifbeabbhlfddcpfdde/mainapp.html?uv_main_windowchrome-extension://ppleadejekpmccmnpjdimmlfljlkdfej/mainapp.html?uv_main_windowchrome-extension://eggnbpckecmjlblplehfpjjdhhidfdoj/mainapp.html?uv_main_windowchrome-extension://jfjjdfefebklmdbmenmlehlopoocnoeh/mainapp.html?uv_main_windowchrome-extension://knipolnnllmklapflnccelgolnpehhpl/mainapp.html?uv_main_window–jeroen
Posted in Chrome, Development, Google, GoogleHangouts, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/02/26
Reminder to check out the results of this thread: [WayBack] Thread by @jpluimers: “Jammer dat het Privacy Statement op mijnlumc.lumc.nl/mijnlumc/?#/co… als een pop-up zichtbaar is, waardoor je het niet volledig kunt afdrukk […]”.
Related:
Thread:
Jammer dat het Privacy Statement op mijnlumc.lumc.nl/mijnlumc/?#/co… als een pop-up zichtbaar is, waardoor je het niet volledig kunt afdrukken of als PDF opslaan.
Vreemd ook dat de tekst op lumc.nl/12367/ anders is dan in de consent hierboven.
Kan @LUMC_Leiden dat oplossen?
–jeroen
Posted in Chrome, Development, LifeHacker, Power User, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2021/02/17
If your company manages your own infrastructure, be sure you have monitoring on all levels.
It saves you from customers discovering issues like this: [WayBack] Thread by @jpluimers: “The @EmbarcaderoTech docwiki is down due to an error in duobook2.[…]”:
The @EmbarcaderoTech docwiki is down due to an error in duobook2. URLs pointing to wiki content fail, no matter the product. Examples for Rio and XE2 grabbed from docwiki.embarcadero.com/Libraries/Rio/… and docwiki.embarcadero.com/Libraries/XE2/…
![]()
This is the #1 reason for allowing archival of all your product documentation web-content in the @internetarchive, even for non-current products, as now only parts that have been allowed to save in the past are available.Apart from nobody noticing the outage yet, which is bad in it’s own way, I hope the cause is not somebody fiddling with duobook (3 year old and unmaintained) without testing the consequences. As that would make the cause of the outage embarrassing.
[WayBack] https://github.com/ElectricVersion/DuoBook
Finally it is rather odd to get a HTTP 200 SUCCESS code on a failure. A HTTP 500 or 503 would be far more appropriate.
I wonder if that is a @mediawiki thing; maybe they could shed some light on that.
References en.wikipedia.org/wiki/List_of_H… and en.wikipedia.org/wiki/List_of_H….
The cool thing is that the stack traces teach you a lot about how a framework is structured.
Related:
Exception encountered, of type "ArgumentCountError" [6a5b64d3a502a9acff148fe1] /Libraries/Rio/en/Main_Page ArgumentCountError from line 420 of /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php: Too few arguments to function DuoBook2Template::displayPrefs(), 0 passed in /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php on line 99 and exactly 1 expected Backtrace: #0 /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php(99): DuoBook2Template->displayPrefs() #1 /var/www/html/shared/BaseWiki27/includes/skins/SkinTemplate.php(248): DuoBook2Template->execute() #2 /var/www/html/shared/BaseWiki27/includes/OutputPage.php(2335): SkinTemplate->outputPage() #3 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(743): OutputPage->output() #4 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(509): MediaWiki->main() #5 /var/www/html/shared/BaseWiki27/index.php(43): MediaWiki->run() #6 {main}
Exception encountered, of type "ArgumentCountError" [d3d353581c3915881b976ab6] /Libraries/XE2/en/Main_Page ArgumentCountError from line 420 of /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php: Too few arguments to function DuoBook2Template::displayPrefs(), 0 passed in /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php on line 99 and exactly 1 expected Backtrace: #0 /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php(99): DuoBook2Template->displayPrefs() #1 /var/www/html/shared/BaseWiki27/includes/skins/SkinTemplate.php(248): DuoBook2Template->execute() #2 /var/www/html/shared/BaseWiki27/includes/OutputPage.php(2335): SkinTemplate->outputPage() #3 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(743): OutputPage->output() #4 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(509): MediaWiki->main() #5 /var/www/html/shared/BaseWiki27/index.php(43): MediaWiki->run() #6 {main}
–jeroen
Posted in Development, DevOps, Infrastructure, Power User, Software Development, Web Development | Leave a Comment »