[1] Good Practices for Capability URLs
( ( 版))
http://w3ctag.github.io/capability-urls/2014-01-03.html
[2] Good Practices for Capability URLs
( ())
https://www.w3.org/TR/capability-urls/
[3] Good Practices for Capability URLs
( ())
https://w3ctag.github.io/capability-urls/
[4] Push API - Web APIs | MDN
( ())
https://developer.mozilla.org/en/docs/Web/API/Push_API
The endpoint for the subscription is a unique capability URL: knowledge of the endpoint is all that is necessary to send a message to your application.
[8] Telegram Bot API
()
https://core.telegram.org/bots/api
Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.
Making requests
All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:
[9] 記事の外部共有とLaTeX記法による数式表示に対応しました - Kibela Blog
()
http://blog.kibe.la/entry/2017/04/11/154057
[11] Beaker | Peer-to-peer Web browser. No blockchain required.
()
https://beakerbrowser.com/
Dat URLs are effectively unguessable and are never sent over the network, so only people you share the URL with will be able to download your site’s files.