{"action":"created","issue":{"url":"https://api.github.com/repos/beakerbrowser/beaker/issues/230","repository_url":"https://api.github.com/repos/beakerbrowser/beaker","labels_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/230/labels{/name}","comments_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/230/comments","events_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/230/events","html_url":"https://github.com/beakerbrowser/beaker/issues/230","id":197946983,"node_id":"MDU6SXNzdWUxOTc5NDY5ODM=","number":230,"title":"Extensions?","user":{"login":"zeke","id":2289,"node_id":"MDQ6VXNlcjIyODk=","avatar_url":"https://avatars1.githubusercontent.com/u/2289?v=4","gravatar_id":"","url":"https://api.github.com/users/zeke","html_url":"https://github.com/zeke","followers_url":"https://api.github.com/users/zeke/followers","following_url":"https://api.github.com/users/zeke/following{/other_user}","gists_url":"https://api.github.com/users/zeke/gists{/gist_id}","starred_url":"https://api.github.com/users/zeke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zeke/subscriptions","organizations_url":"https://api.github.com/users/zeke/orgs","repos_url":"https://api.github.com/users/zeke/repos","events_url":"https://api.github.com/users/zeke/events{/privacy}","received_events_url":"https://api.github.com/users/zeke/received_events","type":"User","site_admin":true},"labels":[{"id":398801843,"node_id":"MDU6TGFiZWwzOTg4MDE4NDM=","url":"https://api.github.com/repos/beakerbrowser/beaker/labels/discussion","name":"discussion","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-12-29T03:10:48Z","updated_at":"2018-09-24T16:54:03Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"@pfrazee is it possible/easy to install Chrome extensions in Beaker?"},"comment":{"url":"https://api.github.com/repos/beakerbrowser/beaker/issues/comments/424046681","html_url":"https://github.com/beakerbrowser/beaker/issues/230#issuecomment-424046681","issue_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/230","id":424046681,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNDA0NjY4MQ==","user":{"login":"pfrazee","id":1270099,"node_id":"MDQ6VXNlcjEyNzAwOTk=","avatar_url":"https://avatars2.githubusercontent.com/u/1270099?v=4","gravatar_id":"","url":"https://api.github.com/users/pfrazee","html_url":"https://github.com/pfrazee","followers_url":"https://api.github.com/users/pfrazee/followers","following_url":"https://api.github.com/users/pfrazee/following{/other_user}","gists_url":"https://api.github.com/users/pfrazee/gists{/gist_id}","starred_url":"https://api.github.com/users/pfrazee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pfrazee/subscriptions","organizations_url":"https://api.github.com/users/pfrazee/orgs","repos_url":"https://api.github.com/users/pfrazee/repos","events_url":"https://api.github.com/users/pfrazee/events{/privacy}","received_events_url":"https://api.github.com/users/pfrazee/received_events","type":"User","site_admin":false},"created_at":"2018-09-24T16:54:03Z","updated_at":"2018-09-24T16:54:03Z","author_association":"MEMBER","body":"A lot of our ideas for Beaker have evolved since this thread started, while some have not. Let me give my current thinking.\r\n\r\nI'm not 100% sure about how we'll approach extensions, or which APIs we'll eventually include, or if we'll end up including page injection APIs. Maybe we will include them; maybe we'll implement the ful Web Extensions API. Sometimes it's better to just start with the simple old solutions and build from there.\r\n\r\nWhat I *do* know is that we want a Web applications model which is safer and more powerful. To some degree, I think that means merging the extensions world and the website world so that you can \"Install\" an app and give it a lot of power: things like registering for intents, adding buttons to the navbar, and running persistent background processes. (The [library API](https://beakerbrowser.com/docs/apis/experimental-library) is the beginning of a step to that kind of power, but I am not satisfied by it in the least.)\r\n\r\nI also know that we can make a more powerful plugin system by getting apps involved in their own extension. If we create APIs for apps to load and run HTML/CSS/JS plugins, then we give apps the opportunity to structure the exchange between themselves and their downstream. The app can say, \"I display comments and I have a toolbar for inserting markup: does the user have any plugins for adding actions to the toolbar?\" That creates potential for a much more powerful plugins ecosystem.\r\n\r\nMaybe we need APIs to modify core behaviors like monitoring & modifying all traffic, or injecting JS into every page you visit. My hope is that we could improve the core behaviors so that userland hooks don't need to adopt that kind of risk, but I recognize that's an ambitious goal, and it comes with downsides.\r\n\r\nI'm trying not to dismiss your requests. I'm just trying to find a new approach that fixes some of the old."}}
{"actor":{"display_login":"pfrazee"}}