Not sure if it helps much. It still looks like the same clickbaity garbage that's in my regular trending tab.

I think it's worse for me, based on the current set. The official trending page has a few videos that I'd like to watch, including two from my subscriptions. But the fairtrending page has nothing I am interested in.

Yes, here in my location too. Pretty much the same complete trash

Looks like AI recommendations did have a point all along lol

Though it seems to be a different list of clickbaity garbage from https://m.youtube.com/feed/trending which is sort of interesting.

I’m reasonably sure the YouTube one shows old stuff if it’s currently popular. Which I’d assume is what you’d want.

There’s nothing is even consider watching on the “Fair trending” one; I can see myself watching one or two things off the YouTube one if I was very bored.

I used the filter on the site and I watched a view of these videos https://www.fairtrending.com/?lang=en&fc=cat&cat=28&tag=&msc...

Honestly I'd much rather have some configurable yaml than some obscure app in the middle of your cluster that reads CRDs when what you're doing is just adding a side car.

At least this way you can tell if your local yaml is applied or not without a complicated diffing algorithm that compensates for an in-cluster modifier.

I would too, except, have you seen what your YAML looks like after all the Linkerd additions? There's a reason they don't even mention in the docs exactly what it changes.

Crypto still just means hidden or secret though. Both sides here probably ought to increase their specificity by one level.

Interestingly, r/crypto is the cryptography subreddit and has https://www.reddit.com/r/crypto/comments/7jrba2/crypto_is_no... stickied.

You can get it much of the way there by tweaking `~/.inputrc`

"\e[A": history-search-backward # Up key

"\e[B": history-search-forward # Down key.

Allows you to get press up while you have `ssh 10.2` in the terminal to cycle through ips matching, etc. It won't display like in fish before pressing it, but I find that's a reasonable tradeoff.

Managing node with package managers feels like a a bit of a fools errand at the moment. They are going to be wrapping npm somehow, but when npm can't even do things right..

To be fair, that aptly describe being a package maintainer in general -- you spend all day adding workaround patches so build systems stop doing things the "wrong way".

edit: Where "wrong way" is defined as "differently from the target distro's best practices"

They absolutely should not be wrapping npm. npm is attempting to do a job that package managers should be doing to begin with

The problem is that there is no single package manager that covers every platform. If you are writing an inherently portable library in node.js, as an author, are you supposed to also provide packages for RPM, dpkg, pacman, brew etc? Or do you expect distros to package every tiny thing?

So in practice there is a niche that npm covers, that wouldn't be filled if we removed it.

On the question of whether the system package manager should wrap npm - the reason why you want to do so is because it lets npm dependency resolution work regardless of how packages are installed. If the system package manager just does its own thing, then next time you do need to npm install a package (because it's a relatively obscure package that's not in your distro), you don't want it to install copies (or worse, yet overwrite) all the dependencies that you've already installed by other means.

The usual way package managers do this is, at packaging time, to use the native build tool to install the software rooted in a temporary directory, then fix up those files as needed (including fixing permissions and ownership) and copy them into a tarball. Does pacman not do that?

It does [1]:

  package() {

    npm install -g --user root --prefix "$pkgdir"/usr "$srcdir"/$pkgname-$pkgver.tgz

    rm -r "$pkgdir"/usr/etc

    mkdir -p "$pkgdir/usr/share/licenses/$pkgname"

    ln -s "../../../lib/node_modules/$pkgname/LICENSE-MIT" "$pkgdir/usr/share/licenses/$pkgname/"

  }

[1] https://git.archlinux.org/svntogit/community.git/tree/trunk/...

This is cool. A few funny ones I found:

ExampleTester

Commanater

java-cruft

Generatter

the-git

Damn that Fermat margin.

Is there really any benefit to this over explicit child process calls? I realize the syntax is shorter, but now you're hiding the fact that you are shelling out.

Overloading require for this purpose is a guaranteed way to break static analysers and module bundlers.

If I understand you right, child process is made by utility that check your local version and laters to notify your for updates. It should only be called once an hour

There are also 3 gotos in that function.

Goto should be used in the (admittedly rare) cases where it makes program flow cleaner. The original complaint was that people weren't moving to structured programming constructs as they became available. That really isn't a problem any more.

I would totally install a sublime plugin or something like that for this.