mjochim

Apart from the fact that FFT is way more complex than needed for a guitar tuner, I also believe it’s not even really possible to use a Fourier Transform for a useful guitar tuner. Because you won’t achieve good enough frequency resolution.

I would be interested if I am missing any possible tricks here. But the low E string on a guitar is about 82.4 Hz. For a useful basic tuner you would need a precision of maybe 5 cents (~ percent of a semitone), or roughly 0.25 Hz (roughly 1 Hz for the high E string). Frequency resolution with the FFT improves when you analyse a longer signal. For 0.25 Hz resolution, you need more than two seconds of audio. Two seconds where the pitch doesn’t change. I don’t think you’d get anywhere with such a design.

I’m not sure if this could be changed with a higher sample rate. With a higher sample rate, you have more samples per second to feed into the FFT, but also the upper boundary for frequency increases, so I believe frequency resolution just stays the same. I’d need to look up the formulas, though. Maybe with extreme zero padding? Or any other tricks?

It brings to our attention that there is a whole class of applications - "invite only" ones - where the main argument of the article does not apply. And therefore the conclusion ("The login user interface should distinguish bad user handle vs bad password") does not apply either. The article just mentions "99.9% of all websites" somewhere near the beginning, and that number may be way too high.

I would in fact be interested in an analysis of how many web sites do and don't follow recommendations like "do NOT distinguish bad user handle vs bad password", which are widely considered best practices. I wouldnt take a guess, could be anywhere between 10 and 90 percent.

> It could almost be useful.

I'm still pondering the “almost” ;-).

> It's a hash of everything that goes into a commit, including the commit message

... and, very notably, the hash of the parent commit. That is also part of the commit, which means that changing a parent commit would also imply changing the hashes of all later commits. This is sort of the whole point of git/version control.

> What's changed since then in terms of technology? Unless it's very significant, I suspect it will go the same way. Apart from an assistive technology viewpoint, my gut instinct is that it's not that satisfying or rewarding talking to a computer all day.

Training data is now abundant compared to twenty years ago, and so is computation power. That means training can be much more complex now.

The underlying technology is now typically neural networks (broadly speaking), whereas twenty years ago it might have been Hidden Markov Models.

Overall, recognition quality, even without speaker-specific training, is now on a very different level than back then. Whether it’s considered good is a matter of opinion. But it’s significantly better than twenty years ago.

Well Stack Overflow partly matches your description. I've never looked at self-hosted software that resemnles SO, but a quick search turns up this list:

https://meta.stackexchange.com/questions/2267/are-there-any-...

In German, we have almost the same expression, "ein Schuss vor den Bug." Literally, it translates to "a shot in front of the bow." I never thought about where it came from. Interesting to learn.

The expression has somehow always felt more like a frontal attack that stops right before actually hitting you. But my head may have conflated it with "jemandem etwas vor den Latz knallen," which translates to "slap something in front of somebody's bib."

Depends on whether you consider `git commit --allow-empty` a weird quirk ... I guess it would be reasonable to do so ;).

> Whenever you normally use some programs with other options than their defaults, it is simpler to define aliases for those programs.

I don't buy into this. These aliases tend to come at the cost, or at least the risk, that your workflow breaks when you are at another computer or working on a shell on some server that doesn't have this alias. That's why I like additional aliases, like l for ls, but with your favorite options. But I dislike aliases that change default behavior - and often in an intransparent way.

If the numbers 54 and 36 is correct, then one could be inclined to a simplified calculation and say that 1.5% of popular vote (54/36) equals 1.0% of seats. In that case, 75% of popular vote would equal 50% of seats. Or in other words: 3-1.

(and 50% of seats are not even a majority)

Another model would require 15% more to go from 36% to 51% of seats. In this case, 69% of popular vote (54+15) would be required for a majority of seats, or in other words: 2-1. Which effectively is just as egregious as 3-1.

Since I don't drink coffee, you are unlikely to ask me that question. But if you did, I might assume you are either joking or an idiot ;).

Clearly, it's a trick question (with unnecessary details to distract you from a possible solution) and the one asking probably thinks they are very clever. So now, whether you accept an equation or insist that it's impossible to solve when it's not really comes down to how you want to play that game.

I never knew! Thanks for sharing!

Let's neglect the horizontal distance the chair(s) travel at the bottom and at the top of the lift. Then the answer is "all of them," which holds true in your one-chair scenario.

The question reminds me of "how many groves are there on a vinyl record?"

If we are talking obligatory responses, don't forget this one: https://xkcd.com/221/

Since GP says it was a POP3 server, I suppose you would set up an email account in your client with its inbox server pointing to that POP3 server. When the client requests the content of the inbox, the server responds with a list of "emails" that are really just files with some email header slapped on; so your email client's inbox window essentially becomes a file browser.

> to rabbithole time away with fun

I absolutely love how you use rabbit hole as a verb here :D.

Because it's fun. For some, at least. One of several valid answers.

Except everything isn't more expensive. For example rent. Also, everyone can go see a doctor and pay nothing (not just the top quintile). All of this is if course simplified, but just to add another pair of cents.

I'd say most smartphones are powered on 24/7 during their regular phone lifetime. Not much would change by turning a phone into a 24/7 webcam, if viewed from that angle. Then again, CPU load would certainly be higher when used as a webcam.

It's called a strawman argument.

And I think you did not mean "win at life" in as broad a sense as the other person interpreted it. Either that or you two have very different ideas of what "winning at life" could mean.

sed --in-place has one file as both input and output. It's not really different from any pipe of commands where the input and output files are the same. But sed also makes a copy of the file before overwriting it - per default.

Huh? Btrfs is copy on write and it's definitely being used.

Have you thought about being a (local) politician? From a voter‘s perspective, this sounds like someone I would like to be my town’s mayor. You can grasp a large variety of things, you can meaningfully talk to experts in many fields and then bring their different ideas together in your policy.

Of course politics is a field with its own very special rules that may not have much to do with actual understanding of the subjects at hand. But I’m not talking POTUS or senator and maybe not even mayor. Even in smaller towns there are a couple of positions to fill. (I’m from Germany but this is true for many countries; maybe it’s true for yours. I’m presuming you’re from the US and I just noticed that I would rather not presume that, but I guess I do most of the time on HN.)

Don't know which providers you have considered, but one that many around me use is posteo.de. Or gandi.net (based in France).

Are you saying lesser known and less polished or lesser known and more polished?

GP was likely refering to extraordinary disks with more than 7200 rpm

Well thanks for this summary :-).

pgrep -f and pkill -f probably do the trick.

Good point. At the very least, it buys you time while attackers try to deobfuscate. How valuable that is is left for everyoneto judge; especially considering what a sibling says about locking yourself out - basically you and your team might also have to deobfuscate and thus lose time.

When the working copy of your git repo resides on a remote box R1 rather than your local machine. You want to ssh into the R1, edit files and commits there and then push from there to some other remote host R2. Meanwhile your private key for accessing R2 is on your local machine. R1 can only access your forwarded agent, but not your private key.

ProxyJump doesn't help you here because R1 does much more than just proxy your SSH connection.