If so how would that work on non Apple devices? Also how much will that sandbox protect you?
A native graphical shell for SSH
41–50 of 239 posts
Re: A native graphical shell for SSH
#42Re: A native graphical shell for SSH
#43i'm trying to understand how outer shell works here. on the website you give the following as your motivation: > Apps like Jupyter and Tensorboard are not typically visible to standard web browsers if they’re running on remote servers, because it would be terribly unsafe to let the whole internet touch this app. Instead, they run on a local port on the server, which your computer can’t access directly. > Classically,…
I'm closer to the cluster that uses them for deep learning experiments, GPU kernel optimization, robot development (a robot is just a server that moves!)... use cases where you are explicitly using a remote computer.
For this cluster of people, I think this tool feels more intuitive than the flow you suggest. But maybe I'm projecting!
And, to me, this just feels like one of the fundamental things that could exist; it's like a graphical operating system, but remote-first.
Re: A native graphical shell for SSH
#44I don't really know what outerframe frame is. I tried to understand from the video and the blog but I'm still not sure what it is. Is it like a web browser but instead of DOM, HTML and JS you have Swift and SwiftUI running in a sandbox? If so how would that work on non Apple devices? Also how much will that sandbox protect you?
https://outerframe.org/ and https://outerloop.sh/native-apps/
Re: A native graphical shell for SSH
#45It does need an agent that starts with every X or Wayland session and waits for requests from remote SSH sessions to start an app.
Re: A native graphical shell for SSH
#46Earlier quoted context omitted.
You have a very loose definition of a shell that conflicts with about 40 years of history.
Not really no. I’ve been using shells and authoring new ones for around 40 years across a variety of platforms. The term has always been pretty loosely defined because as technology evolved the term “shell” was borrowed. So like I said, a shell can refer to a graphical core just as much as a text-based one. You can get web shells too. The original intent was that a shell is a thin wrapper on top of the OS to expose t…
Re: A native graphical shell for SSH
#47I don't really know what outerframe frame is. I tried to understand from the video and the blog but I'm still not sure what it is. Is it like a web browser but instead of DOM, HTML and JS you have Swift and SwiftUI running in a sandbox? If so how would that work on non Apple devices? Also how much will that sandbox protect you?
It's purportedly cross-platform. The documentation leaves a lot to be desired, but it is described more here: https://outerframe.org/ and https://outerloop.sh/native-apps/
It's a fun heretical idea, moving away from a "cross-platform" web to a "multi-platform" web. It's a cross-platform protocol that hands off to platform-specific frontend code. I think it's a natural direction for the web, in a world where LLMs can translate to other platforms.
Re: A native graphical shell for SSH
#48Earlier quoted context omitted.
Ever since I started using Caddy, doing that has been soooo easy. Download the binary, make a Caddyfile myservice.example.com { basic_auth { admin some_password_hash_here } reverse_proxy :3000 } And then just "./caddy start"
does this work with multiple caddy servers? ie can you bind multiple caddy servers to port 80/443?
Re: A native graphical shell for SSH
#49Earlier quoted context omitted.
Ever since I started using Caddy, doing that has been soooo easy. Download the binary, make a Caddyfile myservice.example.com { basic_auth { admin some_password_hash_here } reverse_proxy :3000 } And then just "./caddy start"
does this work with multiple caddy servers? ie can you bind multiple caddy servers to port 80/443?
domain1.com -> service on port 1234
domain2.com -> service on port 5678
domain3.com -> serving a file directory.
And then you still access domain1.com, domain2.com, domain3.com on port 80/443
Re: A native graphical shell for SSH
#50Earlier quoted context omitted.
Not really no. I’ve been using shells and authoring new ones for around 40 years across a variety of platforms. The term has always been pretty loosely defined because as technology evolved the term “shell” was borrowed. So like I said, a shell can refer to a graphical core just as much as a text-based one. You can get web shells too. The original intent was that a shell is a thin wrapper on top of the OS to expose t…
Appeal to authority.