@cthisbear :-
[Slightly "off-topic", I know, but I think I'm allowed to these days..!] 
If you want to try the 'portable' SlimJet, Chris, do be aware that both versions are running with the --no-sandbox option.
This was the very last browser I gave the 'portable' treatment to; as always, it was Flashpeak's insistence that the launch wrapper must be called "flashpeak-slimjet" that was throwing me out.....and as usual, I was overthinking it.
The 64-bit version presented slightly more of a challenge. I normally employ a pair of wrappers, one for older Pups where the built-in 'lib' directory is needed, the other for more recent Pups where the built-in system libs are newer, so would conflict. Each of these has a slightly different name. Most of the clones are quite happy with this, but Flashpeak say the wrapper must always have the specified name.....and you can't have two identically-named files in the same location, 'cos Linux doesn't allow that, does it? 
So, the two wrappers are kept in a sub-directory, and at launch time, the appropriate one is copied out to the main directory & renamed just prior to firing Slimjet up. Slightly fiddly, but it does seem to work!
If anybody really wants Slimjet-portable64 with full sand-boxing enabled, it wouldn't be too hard to build a "run-as-spot" variant, along the same lines as the Google-Chrome one....
(If you have an existing profile you want to use, just drop it into the top level & re-name it to "PROFILE". Slimmie should pick it up and use it automatically; otherwise, just launch Slimjet, and a new one will be automatically created & sym-linked inside /slimjet at run-time.
You also have the ability to add a Menu entry from wherever your portable is located.....IF you want one)
(*shrug...*)
Mike. 