Archive for the ‘Chrome’ Category
Posted by jpluimers on 2020/04/17
Reminder to self:
Some 5 years after the .zip top-level domain got live, I wonder if there are any domains in it.
Currently, it screws up non-quoted searches in browsers like Chrome, so I wonder if this still holds: .ZIP URLs (or, Why You Should Block Domains on a TLD That Doesn’t Have Any) | Blue Coat
When writing this, there was one domain (nic.zip) and two registrars.
–jeroen
Posted in Chrome, Google, Power User | Leave a Comment »
Posted by jpluimers on 2019/12/30
Boy, I totally missed this was possible: [WayBack] How to text from your computer with Android Messages – The Verge
Texting from the web gives you a lot more flexibility in how and where you can continue conversations. Here’s how to set it up and get started.
…
- Make sure you’ve got the latest version of Android Messages installed on your phone.
- Go to messages.android.com on the computer or other device you want to text from. You’ll see a big QR code on the right side of this page.
- Open up Android Messages on your smartphone. Tap the icon with three vertical dots at the top and to the far right. You should see a “Messages for web” option inside this menu. If you don’t, just give it some time. Google is rolling out the feature gradually to everyone over the next week.
- Tap “Scan QR code” and point your phone’s camera at the QR code on your other device. In less than a second, your phone will vibrate and the two will be linked up. You should notice your conversations show up in the left column of the browser window. Google says that “conversation threads, contacts, and other settings will be encrypted and cached on your browser.”
Note: this doesn’t mean your actual text conversations are encrypted. They’re not.
–jeroen
Posted in Android Devices, Chrome, Google, LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2019/08/16
When archiving pages in the WayBack machine, despite Privacy Badger having set to “save no cookies”, it still managed to set truckloads of cookies.
So I used the Chrome settings in chrome://settings/content/cookies to disable cookies and now everything is fine.
–jeroen
Read the rest of this entry »
Posted in Chrome, Google, Internet, InternetArchive, Power User, Privacy, WayBack machine | Leave a Comment »
Posted by jpluimers on 2019/05/27
When you get the response “web.archive.org unexpectedly closed the connection” without even returning an HTTP code, but:
- it works in anonymous mode
- it works with all extensions turned off
then likely there are too many cookies for archive.org or/and web.archive.org: in my case, I had 90 cookies.
Cleaning these cookies out resolved the problem (I used [WayBack] Awesome Cookie Manager for this).
Edit 20231230: Awesome Cookie Manager source repository at [Wayback/Archive] Phatsuo/awesome-cookie-manager: Awesome Cookie Manager.

--jeroen
Posted in Chrome, Google, Internet, InternetArchive, Power User, WayBack machine | Leave a Comment »
Posted by jpluimers on 2019/05/13
[WayBack] Where is the Chrome settings file? – Super User, on various platforms as a folder named Default under:
In Windows: %LocalAppData%\Google\Chrome\User Data\
In OS X: ~/Library/Application Support/Google/Chrome/
In Linux: ~/.config/google-chrome/
The easiest way to find out the actual location is by browsing to chrome://version/ as per [WayBack] google chrome – Disabling “Sign In ” tab on startup – Super User. There the entry Profile Path will show the actual profile location.
Inside that path is a JSON file called preferences which you can edit if Chrome is closed (since Chrome will overwrite it regularly when active).
A few entries I saw are interesting:
- Restoring the session on startup:
"session": {
"restore_on_startup": 1
},
- While running
"exit_type": "Crashed",
"exited_cleanly": true,
- After closing
"exit_type": "Normal",
"exited_cleanly": true,
A trick to restore the session after you quite Chrome is to replace "exited_cleanly":true with "exited_cleanly":false in the Preferences file.
–jeroen
Posted in Chrome, Google, Power User | Leave a Comment »
Posted by jpluimers on 2019/04/18
I still have to do this every few weeks on all my desktop machines: [WayBack] When +Google Nederland maps only fills none or part of the map tiles… – Jeroen Wiert Pluimers – Google+
When +Google Nederland maps only fills none or part of the map tiles at https://maps.google.nl, but https://maps.google.com works fine, then remove any gsScrollPos cookies from www.google.nl.
I need to do this every couple of days to keep maps.google.nl working.

Later I also found it can happen for YouTube, then did more digging for gsScrollPos and found a better workaround: [WayBack] Awesome Cookie Manager where you can just delete the gsScrollPos cookies from all sites in one go.
Even later I found out that this can be one of the causes for the WayBack machine giving an error 400 when archiving. A more common reason however is that many archived web-pages try to create cookies in the web.archive.com subdomain resulting in the same problem.
The cause seems to be the Great Suspender plugin which should be fixed by now, but might not automatically update to the latest version. See:
Pending a new Great Suspender release, below is a quick way to manually remove them if you are into SQL scripting for sqlite. It basically comes down to executing the below statement when Chrome is closed:
delete from cookies where name like 'gsScrollPos-%'
Edit 20231230: Awesome Cookie Manager source repository at [Wayback/Archive] Phatsuo/awesome-cookie-manager: Awesome Cookie Manager.
--jeroen
Posted in Chrome, Google, GoogleMaps, Internet, InternetArchive, Power User, WayBack machine | Leave a Comment »
Posted by jpluimers on 2019/04/08
For my link archive:
On uBlock, uMatrix, Personal Blocklist, Google Chrome Site Settings and others.
–jeroen
Posted in Chrome, Google, Power User | Leave a Comment »
Posted by jpluimers on 2019/01/11
For a long time, sites have been able to add themselves to the search engine list in Google Chrome.

The last one is my own, but hundreds of them are not.
I never noticed this until I needed to add some custom search engine strings to the list and found the UI is obnoxiously slow when there are hundreds of entries in that list.
It’s like the cookies editor: the editing speed decreases exponentially with the number of entries in that list.
The feature is called Tab to Search, apparently is intentional, based on the OpenSearch standard and well documented:
Many people dislike it though:
There are various ways around it documented in the last link.
This is the one I liked best: [WayBack] Don’t add custom search engines – Chrome Web Store.
Via: [WayBack] Google Chrome: Remove all ‘Other Search Engines’ – Super User who also pointed me to the script below the signature ([WayBack] Remove chrome “other search engines” · GitHub), which likely needs this change:
–jeroen
Read the rest of this entry »
Posted in Chrome, Google, GoogleSearch, Power User | Leave a Comment »
Posted by jpluimers on 2018/10/23
Cool: [WayBack] Just wanted to tell that the Google+ Optimizer now has a cross post to Diaspora – Feature…. – Ole Albers – Google+.
Get it from [WayBack] Ghosttown – Optimizer – Chrome Web Store
The Google+ – Optimizer increases the user experience with Google+ until the bitter end…
With this extension you can modify and arrange your google+ stream just like you want.
Some of the Features:
* Remove unwanted content ("suggested contacts, youtube-comments,animated gifs...)
* Display additional content (stopwatch)
* Filter by Hashtag
* Autosave-Feature
* Bookmark-Feature
... and more
The first time you open a page on plus.google.com, you see this:

Then when you post a removable information bar:

That directs you to the configuration (either right click the icon, or follow http://hurz.me/gplusoptimizer), where in the main item, you can enter your diaspora host (in my case pluspora) information:

–jeroen
Posted in Chrome, G+: GooglePlus, Google, Power User, SocialMedia | Leave a Comment »
Posted by jpluimers on 2018/10/16
tl;dr: Finding event handlers registered using jQuery can be tricky. findHandlersJS makes finding them easy, all you need is the event type and a jQuery selector for the elements where the events might originate.
I need to invest some time in using this: [WayBack] Quickly finding and debugging jQuery event handlers with findHandlersJS – The Blinking Caret
Sourcecode: [WayBack] raw.githubusercontent.com/ruidfigueiredo/findHandlersJS/master/findEventHandlers.js
References:
Via: [WayBack] javascript – Chrome Dev Tools : view all event listeners used in the page – Stack Overflow
–jeroen
Posted in Chrome, Development, Google, JavaScript/ECMAScript, jQuery, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
penguin020 commented on Dec 22, 2017 •