I've found it the case if you do more then one "advanced" searches using these operators, your flagged as "unusual activity" and have to do captcha to prove you not a bot.
319 karma · joined March 7, 2013
But that aside from duplicate apps, my 2nd more important point was SECURITY. An iphone user w/ phone from 2013 can still feel confident that his phone is secure , an android user from 2013 is laughably insecure.
If you use your phone for any work related sensitive data , and android phone is a huge gamble.
My last attempt at an android was a Samsung Note3 on Verizon.
Pretty much every app had 3 versions - google/android version - samsung version - verizon version
Locked bootloader so couldnt' really remove the duplicates.
Critical Security update released by a google? Well first has to be approved by Samsung ... that takes a month at least , then approved by Verizon.
Realistically if you saw the security update w/in 3 months that was pretty fast.
So a zero day exploit ... 3 months waiting for patch.
Android really won.
https://corp.delaware.gov/paytaxes/
>Foreign Corporations must file an Annual Report with the Delaware Secretary of State on or before June 30 each year.
(ie if he opened acct in Apr 2017, he'd have missed 2 filings by now)
>Besides the high rate of corporate taxation (one of the highest of all developed economies), the IRS tax code has huge penalties for noncompliance. For instance, if you intentionally disregard filing a bank reporting form (the FBAR), you’ll face serious penalties, including jail time, a $50,000 fine
Were you required to file a bank reporting form and didn't over 2 years? (ie $100k ) ??
Where is the scale balanced on this ... will it be the same in each of the different countries implemeting it?
>as long as it do not conflict with the interest of the data subject in regard to their need for data protection
Article 6.1.f
>processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.
So ... I can retain IP records in my logs , as long as they aren't a child?
Two view points to this:
1) If make to specific, big players will find a way to slip through the exceptions and game/lawyer the system
2) So vague , that only the "big players" will have the infrastructure/legal approval to actually guarantee 100% compliance. Smaller fish that the reward just doesn't justify the risk/uncertainty will certainly pull out of the market.
If the law is about "supercookies" and targeting an individual throughout the entire internet ... it should say that.
If its about the transfer/monetization of the aggregation of data ... PII being sold for money or some other in-kind transaction ... say that.
If a single entity uses a cookie and retains data for one single domain and that is ok ... say that.
If retaining logs that contain an IP Address and the logged in credentials are ok to keep for security auditing. .... say that ... if its only ok to store them for a year(??), 6 months(??) , 1 month(??) ... say fucking that!
If a company/site is aggregating PII of over a million unique users is troubling and should be specifically bound by these restrictions and need a DPO ... say that.
If a site only has a few 1,000 - 10,000 Unique PII records/users of note , and is not the focus of these regulations .... say that.
Give concrete examples, lawyer the shit out of it ... leave open for amendments so when abused can be modified.
It's just a shitty law trying to fix an already shitty situation.
Many countries outlaw face coverings as they imply correlation with lawlessness.
The direct linking of IP address as PII flies in the face of that. If I am logging IP addresses for security and to monitor against abuse, and I in fact determine that an IP address is abusive, it behooves me to have any/all data that ip address used in my system to try to identify them.
The right to be forgotten .. why just online? Why just digital?
What if a shop owner or waiter in small town notes which customer like what, or what client tips well. Which local has annoying kids that she lets wander an vandalize the store.
If that owner/waiter writes that down in a log, and shares with co-worker on next shift ... is that in violation. What if they don't write it down and just have a really good memory ... what if they just 'organically' get a reputation and word gets around.
Is old wives gossip illegal under GDPR , or the "sterotypical" Italians mothers who keep an eye out on all the kids in street and report to each other who is doing what.
Plenty of stores and bars will have a list "don't take personal checks from these people" ... are those types of lists not allowed anymore?
If the GDPR was JUST limited to "customers" or people who have explicitly created accounts that might be one thing, but over reaching to say ANY apache webserver that automatically logs IP addresses had to be GDPR compliant is absurd.
If I post a tech blog with how-tos , personal ramblings, or even example code projects I release as open source that you are completely free to use or not use ... why do I have now have some obligation to you? You chose to walk up to my storefront and look inside ... I'm free to remember whatever I want about you while you looked around.
The US passed pretty broad overreaching Computer Fraud and Abuse Act [https://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act] that many have argued is so broad that a violation of TOS could be considered abuse/hacking. If you view my site without agreeing to my TOS, should I be able to have you prosecuted?
2) What is the current business model? Is it successful? Is it making a profit?
3) What would it cost in man-hours to completely refactor code?
4) What will it cost to retrain staff on new code?
5) What will it cost to retrain clients?
6) Can you guarantee that the code-refactor will not introduce any regressions/errors that may potentially impact client level SLA (ie pissed of clients)
7) You've been there ... what 48 hrs? You completely understand all the intricacies of a code base rewrite and how will affect all inter-connected processes (both code base and other wise)
8) Your previous blog at digitalbaboon.com bemoans your unemployment status and about to be broke and not able to pay rent ... you now have a job and publicly bash your new co-workers/boss?
"What the fuck is this? Who the hell in his right mind couples view and the actual logic together anymore? Jesus, man" ...
"What the humanly shit man! No wonder this company can only hire full-stacks because no actual front-end developer would survive this blast in the face with what seems to be a double barrel shotgun."
9) In your Oct 6th post , you post " I want more stability now that I'm 25 years old and not getting any younger. Hence, I was looking for a mature place with a solid business model where to spend the majority of my time."
Guess ... what , "solid business model" means making money.
Are they making money? Were you making money before this job? Who's got it more figure out kid?
This was related to iconv() and UTF8.
This is NOT the fix for this CVE.