Chrome apps shut down, what's the plan?

[chrisac...@gmail.com]

Got this from Google. What's the plan? Thanks.

Hello Chrome App Developer,

As we previously announced in 2016, changes in support for Chrome Apps on Windows, MacOS and Linux will begin starting March 2020. We are writing to let you know the details about this plan, along with some important updates about ending Chrome app support on Chrome OS.

What do I need to know?

Starting this year, we will no longer provide support according to the following schedule. Please note, these timelines are for Chrome Apps only, and do not impact Chrome Extensions.

Scheduled Date	Action
March 2020	Chrome Web Store will stop accepting new Chrome apps
June 2020	Chrome Apps on Windows, Mac, and Linux will no longer be supported. Customers who have Chrome Enterprise or Chrome Education Upgrade will have access to a policy to extend support through December 2020.
June 2021	NaCl, PNaCl, and PPAPI APIs will no longer be supported. Chrome Apps on Chrome OS will no longer be supported. Customers who have Chrome Enterprise or Chrome Education Upgrade will have access to a policy to extend support through June 2022.
June 2022	Chrome Apps will no longer be supported on Chrome OS for all customers.

What do I need to do?

• Assess your alternatives and plan to migrate off Chrome Apps to other solutions in the coming months, such as Progressive Web Apps (PWAs), Android apps (for Chrome OS), and/or Chrome Extensions.
• Migrate before June 2021, keeping your users in mind so that they have sufficient time to switch to your new product.

[Mike Frysinger]

tl;dr: rest assured that the ssh extension will keep working. if you don't care about the details, you can stop reading :). if there are any important updates or notifications, they will go out via the app & this mailing list.

I've been working on the wasm port and with other chromium devs for a few years now to minimize user disruptions. I have a pending CL to clarify & document all of this, but was waiting on feedback from product teams before landing. I didn't think this specific announcement was going to go out before I had a chance to land, but oh well.

when I get back from vacation later this month, I'll sync up with the teams again and settle some details. I'll need to refresh the CL anyways to include this new announcement.

fwiw, i already have poc WASM builds of OpenSSH in the tree. we're working on the JS parts now and will hopefully have those available for dogfood by end of June 2020.

if people are worried about non-CrOS, they can use the extension that I released a few years back. that will work on all platforms and is not affected by the chrome app specific deprecation.

-mike

[Christoffer Olofsson]

Oh, I wasn't able to find the extension yesterday. Thanks, found it now!

--
You received this message because you are subscribed to a topic in the Google Groups "chromium-hterm" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-hterm/5sIFWXh4MJw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScmJ06oKcm7EzqQ4vRCo40YA%3DTw9P%2BC1L5xswNEoD-TaUA%40mail.gmail.com.

[Robert Campbell]

Brave currently doesn't support NaCL, so does this mean that in the future with the WASM builds, that it should theoretically work on Brave? By "poc WASM builds of OpenSSH" mean that you have some builds that work strictly by WASM? Would those theoretically work on something like Brave? How might an early-adopter like myself test one of these?

[Mike Frysinger]

i suspect that, until the web platform adds the necessary socket functionality, Secure Shell will (mostly) remain Chrome-only.

i've pinged the people holding up my CL that covers this in the docs so hopefully will have more info later as to the new requirements.

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/4e305a85-189d-4cf6-a1cd-b42b8e668966%40chromium.org.

[Theodore Dubois]

How will the WASM version of the nassh extension access sockets? Correct me if I'm wrong, but my understanding is that the only direct socket APIs in Chrome are chrome.socket (only available in Chrome apps which are being deprecated) and NaCL (now being deprecated).

~Theodore

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScm4q8NC1gs_LhUTtjNzKRpBbHgBmQJyeOdOGut8ZNdvJg%40mail.gmail.com.

[Andrew Stone]

Socket access will be via whitelist, as indicated here: https://chromium-review.googlesource.com/c/chromium/src/+/1965969

-A

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/85288CC8-4146-4FE4-A0B3-75F3F8F1BD29%40icloud.com.

[Theodore Dubois]

Are there plans to open that API to extensions not written by Google?

~Theodore

[Theodore Dubois]

Found my answer at https://crbug.com/909927.

Thanks!
~Theodore

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/FDAA6D54-8FCE-4A04-8A61-B38047CE46DF%40icloud.com.

[sus...@gmail.com]

Please share the link! 

To unsubscribe from this group and all its topics, send an email to chromiu...@chromium.org.

[Mike Frysinger]

https://chrome.google.com/webstore/detail/iodihamcpbpeioajjeobimgagajmlibd

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/1ab1e79b-917a-4212-ab17-b63b039c3745%40chromium.org.

[Colm Buckley]

Experimentally switched to the extension from the app; I like the way you can quickly select a client from the dropdown menu, all the other functionality seems to be just fine.

One piece of muscle memory is tripping me up - ctrl-shift-N in the app brings up a new window at the connection dialog; in the extension it brings up a second connection to the current client. Is that an intentional change? I'm used to hitting ctrl-shift-N to bring up a new connection; but it's rarely to the same host.

Otherwise this was close to a no-op replacement.

Colm

To unsubscribe from this group and all its topics, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOSckR_8BUbo8bVONmYt07ObqmNVqtkrmEPTujjg8BobAwDQ%40mail.gmail.com.

--

Colm Buckley | Corp Eng Tech Lead | +353 87 2469146

[Mike Frysinger]

that behavior wasn't intentional.  i filed https://crbug.com/1045581 to track.

-mike