Yes he does mention it was on an iOS device in his post. It was a bit confusing at first but I'm absolutely sure he is talking about iOS with the scheduling reminders.
183 karma · joined February 23, 2016
The web site had a black banner with white text on the top that stated in high contrast that it was the developer site and no actual transactions would run and tickets could not be purchased if a transaction was attempted here. (even was using a test domain while clearly the live site's domain was in the header)
They still required us to purchase some package to use the certificates on that site. When LE came up we were more then thrilled that we didn't have to fork out extra cash for developing on sites that don't get traffic at all and clearly stated this fact.
I will never go back to StartCom considering how they treated us that day.
It seems more like to that the approval process is strictly to whomever is approving requests at the time because I've also seen several friends get certificates for e-commerce sites that were clearly labeled as the production server and have yet to be revoked after several years of running and becoming successful.
I don't know how StartCom run's the actual process and I could have just been caught on a bad person that day but honestly when you have one bad experience humans tend to avoid going through that again since we are programmed since birth to do this. Of course Let's Encrypt has been more then what we expected and will continue to use them until such time we are required to stop using them!
Go Let's Encrypt - You got this companies support and I'm sure that of many others so don't ever stop fighting!
If you search the link on most search engine's it shows that the title is "PayPal Restores Account of Dropbox Rival Seafile After Monitoring Row"
"<title>PayPal Restores Account of Dropbox Rival Seafile After Monitoring Row - Fortune</title>"
Of course the article title in-line doesn't have that but it was probably a bad move on the developer's part to not create as much duplicated content on the page would be my guess as to why that occurred.
Either way it is very confusing I agree!
Just thought users would like a non-translated form as not everyone can spend extra time re-reading sentences to understand the exact context of the article!
edit That number is actually active users and I do apologize the number of registered accounts is estimated to be over 645 million! edit2 Actually 4.9% of the estimated accounts were "leaked" (if this is an actual twitter leak since still no official word)
This is also why I'm glad I've never used the accounts for TV and have always resorted to the number generating system (if of course the breach is related directly to the accounts)
search "Do you have a TV Account" I have yet to find an answer from someone that said No (meaning they use the numbering system- only yes, used to and "free" which still is a login). A lot of answers to include that they use the same password for the same email for various accounts. A few that don't but those numbers are very small and more than likely that user was compromised another way.
edit Of course this is speculation and as mentioned in the original post of this article we should assume this was TV being hacked versus just a simple re-used password
This breach could also be data leaked from TeamViewer but as of right now there has been no official word as far as I can see. Considering users like to use the same username and password a bot could easily run through a leaked list and report any successful logins back to an attacker (an older exploit).
As far as I can tell the random numbers being generated are not affected but users who have actual accounts are being affected. There has been no official word but the number generating system being exploited over the accounts being exploited seems far less likely. Only time will tell thought so hopefully we will get an official word soon!
edit Seeing a lot of different theories in the comments and honestly I'm not sure which one makes the best sense. I really do hope TV makes a comment soon about how it's happening but we probably won't see that announcement until they release the fixes which are supposedly later this year.
I've seen several open source systems that share on GitHub such as PadLock but have yet to be able to test these to compare to Roboform. Considering how cheap I was able to pick up Roboform to (as a college student I got 4 years for 1) I really haven't seen the urge to switch considering on how universal Siber System's Roboform does on multiple systems.
Even though this can also be a downfall if the developer's slack on one system, I have been satisfied with these guys since I started using them so many years ago and really haven't found many complaints.
edit My entire reasoning for posting was that while I'm very familiar with Roboform my experience with KeePass was always lacking compared to others.
[1] http://www.tcpiputils.com/browse/as/32934 * note there are more than average ads on this site and it's a bit plain but this was the only one I could find that, with my brief searching, showed ip prefixes associated to the AS number.
If anyone has a better lookup tool that'd be great!
edit: Should also note that since other users are mentioning they might be under multiple AS number's maybe the ticket would be to setup a GitHub that collected these AS numbers for FB.
edit 2: found a less ad filled site! http://ipduh.com Search AS32934 click "prefixes" at top
edit I had to copy and paste the link to a new browser - apparently knowing the referrer the page will redirect to a blank page.
However for a bigger enterprise they require more functionality here is a comparison of the differences between the Community and Enterprise Editions.
https://about.gitlab.com/features/#compare
Several pricing options for EE but essentially the base cost is $39 /year per user.
Totally true, I myself went thru an over use of refined sugar and non-healthy fast food choices. It was a truly terrible experience that thankfully I caught at a young age before it progressed to thousands to possibly hundreds of thousands in medical care.
Essentially I ended up having tears in my throat and ulcers at the same time causing and obscene amount of blood to, well for sake of the conversation, come back out of the body reverse style. It was due to the amount of sugar intake and "fast food" that caused me to experience this horrible scenario. I feel as though a lot of people who experience this just go, "oh I'll take some pills and I can get right back into it" which in it self will cause the problem to worsen but the general populous has for some reason come to believe that the magic pill solves all and we can rely on future technology to keep us "safe from tipping the edge"..."until it all collapses into a mess".
I honestly believe it's the fact that our culture is now bred to have things handed to them so easily. As an application/web designer I often have to create "dumbed" down interfaces that to me seem illogical and a waste of precious coding time.
While yes it sucks they don't put it in bright high contrast words on the labels, but at the same time they are putting it on the label and if we just took the time we could curb this silly notion of the big corporation is evil - even creating a core class required for students to take at various stages of school would make a phenomenal difference (in theory).
Essentially while a company may be evil, they are only evil because it's making a profit. We the people of the world need to make the change for big industry to make change because at the root of it they only do it because we keep paying!
This is becoming more and more important to me as I have ranged from the updating on nightly builds to only updating when I see real performance benefit - and even then I wait till I see more users from my model and service provider commenting on how much the change benefits them.
*edit - of course application updating is an entirely different process and I allow this to update ASAP due to unlimited data plans but updating core os features has become more and more towards the above versus the application update idea.