4oo4

Joined 11 years ago

Karma

569

Submissions

278

Member since

Jun 15

[ my public key: https://keybase.io/4oo4; my proof: https://keybase.io/4oo4/sigs/nPir1PHzdPsISlzduR9kfI3BIB8i0ZIEL5keD5nLcfk ]

View on Hacker News

Recent submissions

Comment · 5 months ago

JSshelter looks cool, I'm not familiar but this makes it seem like it operates more like resistfingerprinting by blocking outright instead of noise injection, at the expense of more broken sites?

https://jshelter.org/fpd/

What all security extensions do you run? After running into issues over the years, with extensions doing multiple things that fight each other, I switched to trying to block via ublock origin as much as possible, then prefer other extensions to just do one thing to extend coverage, like this one. Makes it much easier to troubleshoot/exclude/disable when it breaks something vs. fiddling in settings.

Comment · 5 months ago

I tested this extension that I've been using for a long time on the turnstile page and it got through, fwiw. I think it's a bit more subtle than how resistfingerprinting works but not sure what the privacy tradeoff is.

https://github.com/kkapsner/CanvasBlocker

Comment · 6 months ago

From personal experience:

- Don't tense up and play the most relaxed you possibly can. it's very hard to unlearn if you start off that way like I did

- Be kind to yourself since playing guitar is an unnatural thing to do (wrist position, hand strength required, calluses, etc.), so it takes time.

- Play along with songs as much as possible. Slow it down if you need to or just do a simplified version at first, and just focus on improving/learning one thing each time you play. This is also a great way to get comfortable with improv.

- If you're struggling with something, break things down to the smallest possible parts you can, play it really slow and repeat, until your muscle memory takes over, then slowly speed it up and put it back in context.

- If you're playing an electric, turn the volume up enough and let that do the work instead of your picking

- If you catch yourself noodling instead of playing consciously, stop playing. It's OK to noodle sometimes but if you do it a lot you'll get used to going on autopilot and your skills can plateau

- Don't be afraid of the upper fretboard. You can play super slowly up here and as long as you can at least fake being confident/intentional it'll sound nice. If you have smaller hands and have trouble with stretching your hands on lower frets, this can work to your advantage.

- You can get a solid guitar for $400-500. Spending more money up to about $2-3k will get you a nicer guitar, chasing that extra 1% of tone and have a nicer feel in your hands, but it's diminishing returns the more you spend.

- Same with pedals. Yes you can spend lots of money on fancy/unique pedals, but there's nothing wrong with sticking to cheap ones, especially Boss. A lot of great 80s/90s music was recorded with them, and bands frequently use the cheaper/commodity ones while touring instead of fancy boutique ones.

- Per Nile Rogers: "It's not about the shit you play, it's about the shit you don't play" (especially for funk stuff)

- Also for funk (and post-punk and experimental) stuff, a guitar is also a percussion instrument if you want it to be.

- Once guitar playing gets to a certain level of virtuosity (Steve Vai, IMO), it paradoxically can become extremely boring. Playing simply but with the right emotion channeled into your picking hand is much more interesting than super technical stuff.

- Related, remember that Bill Withers was in his 30s when he started making music and chose a very simple way of composing things, but was still able to do amazing things

Comment · 7 months ago

Someone already found this years ago:

https://www.youtube.com/watch?v=XfcvX0P1b5g

I haven't read the full article yet but I'm guessing they didn't give credit, as the New York Times tends to do. Not definitive but it's a very convincing case.

Comment · 7 months ago

Yes and no, in this case you don't need a local vscode instance to connect to your vscode container, just a browser. It's more similar to self-hosted Github Codespaces, and but I believe code-server was actually released first.

Personally I've fiddled enough with podman that that part of it doesn't bother me, and I don't like Docker/Podman desktop (which I think is what devcontainers assume the setup is) and just want to use the docker/podman daemon/cli, so that's something I also don't want to have to mess with. I know you can also point devcontainers at a remote or local docker daemon, but that means giving it full control of the daemon, which is a nonstarter and too risky for me from a security standpoint. I really like to have my podman containers really locked down in terms of capabilities, userns, gvisor, etc. and given that it just wants full control of docker I'm guessing it takes none of that into consideration (or, painful to try and graft on).

I also really don't trust VSCode's remoting protocols (especially remote tunnels, which is basically just a reverse shell). So for me it's a matter of having more control over container runtime security (the docker/podman ecosystem usually treats it as an afterthought in favor of convenience, and devcontainers appears to be no different), and it doesn't depend on anything on my machine I'm accessing it from. Since VSCode just a becomes another self-hosted web app this way, it's pretty much the exact same experience no matter where I'm connecting from.

Comment · 7 months ago