Slack Is Shutting Down Its IRC Gateway

Slack, a team collaboration communication service, has updated its IRC support page to note that it is ending support for IRC on its platform: Unfortunately, support for gateways is ending. Starting on May 15th, it will no longer be possible to connect to Slack using the IRC and XMPP gateways. In another support page, which requires you to log in to one of your Slack groups, the company elaborates: As Slack has evolved over the years, we’ve built features and capabilities — like Shared Channels, Threads, and emoji reactions (to name a few) — that the IRC and XMPP gateways aren’t able to handle. Our priority is to provide a secure and high-quality experience across all platforms, and so the time has come to close the gateways. Please note that the gateways will be closed according to the following schedule: March 6, 2018: No longer available to newly-created workspaces; April


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/LV9lsi2cTVQ/slack-is-shutting-down-its-irc-gateway

Original article

Amazon Opens Registration For .BOT Domain Name

Amazon began accepting registration requests for .BOT domain name from the public this week as the e-commerce giant comes to realize the potential of the top level domain name it secured rights for two years ago. For now, Amazon is keeping the registration for .BOT domains limited. “Creators with published bots who use Amazon Lex, Microsoft Bot Framework and Dialogflow can validate a bot and register a .BOT domain name,” the company said, noting that the limited registration phase would end on March 30, 2018. At the time of registration, Amazon requires users to sign into their Amazon account and validate their published bot.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/SXqWGE4iIe0/amazon-opens-registration-for-bot-domain-name

Original article

HTTP 103 – An HTTP Status Code for Indicating Hints

The Internet Task Engineering Group (IETF) has approved the new HTTP status code 103. The new status code is intended to “minimize perceived latency.” From the circular: It is common for HTTP responses to contain links to external resources that need to be fetched prior to their use; for example, rendering HTML by a Web browser. Having such links available to the client as early as possible helps to minimize perceived latency. The “preload” ([Preload]) link relation can be used to convey such links in the Link header field of an HTTP response. However, it is not always possible for an origin server to generate the header block of a final response immediately after receiving a request. For example, the origin server might delegate a request to an upstream HTTP server running at a distant location, or the status code might depend on the result of a database query. The


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/yLm3EevD-gw/http-103---an-http-status-code-for-indicating-hints

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: