TabLister

The latest releases:

... more details:

This is a Web Extension that is meant to help store browser windows & their tabs.

When you have multiple windows with multiple tabs, you can, with the help of Tablister:

Important note regarding Storage (Saving Windows & Tabs), Data, & Privacy

Saving data happens in your browser (using LocalStorage), Tablister (and I) never see that.

Saving a webpage with Windows & Tabs requires no authentication & no account. That data is located at a hard to guess -- but not impossible to find -- location.

If you never Save to Webpage all data is on your hardware & is never sent to Tablister.com

If you save information to create a webpage that data is encrypted and sent to Tablister.com; again, though, it is saved in an obscure way NOT a secure way.

This is intentional & meant to lower the barrier to dealing with lots of tabs and being able to easily share lots of tabs.

The goal of Tablister is not to be a vault for secure and private storage.

Lastly, all usage of Google Analytics has been removed in V2. And the account to access analytics for V1 has been closed.

[1] This means reopening the extension will show these when clicking "show saved links & webpages", but they're never sent to a remote host. [2] This means your data is posted, with encryption, to a remote host. There are no accounts & no authentication. Just obscure URLs. [3] At some point, a Setting to have that plain text use Markdown will happen.

Browser Support

In some ways, 2017 made Web Extension way easier to develop for multiple browsers.

Chrome, Safari, & Firefox are currently supported. (Edge may be soon, too.)

Distribution is a pain from each browser vendors official distribution channel, with the exception of Chrome.

Apple had -- maybe it's better now -- an arduous, inconsistent (no way to check status, or replace a build after submission but before a review started). Now that process is more like the one for iOS apps, and therefore a costly process ($99 / year) for a free extension.

So, for those reasons, the home page at https://tablister.com is the best place to get the latest version & ongoing support for all but Chrome, might be dropped in the near future. That's not meant to be an edorsement of Chrome, it's just likely that until I have time to learn how to port to Safari & until I find an easier way to port to Firefox, those won't get much attention.

There's a lot more I'd like to do:

But first there's a lot that needs to be fixed & improved:

Under the Hood (stuff most people won't care about)

The extension is not super complex by any means, but because browsers had completely different technology (addons vs plugins vs web extensions) when I started; I've used a task manager to build distributions. That started with Grunt & now is done with webpack. The nature of extension across all browsers is awesome and way more consistent than it used to be, but the way this extension gets built I have the option to customize or change any of the targeted browsers.

One nuance is that there is integration with the website, https://tablister.com, to store data when a user elects to do so.

So webpack compiles JS for the extensions, and for the website.

And, where it gets really interesting is that when you've installed the extension and are viewing a page on https://tablister.com, e.g. https://tablister.com/save/1234567890, the extension injects another piece of "built" JS in to those webpages. This is done so that viewing a webpage with the extension available has functionality that could only exist in the extension. For example, a single click to restore multiple tabs cannot be done without the injected JS (think popup blocker). Other features are also available for the same reason.

Addons, plugins, extensions have always been HTML (or something called XUL), CSS & JavaScript. So the core functionality in the JS was originally built with "native" JS, leveraging APIs provided by the browsers; and with help from jQuery. jQuery is still awesome. But the current version has been completely rebuilt leveraging React.

My vested interest in working on this is more about learning and implementing things I don't get to use at my day job -- even more than helping reducing browser chaos. At any point in time I might have Safari & Chrome with several windows open in each, with several tabs open in each.