Am I the only one who thinks it's crazy to put all of your passwords on a companies cloud where every single one of their other customers password vaults also lives?
Aside from putting the burden for file management of the vault on the customer, help me understand how local storage (with backups) isn't the safest place to keep my passwords from being compromised.
Ghost/spam traffic is a real problem for GA. UA codes are public and can be targeted with spam referrals or simply randomly hit (especially for UA codes that end in -1).
Filtering spam and getting useful data on GA is a never ending job that Google keeps making harder. (re removal of Service Provider / Network Domain [1])
Are those fees also present for transactions that are refunded immediately before they batch (i.e. testing). Let's say a stripe IP wasn't whitelisted on the server and started being denied coming back, causing transactions to fail. If I want to do a quick live environment test on this it now costs my client money, which is not ideal.