Added use of jsdelivr.com cdn

Author: SomajitDey

README.md

@@ -18,7 +18,7 @@ Securelay works in the following ways:
 
 **CORS:** Allowing CORS is a must. Otherwise, browsers would block client side calls to the API.
 
-**Futureproof:** The URL(s) of the API endpoint(s) may be found with a GET at https://securelay.github.io/api-endpoints.json.
+**Futureproof:** The URL(s) of the API endpoint(s) may be found with a GET at https://cdn.jsdelivr.net/gh/securelay/api/endpoints.json courtesy of [jsdelivr](https://www.jsdelivr.com/?docs=gh). This requires storing the list of URLs in JSON format in a endpoints.json file in the https://github.com/securelay/api repository. 
 
 # Security
 Security is brought about by the use of dual paths, one private and the other public. Note here that other relay services like [piping-server](https://github.com/nwtgck/piping-server), [http-relay](https://httprelay.io) or [pipeto.me](https://pipeto.me) use the same path for both GET and POST.