2 ms·
Neither am i! I had a look at the terms. I couldn’t see anything specifically outlawing this, So i put a little disclaimer and message at top of the action yaml
by keepamovin 3y ago
Neither am i! I had a look at the terms. I couldn’t see anything specifically outlawing this, So i put a little disclaimer and message at top of the action yaml addressing GitHub staff and requesting they inform me if they need it taken down! I’m happy to oblige of course.
I also added a little message at the top of the main project’s read me like remember you know you’re on GitHub infrastructure don’t abuse this. Thanks for repeating it in your comment. I appreciate that !
My feeling is that GitHub probably would’ve ironed out many categories of abuse that they want to prevent over the many years that actions have been live and I think it’s unlikely therefore to get abused by people but let’s see what happens. Hopefully it doesn’t.
But it’s fairly funny in a way because the same technology is what I use for CI to check the applications working—there’s actually a surprising amount that you can do with GitHub actions, and in this case I was able to kind of basically turn it into a virtual desktop by way of ngrok, we are able to interface with her and guide you through the set up using GitHub issue comments I just thought that was really nice and I wanted to share it.
You can also tunnel in BrowserBox over SSH but I didn’t bother looking into that because ngrok just seems like the simple solution.
Finally, it’s a bit of a stretch to call it a VPN and I’m throwing up with calling it a proxy next time I post this—because these words are something people are familiar with and it’s essentially that kind of thing, but I think there’s important differences. but what it actually is harder to communicate and harder for people to get their head around: it’s really a remote virtualized browser that you’re connecting to using Websockets and web RTC, over an encrypted connection.
BTW - did you give it a try? What did you think?