Just finished a 3 hour session (Sunday p.m.) trying my darnedest to make Wallet module function like BD adverts says it does. In my
experiences today, I tried to populate Wallet from 30 Websites. I succeeded in doing so in only 20 out of 30 attempts, a success rate
of about .6666, not a very good percentage in my opinion. Perhaps I am not doing something right, or when I installed Bdtp2016 I
did so incorrectly and not all of the program or tools downloaded or installed, or in initialized correctly,but the screen prompts tell me I
did so successfully, so;
I read the Wallet instructions to the User as telling the User (he or she) can go on the Internet, go to a Website IPL address, go to the
login page on the Website and enter the User's user ID/Email/Name and Password/Pin code) and login. Wallet feature may or it may
not confirm the login info, and adds the credentials to both the Wallet module and Fire Fox Wallet Add-on (FFWAO). But, in a third of
my attempts it has not done so. I have my own methodology, which I suspect, duplicates many Forum followers, so critique me.
First, I go to the Website and login. I do not use the FFWAO. I manually enter my user name and password from a crib sheet. In cases
(50-75%) of the time) Wallet feature does not recognize or save the login information, i.e. no Wallet splash screen When it does, I test it.
If it saved the login info in the FFWAO and Wallet module, the attempt was a success. Second, regardless, I continue the login attempt and
use the FFWAO to try and save the login info to the add-on and module. If this fails, then I count an attempt a failure. Third, a manual login
attempt without using the Wallet feature is always successful, assuming the user name and password are good to begin with. Fourth, the
Wallet feature may quixotically recognize the Website login info, after I log out, not during the actual attempt itself. Go figure.
Observation: Wallet feature seems written to "handshake"with the Website server. How this occurs I do not know, but I have noticed
that many government and banking websites have not a one step but a three step login process. (a) an introductory page, (
a login
page and © a user key to validate the login. If the Wallet feature is primed to recognize the info in only one of these steps, then failure.
If the Wallet feature picks up info on all three steps, then you get one, or two, or three info increments in both the add-on and module
entries for a web,again failure.
My concerns and priorities are: is (a) Protection (All modules), ( Privacy (Password module), and © Tools (Antitheft module). To me
everything else is secondary. Safepay module is problematic and without a working Wallet manual of no use. Antitheft module is also
not functional for reasons discussed on another thread, i.e. locators anomoly. My big concern about Bdts2016 is this: With the Wallet
problem, can I continue to safely rely on the Privacy modules, and/or Protection modules for Internet protection?
Observations, comments and critiques and help invited, mostly helpful advice.
PS: W7, FF 30.0.03
