[coral-users] So, no more nyud.net?

[Ant]

Is it confirmed to be dead now? Thank you in advance. :(

[Mike Freedman]

Yes, unfortunately, the DNS multi-tenancy of our deployment platform is
no more, so things stopped working.

Post by Ant
Is it confirmed to be dead now? Thank you in advance. :(

[Ant]

Bummer and thanks. Is there another service that can cache fully too? I
know Google can, but not good as Coral. :(

Yes, unfortunately, the DNS multi-tenancy of our deployment platform is no
more, so things stopped working.

Post by Ant
Is it confirmed to be dead now? Thank you in advance. :(

[Dr.Flay]

Such a shame, but understandable with the shift to HTTPS it will have less and less use anyway.
It was a great help to freedom of speech, and I recommended it to a UK politician whose blog was under a DoS attack.
There was obviously a painful delay in her site being viewable again, but once it started to cache and propegate I gave her a link via twitter.

The ability to use a cache only when needed was also one of Corals greatest features, as the alternatives require some level of admin so are beyond many "normal" users.

As we go into a hellish world of IoT insanity, I wonder if it would not be wise to approach the EFF with a view to creating a Coral replacement that has similar backing as the HTTPS Cert initiative (=infrastructure and man-power).
I am getting sick of seeing Cachefly connection errors, and a failure to retrieve something actually cached.
So far I have seen only 1 cached site served from Cachefly. All other times I see a page showing the broken chain at step 1.

Freedom of speech and DDoS are hot topics we will be hearing a lot more of, and we may need a new Coral more than we ever did before.

I have spoken about CoralCDN on my radio show in the past, and next Friday I guess I will be reading it's obituary.
Mike, if there is a song that reminds you of Coral, or what it meant to you to work on something so long, I would like to play it on my show (we have a free hand to play anything).

Cheers for the years.

----- Original Message -----
From: "Mike Freedman" <***@CS.Princeton.EDU>
To: "Ant" <***@zimage.com>
Cc: <coral-***@cs.nyu.edu>
Sent: Sunday, December 04, 2016 6:41 PM
Subject: Re: [coral-users] So, no more nyud.net?

Post by Mike Freedman
Yes, unfortunately, the DNS multi-tenancy of our deployment platform is
no more, so things stopped working.

Post by Ant
Is it confirmed to be dead now? Thank you in advance. :(

_______________________________________________
coral-users mailing list
http://cs.nyu.edu/mailman/listinfo/coral-users

[Mike Freedman]

Post by Dr.Flay
Such a shame, but understandable with the shift to HTTPS it will have less and less use anyway.
It was a great help to freedom of speech, and I recommended it to a UK politician whose blog was under a DoS attack.
There was obviously a painful delay in her site being viewable again, but once it started to cache and propegate I gave her a link via twitter.
The ability to use a cache only when needed was also one of Corals greatest features, as the alternatives require some level of admin so are beyond many "normal" users.

I personally use CloudFlare now for these types of use cases. Our
deployment never could stand up to the levels of DDoS attacks that have
become the norm. In the end, it's ultimately become about aggregate
network capacity. That does require the website owner to control their
DNS, however.

Post by Dr.Flay
As we go into a hellish world of IoT insanity, I wonder if it would not be wise to approach the EFF with a view to creating a Coral replacement that has similar backing as the HTTPS Cert initiative (=infrastructure and man-power).
I am getting sick of seeing Cachefly connection errors, and a failure to retrieve something actually cached.
So far I have seen only 1 cached site served from Cachefly. All other times I see a page showing the broken chain at step 1.
Freedom of speech and DDoS are hot topics we will be hearing a lot more of, and we may need a new Coral more than we ever did before.

For what it's worth, I'm also an advisor to the company behind
Blockstack, as it's ex-Princeton folks. It's also not about caching
random webpages, but is a new way to build secure applications and web
content without even dedicated servers (and address some of the https
issues you mention above, which CoralCDN could not).

https://blockstack.org/

Post by Dr.Flay
I have spoken about CoralCDN on my radio show in the past, and next Friday I guess I will be reading it's obituary.
Mike, if there is a song that reminds you of Coral, or what it meant to you to work on something so long, I would like to play it on my show (we have a free hand to play anything).

Thanks for the good wishes :)

Post by Dr.Flay
Cheers for the years.
----- Original Message -----
Sent: Sunday, December 04, 2016 6:41 PM
Subject: Re: [coral-users] So, no more nyud.net?

Post by Mike Freedman
Yes, unfortunately, the DNS multi-tenancy of our deployment platform is
no more, so things stopped working.

Post by Ant
Is it confirmed to be dead now? Thank you in advance. :(

_______________________________________________
coral-users mailing list
http://cs.nyu.edu/mailman/listinfo/coral-users

_______________________________________________
coral-users mailing list
http://cs.nyu.edu/mailman/listinfo/coral-users