../unsandboxed-extensions redirects

[yuri-kiss]

i had no idea where to put this due to there not being a discussions tab on the turbowarp.org page,
I was wondering why experiments.turbowarp.org/unsandboxed-extensions/ redirects to turbowarp.org

[GarboMuffin]

Because unsandboxed extensions are no longer an experiment. turbowarp.org fully supports unsandboxed extensions.

[yuri-kiss]

yeah but some extensions are unable to get into the gallery so thats what was used, if you can cant you add a url param or something to enable ALL extensions even ones not on the gallery to be ran unsandboxed?

…

________________________________ From: GarboMuffin ***@***.***> Sent: Wednesday, June 7, 2023 8:05 AM To: TurboWarp/.github ***@***.***> Cc: Surv ***@***.***>; Author ***@***.***> Subject: Re: [TurboWarp/.github] ../unsandboxed-extensions redirects (Discussion #2) Because unsandboxed extensions are no longer an experiment. turbowarp.org fully supports unsandboxed extensions. — Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAGGRICIJ7C4LPGDNH54AXDXKBVCBANCNFSM6AAAAAAY5YCOBI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GarboMuffin]

The unsandboxed extensions experiment had the exact same limitations.

[GarboMuffin]

There are inherent unfixable security risks in letting people run arbitrary untrusted JS. If someone's account gets phished through that, suddenly it becomes our fault.

[GarboMuffin]

We let you run unsandboxed extensions from local files now. That should be good enough for 90% of uses.

[yuri-kiss]

well that sucks, since you cant do that is there at least a way to fork turbowarp and disable the sandboxing for my own purposes?

[yuri-kiss]

as idk how to host a NodeJS site on github