• 2 Posts
Joined 2Y ago
Cake day: Nov 30, 2020


If you’re on Linux, here’s my notflix script to torrent and watch instantly.

Just do:

./notflix.sh solaricks

Wait 2 minutes, and it’ll play.

Time to root and flash, though I really wish that was an easier process. It’s a different process and set of downloads for each phone.

I tend to search for strings, like ‘CC-BY-SA’, because you’ll get things like Deviant Art images which are CC, even if the site isn’t.

Nice blog post, and always nice to see RSS feeds.

I’ve never had practical trouble downloading scripts and identifying the creators, because I use package managers. I think the best general solution for normal end-users getting packages they can trust is always a well-audited package manager.

And of course, the GPG key solution seems to work well enough for coders.

I can’t imagine a general solution to Github workflows. I use Gitlab’s CI for LaTeX documents, but terraform code would obviously be better for other projects. I sounds like disparate solutions is a good idea.

I’m not sure MS will have much luck using EEE on GPL projects.

When .doc format was extended, they then ‘extended’ it with proprietary features, then extinguished competition by locking them out of those additional features.

You can download all Github projects, and wikis, because they’re all based on Git, and the only ‘extensions’ particular to Github are CLI specs, and issues, which can also be ported easily.

I’d find this a niussance. I use automatic git merges and pushes through ssh keys.

Perhaps the article is trying to talk about removing ‘password-only’ authentication, but what it says is that it requires ‘one or more forms of two-factor authentication’, which suggests a second or third form of authentication, so ssh-keys-only seems like it’s out.

Streaming anything with 4 lines of bash
I'm running a similar script, and it's great. Takes a minute to find less popular films, but broadly works fine.

I turned my notes into an online cheat sheet
I take lots of notes, so I've made them into a cheat sheet, and stuck them on my website. ## Why not use existing documentation? I want a more chronological order. If you `curl cht.sh/git`, you find `stash` is covered before committing, and there is no init or clone, so at that point you don't actually have a git to work with. I'm also not a fan of documentation explaining what something does. This is meant to be for people who already know what something does (why else would you be looking for docs on it?), and just want to know the basic commands to set up and start. I want docs that give you the bare bones in ~5 minutes, with the assumption that man pages and Stack Exchange will take care of advanced usage. I've worked on making it more accessible, but it's still a work in progress. If you'd like to make a correction, or add a program, the whole thing is on a git, [here](https://gitlab.com/andonome/lk). PRs are welcome.