Databases
After you install Infy, it should automatically download the AutoPagerize (AP) and InfyScroll (IS) Databases, allowing it to work out of the box on thousands of websites.
Tip: Whenever you visit a Database URL, if you click the toolbar icon to open the UI Window, you will always see a database icon appear in the top-right corner as shown above. You can hover over or click the database icon to view more information. You'll also see a Blacklist/Whitelist Button next to the Power Button that lets you blacklist or whitelist the Database URL in one click.
The databases are a user-curated list of URLs with the settings needed for Infy Scroll to provide infinite scrolling on each website. Each website is different, and a database is what allows AutoPagerize extensions and Infy to work automatically on lots of websites. Under Infy's Database Options section, you can view the database items themselves, check their stats, and see the last time they were updated/downloaded. You can also manually update/download them at any time or even delete them from your storage space if you prefer not to use them.
The single-most important setting in Infy Scroll is the Activation Mode setting (found near the bottom of the Database Options), which is set to Blacklist Mode by default. This controls if Infy should activate on all those thousands of Database URLs by default, and how you filter the URLs. Depending on how it is checked, you will have one of two types of filters: a blacklist or a whitelist. If you want Infy to work on as many websites as possible automatically, you'll probably want to keep it on Blacklist mode. If you only want Infy to automatically work on just a few websites of your own choosing, you'll want to use Whitelist mode.
When you have the Activation Mode setting set to Blacklist Mode, you'll have a Database Blacklist. This lets you allow all Database URLs by default, but specify a small "blacklist" of URLs that Infy should never auto-activate on. This mode is useful for entering in a few websites that you simply don't want to enable infinite scrolling for, or where the website no longer works right.
When you have the Activation Mode setting set to Whitelist Mode, you'll instead have a Database Whitelist. This lets you disallow all Database URLs by default, but specify a small "whitelist" of URLs that Infy is allowed to auto-activate on. This is useful if you only need Infy to auto-activate on just a few URLs. For example, you could just enter www.example.com in your Database Whitelist, and Infy will only activate itself on Example.com, assuming there's a Database URL for it. You could also have no URLs in the whitelist, and Infy simply won't activate on any Database URL whatsoever.
When you're on a Database URL and click on Infy's toolbar icon to enter the UI Window, you will either see a "Ban" (Blacklist) or "Check" (Whitelist) button next to the "Power" button. This button allows you to blacklist or whitelist this URL. This will automatically add the website's domain to your blacklist/whitelist in one click, so you don't have to manually go into the Options screen and type it in. This button is togglable, so you can click it again to un-blacklist/un-whitelist the URL as well.
You can manually enter the URLs to blacklist or whitelist in five different ways: Substring Patterns, Wildcard Patterns, Regular Expressions, Exact URLs, and Database URLs. Substring Patterns are the easiest to match against, as it only checks to see if the URL contains the pattern/text you enter anywhere in it.
The table below provides an example of each type:
| Type | Example | Description |
|---|---|---|
| Substring Pattern | www.example.com/page |
This will match any URL that has the string www.example.com/page anywhere in it |
| Wildcard Pattern | *example.com/*/page* |
As indicated by the * characters in it, this is a wildcard pattern that will match any URL that has example.com in it followed by any sub-path (the /*/ part) that is then followed by page
|
| Regular Expression | /^https?://www\.example\.com/page/ |
As indicated by the surrounding / characters, this is a Regular Expression with each . escaped by a \ to match it literally, e.g. \.com
|
| Exact URL | "https://www.example.com/this-exact-page" |
As indicated by the surrounding " characters, this is an Exact URL that will only match this one (single) URL |
| Database URL | (^https?://.) |
As indicated by the surrounding ( ) characters, this is a Database URL that will only match the generic database URL ^https?://. so you can disallow it specifically from ever being used while still allowing all the other Database URLs that would have otherwise matched the generic regular expression |
JavaScript treats \ (Backslash) as an escape character when it is inside a String ("...") and so to display \ literally (as it's commonly used in regular expressions), it needs to be entered as \\. When entering URLs in your Blacklist/Whitelist, however, you are not entering them enclosed in Strings, so please do not escape them with that extra \. Notably, the Options Screen's Database Items dialog displays them like this, so please do not copy Database URLs from the dialog in your Blacklist.
For example ...
This is incorrect:
^https?://.*(showthread\\.php\\?|forum|threads?)
This is correct:
^https?://.*(showthread\.php\?|forum|threads?)
Inside the AP Database are what's known as generic (short) URL patterns that cover a wide range of URLs -- essentially, any URL that starts with http. You may wish to exclude these generic http Database URLs inside your Blacklist, as they sometimes get the wrong page element or prevent you from getting to the bottom of the page and see content you care more about (such as seeing the comments below a blog post, rather than seeing the next page's blog post).
Here's a selected list of the Generic Database URL Patterns you may want to outright blacklist. Parenthesis have been added for your convenience so you can copy and paste them as they are into your Blacklist:
(^https?://.)(^https?://..)(^https?://...)(^https?://.+)
I personally recommend blacklisting these URLs (or at least the first one) for a more stable experience.
When targeting generic database URLs in your Blacklist/Whitelist, you'll want to surround them in ( and ). So, for example ^https?://. would become (^https?://.). This lets you exclude just the one database URL ^https?://. specifically without excluding every other database URL that matches the generic regular expression.
Infy lets you specify how often it should auto-update the database, from 1-7 Days. It's recommended to keep this at 1 or 2 days, as websites can change their settings at any time. You can set it to 0 to disable auto-updating.
Infy uses the following locations to download the databases. If your databases appear to be empty, please check to make sure you can access the following locations. It may be that your ISP has blocked access to them, or even your browser (for example, Firefox is now blocking requests to non https URLs, such as wedata).
- https://cdn.jsdelivr.net (may redirect to jsdelivr.com)
- https://cdn.statically.io (may redirect to statically.io)
- http://wedata.net
If you'd like to add a new URL to the databases (or update one that is no longer working), you can contribute to them on the Wedata.net website.
The Databases are located at:
Important: The AutoPagerize (AP) Database is currently only compatible with the Next Link action and Element append mode (not including Element Iframe) and only uses XPath and Regular Expressions. An AP database item typically only uses three keys: url, nextLink, pageElement, (and, optionally, insertBefore). Consider contributing to the AP Database when your settings are compatible with it so that it benefits other apps that use it. Otherwise, you can contribute items to the InfyScroll (IS) Database (especially if they use Infy Scroll-specific settings like Click Element and AJAX).
The Login API that Wedata uses is OpenID, which is unfortunately slowly being phased out. However, there are still a couple of OpenID providers available that you can use to create an account. Although not intended for this purpose, the provider I last used and recommend is this one: https://openid.dbcls.jp/
If you know a little XPath and would like to help out, I hope you'll consider contributing!