flackr
Future of this project
Now that Chrome App will be gone in June 2021 even for Chrome OS (for individual users), is there any plan to move forward? (Or is it even possible to do so?)
Maybe make the extension client-agnostic so other Web apps that need IRC access can use it.
I don't believe there is a chrome extension API for making the raw TCP connections necessary for connecting to an IRC server, but please correct me if I am mistaken.
There is a sample PWA that I've started on the server branch but it will require running a server (currently NodeJS) on some computer to make the real IRC connections.
Can't extensions use all the APIs apps can?
On Tue, Apr 14, 2020 at 7:46 AM Robert Flack [email protected] wrote:
I don't believe there is a chrome extension API https://developer.chrome.com/extensions/api_index for making the raw TCP connections https://developer.chrome.com/apps/sockets_tcp necessary for connecting to an IRC server, but please correct me if I am mistaken.
There is a sample PWA that I've started on the server branch but it will require running a server (currently NodeJS) on some computer to make the real IRC connections.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-613486254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XPZ6NZNNFF5CCH32MCDRMRZNBANCNFSM4MCNPORQ .
I was even thinking of a general extension to work for any web app that wants a socket connection.
On Sat, Apr 18, 2020 at 1:42 PM Samuel Sloniker [email protected] wrote:
Can't extensions use all the APIs apps can?
On Tue, Apr 14, 2020 at 7:46 AM Robert Flack [email protected] wrote:
I don't believe there is a chrome extension API https://developer.chrome.com/extensions/api_index for making the raw TCP connections https://developer.chrome.com/apps/sockets_tcp necessary for connecting to an IRC server, but please correct me if I am mistaken.
There is a sample PWA that I've started on the server branch but it will require running a server (currently NodeJS) on some computer to make the real IRC connections.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-613486254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XPZ6NZNNFF5CCH32MCDRMRZNBANCNFSM4MCNPORQ .
Can't extensions use all the APIs apps can?
No, extensions have a much more restricted API. Socket API is only one of them.
Weird. How do the SSH extensions work? (There are non-app ones.)
On Sun, Apr 19, 2020, 20:49 Franklin Yu [email protected] wrote:
Can't extensions use all the APIs apps can?
No, extensions have a much more restricted API. Socket API is only one of them.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-616292836, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XP6DYRRI2TSKKROSKFTRNPA27ANCNFSM4MCNPORQ .
https://chrome.google.com/webstore/detail/secure-shell/iodihamcpbpeioajjeobimgagajmlibd
On Sun, Apr 19, 2020, 20:52 Franklin Yu [email protected] wrote:
Any example?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-616293401, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XP6ONL6IQW7UPRYIBJLRNPBGZANCNFSM4MCNPORQ .
That’s the only whitelisted one. I mean, since it’s made by the Chrome team, it’s very easy for them to whitelist their own extension, essentially making the API a private one. CIRC in contrast doesn’t get the bless from them, so it’s more difficult to rely on their private API (technically possible by looking at their code but that’s reverse-engineering because the API would be undocumented).
Maybe we should wait a while? Maybe Google will startallowing sockets for extensions.
On Mon, Apr 20, 2020, 17:20 Franklin Yu [email protected] wrote:
That’s the only whitelisted one.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-616877579, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XP35AJ4KYV233FLCEEDRNTRGFANCNFSM4MCNPORQ .
Maybe Google will start allowing sockets for extensions.
Yes, that would possibly be the best scenario.
I doubt they would permanently block the entire platform from something as important as sockets.
On Mon, Apr 20, 2020, 17:34 Franklin Yu [email protected] wrote:
Maybe Google will start allowing sockets for extensions.
Yes, that would possibly be the best scenario.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flackr/circ/issues/438#issuecomment-616880984, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54XP76K37OVD55UQOV74DRNTS2ZANCNFSM4MCNPORQ .
I think I missed part of the announcement. Chrome App on Chrome OS will be until the middle of next year, but users with Chrome Enterprise or Chrome Education (covering a large part of Chrome OS users) will have one more year. At least this buys more time for students getting Chromebook from schools/universities, and we have adequate time to consider the way out.
I’m editing the issue description for that.
The raw socket proposal is under early discussion. If this proposal is approved, then it becomes possible to host a static page (for example, on GitHub Pages) as an IRC client.