algo VS Atom

Check out the command line args for Auto1111, it talks about a gradio setup that can be accessed remotely. There's a time limit on gradio links though, I think. You could also set up a vpn that will allow you to access your PC remotely, then run A1111 with the --listen command and access it that way. I've done this with an Algo VPN on Azure and a Wireguard client for Windows for Android, but any VPN that lets you access your PC remotely would work.

One way you could try to get around is building your own VPN service, like this: https://github.com/trailofbits/algo/blob/master/README.md

If you want a quick way to setup wiregaurd on your cloud provider of choice there's this easy tool by the security company trailofbits https://github.com/trailofbits/algo

they specifically try to remove extraneous features and make it easy to use, I'm surprised more people don't use it

Isn't the problem that the exit IPs will be flagged / blocked, meaning at best you'll get a ton of captchas etc.? I have set up personal Wireguard VPNs with Algo[1] before on DO, and while they work fine, they cause a lot of friction for that reason.

1: https://github.com/trailofbits/algo

To make matters slightly more complicated, I am using algo which is a DIY wireguard VPN for all my devices (including my validator machine). So all traffic likely needs to get routed to/from the VPN machine running in the cloud (though I might be wrong about this).

Algo project still works well. Very quickly launch a WireGuard VPN to several popular cloud providers, or any Linux instance you already have access to, including your rPi.

https://github.com/trailofbits/algo

I'm surprised that nobody here mentioned Atom [1]. IIUC, Atom was designed to be hackable like Emacs.

A successor to Atom is Pulsar [2].

[1] https://github.com/atom/atom

[2] https://pulsar-edit.dev/

atom (RIP buddy! Free) Atom is a hackable text editor for the 21st century, built on Electron, and based on everything we love about our favourite editors. We designed it to be deeply customizable, but still approachable using the default configuration

These versions of Atom will stop working on February 2 [2023]. To keep using Atom, users will need to download a previous Atom version.

For Mac users - mv ~/.atom ~/atom_bak rm -fr /Applications/Atom.app download https://github.com/atom/atom/releases/tag/v1.60.0 Drag download to Applications folder - to install

Which version did you roll back to, and where obtained? I noticed the packages on GitHub only go to 1.60.0, and the issue affects 1.63. Did copying packages from the .atom directory work without any other changes?

And it doesn't match because https://github.com/atom/atom/releases/download/v1.63.1/atom-amd64.deb returns a 404 not found error, so of course it doesn't match.

# Maintainer: Moses Narrow pkgname=atom-bin _pkgname=${pkgname/-bin/} pkgver=1.63.1 pkgrel=1 pkgdesc='A hackable text editor for the 21st Century. Repackaged .deb / binary release.' arch=('x86_64') url="https://github.com/atom/atom" license=('MIT') depends=('apm' 'electron11-bin' 'libxkbfile' 'ripgrep') optdepends=('ctags: symbol indexing support' 'git: Git and GitHub integration' 'hunspell: spell check integration') provides=('atom') conflicts=('atom') options=(!emptydirs) _archive="$_pkgname-amd64" #https://github.com/atom/atom/releases/download/v1.63.1/atom-amd64.deb source=("$url/releases/download/v$pkgver/$_archive.deb") sha256sums=('5c7c0259062b9d4911d2537bfceaff5316f9de111698840a90d7cd497df891a6') package() { cd $pkgdir tar -xpf ${srcdir}/data.tar.xz rm $pkgdir/usr/bin/apm }

I read the article and I would like to inform you that atom will no longer be officially supported as you can see in official repo (https://github.com/atom/atom )