boihlodnaglcobpellgmclfpakcboehf
While browsing product pages at Amazon, you can create an Associate link simply by clicking on the extension icon. While browsing Amazon product pages of each country with the Chrome browser, you can create a link for an associate (affiliate) simply by clicking on the badge of this extension. You can choose the size of the image and the format of the URL freely, so you can use links that match the respective characteristics of the homepage, blog, SNS etc. Please make use of it by all means. * Operation check is done only on Amazon.co.jp * In order to use it, it must be registered in the Associate Program and the Product Advertising API must be available. * We recommend that you re-create your Access Key ID and Secret Access Key when you register for a new associate in Amazon in each country or when you use PA-API v5 for the first time.
Pedigree Thief
Creates ahnentafels from Pedigree Trees (plus other tools to assist with data input to Genealogical DNA Analysis Tool). Pedigree Thief is a genealogy data gathering tool. The information gathered is intended to be imported into Genealogical DNA Analysis Tool, a program that allows you to manage your DNA matches. Please note that only English language pages are supported although the extension may function in other language sites. The extension's primary function is to read pedigree trees ( Geni and MyHeritage) and convert them to Ahnentafel. See also the included Pedigree to GedCom application that can read pedigrees from other sources. Before using for the first time, right-click the icon and select 'Help' from the menu. This will give guidance to setting up and using the extension. For further help join the Pedigree Thief Facebook group. --------------------------------- Pedigree Thief Change Log Version 3.0.25 updated 15 April 2026 - Fixed issue where Chromosome data was not collected on a MyHeritage match page. Version 3.0.24 updated 11 July 2025 - Fixed change in MyHeritage match page URL Version 3.0.21 updated 2 December 2024 - Fixed recent change in MyHeritage matches page. Version 3.0.20 updated 14 October 2024 - Added options to reading MyHeritage matches the does not involve opening the chromosome browser. Version 3.0.19 updated 9 October 2024 - Fixed GedMatch Pedigree page - P2G button now appearing. Version 3.0.17 updated 17 April 2024 - Fixed bug where sometimes PT would not read MyHeritage cM value if a whole number. - The date/time in PT's MyHeritage Matches menu will be removed once file created. - Oldest date/time will be pre-selected in dropdown. - MyHeritage Match is slow to 'fully' load, PT adjusted to allow for this as it can take several seconds. Version 3.0.16 updated 8 April 2024 - If MyHeritage data limit is reach, the browser tab no longer closes. Refreshing this tab will re-start the read (after waiting for the data limit to be restored). Version 3.0.15 updated 7 April 2024 - No longer includes masked email addresses in GedMatch downloads. - 'Save Matches' button on GedMatch, People who match both kits on both kits tab now includes the total and shared cMs for the FIRST kit. Version 3.0.13 updated 5 April 2024 - Fixed to allow for change in layout of GedMatch One-to-Many Free Limited. Version 3.0.11 updated 27 March 2024 - Fixed bug where Pedigree Thief failed to continue with MyHeritage Triangulations after pressing 'Read' button. Version 3.0.10 updated 25 March 2024 - Adjusted code to allow for slow down in receipt of Chromosome data from MyHeritage. - When reading a match on MyHeritage, PT will try automatically reading Chromosome data of shared matches before any Triangulations data. - Removed … from end of place names in P2G. Version 3.0.8 - updated 5 December 2023 - Added check to ensure info for test person is available on the MyHeritage matches page. - Fixed issue where reading Chromosome page would generate incorrect shared cMs value .(No impact on GDAT). Version 3.0.7 - updated 28 November 2023 - Minor bug fix - activity log - Fixed issue with removal of stored triangulations when read - Further fixes for MyHeritage sites where numbers use comma decimal point Version 3.0.6 - updated 27 November 2023 - Fixed ICW button in GedMatch Both or 1 of 2 page. Version 3.0.5 - updated 25 November 2023 - Updates DNA data if different from that currently stored. - Fixed issue if in comma decimal locale when reading chromosome date from a match page. Version 3.0.2 - updated 21 November 2023 - Fixed format of Matches file from GedMatch 'Matches Both or 1 of 2' from the 'Both' tab and renamed template (was GedMatch Matches with email.txt) - Fixed issue when reading chromosome browser when the data appears to be in a 'comma' decimal point format. Version 3.0.1 - updated 19 Nov 2023 Bug fixes : - Removed duplicates of Date/Times in downloads dropdowns in MyHeritage. - Fixed so only one tab of P2G created. - Fixed ICW & Triangulation output files so that they are limited by the date selected. - Fixed bug preventing GedMatch ICW from downloading file.
URL shortening tool for Amazon
You can shorten the Amazon URL. Press the button to copy the shortened URL to the clipboard. Humans can also replace this extension by handwriting the Amazon URL. This extension does not communicate with the outside world. It only works in your browser.
Historical U.S. Counties Auto-Checker
While searching Ancestry & FamilySearch, auto-checks county and place, notes boundary changes, shows historical county maps Let this tool do the location work for you as you search on Ancestry.com or FamilySearch.org. Optional upgrade for Ancestry.com users: Tree Fact-Checking and LifeMap! U.S. county boundaries have changed over 17,600 times since America was settled in colonial times. Don’t sabotage your search for ancestors by not knowing the correct county for the historical years you are researching. While searching on Ancestry or FamilySearch, this Historical U.S. Counties Auto-Checker extension for Google Chrome automatically checks that the county existed in the year you are searching, checks for valid places, warns of boundary changes, and links to historical county lines on Google Maps for the place and years you are searching! Install today and never let an ancestor fall off the map again! The Historical U.S. Counties Auto-Checker Chrome extension makes use of the award-winning RandyMajors.org’s Historical U.S. Counties on Google Maps tool, underpinned with the complete dataset of the authoritative Newberry Atlas of Historical County Boundaries. 1. Install the Historical U.S. Counties Auto-Checker Chrome extension by clicking the "Add to Chrome" button in the upper right corner of this page. 2. Go to any search form on Ancestry.com or FamilySearch.org and start typing a place and a year. As you finish typing in each box, the Historical U.S. Counties Auto-Checker Chrome extension will update information in a box as shown in the screenshots. Note that the information shown is updated based on the last year box and place box you were interacting with. 3. Read the Note and Warning messages that appear about some counties, and click the MAP link to view historical county boundaries for the place/county/state and historical year you are researching. The Auto-Checker first tries to center the map on the city/place/township you are searching for, and if it cannot find an exact match, it centers on the county you are searching for, and as a final fallback centers on the state you are searching for. 4. Using the map, when you find the correct county name for the year you are researching, put that county name in the place search box on Ancestry or FamilySearch in the form "City, County, State, USA" ENABLE TREE FACT-CHECKING & LIFEMAP FUNCTIONALITY: If you are a RandyMajors.org Monthly Contributor, the Auto-Checker will also check all U.S. location facts on Person profile pages on Ancestry trees, plus create a link to an interactive LifeMap for each ancestor! And your MAP links will open into ad-free fullscreen map windows any time you click a MAP link! LEARN MORE HERE: https://www.randymajors.org/access-ad-free-fullscreen-tools#compare That's all there is to it. Hope the tool helps you discover some "hidden" records! (When you install the Auto-Checker, you may see a standard confirmation window that states that the extension can “Read and change your data on www.ancestry.com or www.familysearch.org or www.google-analytics.com”. Rest assured that the Historical U.S. Counties Auto-Checker Chrome extension ONLY reads the place and year fields and shows the county information as shown in the screenshots above; it absolutely DOES NOT make any changes to your data whatsoever. No logins or email addresses are required to use the extension!)
No New Tabs
This extension does exactly what it says: it stops links from opening in new tabs. Whether it's an old-school link with a target="_blank" attribute or a modern site using JavaScript to spawn tabs, No New Tabs forces the content to open right where you are. THE UNBREAKABLE UPDATE (v3.0.0). Earlier versions only worked by stripping basic HTML attributes like . Version 3.0.0 now handles every technique websites use to open new tabs—it also intercepts JavaScript to keep new pages in the current tab. Temu can't get away with it anymore. Cleans Links: Strips out _blank, _new, and a bunch of non-standard targets. Blocks JS Spawning: New in 3.0.0—prevents scripts from hijacking your browser flow. White/Blacklist: If you actually want Gmail or other specific sites to open new tabs, just add them to the whitelist in the options. Or if you want to ONLY prevent new tabs from certain pages, you can configure a blacklist. AJAX Friendly: Works on sites that load content as you scroll, like Facebook or Twitter. Easily configurable: The extension popup allows you to easily enable/disable the extension, or add the current page to the whitelist. If you find a link or a script that manages to escape, let me know and I'll see if I can hunt it down. Email (available in the options page) is the most reliable way to contact me. I am very responsive Version 3.0.1 (2025/01/11) - Bugfix: Command clicking (or control clicking for you non Mac folk) should open links in a new tab, even with this extension. The previous update broke that, so this one fixes it. Version 3.0.0 (2025/12/24) - The "Unbreakable" Update: Renamed to No New Tabs. - JavaScript Handling: Finally added the ability to prevent scripts from opening new tabs/windows via JS. - Overhauled logic to handle modern web-app navigation better. Version 2.1.2 (2025/11/25) - Performance improvements - You can now use a popup from the extension to easily enable/disable the extension for the current page Version 2.1.1 (2025/9/25) - Small bugfix in fenced frames (really just an annoying log message). - Made config page dynamic, no "Save" required. So fancy. Version 2.1.0 (2025/9/19) - Significant optimizations and performance improvements. - Removed jQuery dependency, other optimizations. - Reduces memory usage and should improve page load performance as well. Version 2.0.4 (2025/9/17) - Version 2.0.3 was a rollback to version 2.0.1. - Fixed a bug in 2.0.2 which reversed the behavior of white and blacklisting, effectively breaking the extension. Sorry! Version 2.0.2 (2025/9/9) - Fixed a bug in rewriting links with rels. - Made the extension overall more robust, fixed some possible race conditions. - Made the options page prettier. Version 2.0 (2024/10/15) - Updates to manifest V3 - Big rewrite under the hood. Settings are not persisted from previous version, sorry. I do this in my spare time and I didn't have the gumption to spend more time on this than it already took to just get the basic functionality working again... Version 1.9 (2020/10/15) - Bugfix: previous version of the script did not work when the "Filter HTML forms" option was deselected. Version 1.8 (2017/12/16) Big change - Should be noticeably faster (only monitors updated/added elements on page, rather than rescanning the whole page on modification). - Added ability to enable/disable by clicking on extension button (also added a toggle in the options page). - Added the __blank (two underscores) target. - Requires fewer permissions, should be fewer corner cases that it misses. Version 1.7 (2015/11/25) - Allows the user to specify what the "_blank" target should be rewritten to (don't do this if you don't know what it means!). Version 1.6 (2015/10/25) - Now disables _blank (etc.) on the tag as well. Version 1.5 (2014/03/07) - Now works on HTML forms as well. Can be disabled in the options menu if you prefer (although please tell me why, if you do!). Version 1.4 (2013/11/6) - Exceptions can now be specified as a blacklist instead of the default whitelist. Version 1.2 (2013/7/7) - Now works with pre-rendered pages (frequently generated from Google searches). As a side-effect, now requires the webNavigation permission to know when new pages are loaded or swapped in. Version 1.0 (2013/3/9): - Now works on dynamically-loaded AJAX content. Useful for sites like Twitter and Facebook. - Added a whitelist option. - Now requires permission to view your tabs, so that I can know which page you're browsing (needed for the whitelist). Version 0.9 (2013/3/3): - Now catch rel=ext and rel=e, which are sometimes used to open new windows in javascript-based techniques. Version 0.8 (2012/7/3): - A change in the previous version meant that my script didn't operate while the page was still loading. Fixed now. Version 0.6 (2011/6/24): - Added the _newtab target Version 0.5 (2011/04/29): - Now works for file:// URLs as well. Version 0.4 (2010/10/28): - No longer needs permission to view your tabs or history (mind you, it wasn't making use of this permission before). It still needs permission to access "Your data on all websites", but there's no getting around that -- it rewrites the links on every page you browse! Version 0.2 (2010/07/21): - Now blocks the _new target as well.
