The 90's also had ClearCase, which is quite revolutionary for its time and I guess it still is. It was a beast to maintain and IBM was making a killing in annual license fee (~3000 per license)
"In the interest of responsible disclosure I did try and contact the dev multiple ways, I was either ignored or not replied to and I feel users deserve to know what’s happening with their data."
In the interest of responsible disclosure I did try and contact the dev multiple ways, I was either ignored or not replied to and I feel users deserve to know what’s happening with their data.
"In the interest of responsible disclosure I did try and contact the dev multiple ways, I was either ignored or not replied to and I feel users deserve to know what’s happening with their data."
As you can read in the article, he did try to contact the developer.
That aside, though, when the issues are this egregious I'm honestly not sure what the right approach is. With flaws this bad it's hard to imagine that they're even capable of fixing the problems, let alone responding appropriately to the disclosure.
"In the interest of responsible disclosure I did try and contact the dev multiple ways, I was either ignored or not replied to and I feel users deserve to know what’s happening with their data."
It seems to me that this post is missing the advantages of Cloud Computing (AWS) and the Cloud Ecosystem. The Cloud is not less expensive than physical servers - it is different and a different beast. You have flexibility and a different toolset, as well the ability to start a new server without procurement.
As well, it completely disregards some of the advantages of physical servers, including in-box IO (disk) needs. Clouds have not been good in the past for high-IO apps. As well, you get more control at the expense of flexibility.
Overall - the determination of Cloud vs Physical should not be based solely on Price but needs and overall Ecosystem that you want to participate in.
Not to mention, as an independent consultant and developer, the ability to spin up a new server to play with any time is invaluable.
You can sue for any reason whatsoever - does not mean you will win.
I am sure that Verizon was smart enough to put a limitation on the time that one had to activate the service. They have very many lawyers that would never allow a deal with no end date.
But again, you buy something over 1 year ago and only activate now? Did you really need this service?
Anyhow - you should not expect people to have a special offer that never expires, you must activate it to get the benefits.
But honestly, sounds like you are crying over nothing if it is really 1 year ago that you purchased this. You are being unreasonable.
Shouldn't said lawyers have made sure there was an expiration date on the original wording of the offer? If not on the packaging then somewhere in the fine print? In the absence of one you might successfully argue that it was open-ended.
I use Verizon and they are always more than happy to activate my CDMA capable phone for use on the Verizon network - which I have been using for a very long time and live contract free this way. I also use a very old completely Unlimited plan, so buying a phone from Verizon would cancel this plan and force me on a new contract.
Anyhow my point is I have no problems adding a personal device to my plan anytime - many times.
I watched this speech near every MLK day in the US while I was growing up, I remember sitting there not understanding it as I was in grammar school.
We watched it on a large TV set that they rolled in on a cart. Granted I was in a 99% white school at the time, but the school was not for the rich - however they bought the necessary footage (I assume now, no idea).
I distinctly remember Dr. King's voice, I will not forget it.
Seems to me that melbourneit.com was the cause of these problems - that is the related link between all these different problems - basically poisoning the DNS of any popular company that uses them.
So not sure what to say, but this is the email I received from DynEct the other day:
subject: Webinar Wednesday: Are You Prepared For DNS Disaster?
sender: Dyn hello@dyn.com via dynect-mailer.net
and some info from my old whois:
$ whois twitter.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
Server Name: TWITTER.COM.GET.ONE.MILLION.DOLLARS.AT.WWW.UNIMUNDI.COM
IP Address: 209.126.190.71
Registrar: PDR LTD. D/B/A PUBLICDOMAINREGISTRY.COM
Whois Server: whois.PublicDomainRegistry.com
Referral URL: http://www.PublicDomainRegistry.com
Domain Name: TWITTER.COM
Registrar: MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE
Whois Server: whois.melbourneit.com
Referral URL: http://www.melbourneit.com
Name Server: NS1.P34.DYNECT.NET
Name Server: NS2.P34.DYNECT.NET
Name Server: NS3.P34.DYNECT.NET
Name Server: NS4.P34.DYNECT.NET
80's RCS (single user) and then CVS (multiple users)
90's CVS and then Perforce
I don't know, this is from my memory, google can fill in the gaps.