HNHacker News
TopNewBestAskShowJobs

BlackFingolfin

624 karma · joined February 21, 2014

submissionscomments
BlackFingolfin··on AirPods Max
With "media server" I generally meant: "device hooked up to the speaker and AV receiver for video playback, couch surfing, perhaps the occasional game (mostly via emulators).

Yeah, adding the microphone and camera is going beyond that, but it's convenient to use the computer already hooked to the TV instead of, you know, hooking up yet another one. Also, how does Airplay give me access to the camera mounted on top of the TV (an old phone, BTW)? Also, how is that relevant for my comment at all? :-)

BlackFingolfin··on AirPods Max
I've recently given Linux another try, for use on a machine meant as a media server, and also to drive my family "video call station" (i.e., combine big TV, webcam and a bluetooth audio widget with mic and speakers so that the kids can talk to their grandparents in COVID times). Went with the most main stream distro, Ubuntu 20.04.

Result: couldn't get the Bluetooth conference widget working. Googled around for hours and tried all kinds of things, including compiling and installing kernel modules and replacing the bluetooth stack. Nothing worked. No, this is not an exotic non-standard protocol, it's a standard one (I think aptX or so? sorry, forgot the details again already; but I googled around and found lots of people with similar issues, and then many "solutions", none of which worked; see above)

Anyway, I am back to plugging in my MacBook each time we want to video conference, and will soon install Windows on the media server (no matter how much I hate the thought).

I really want to use Linux for this kind of stuff, but it's 2020 and I can't get a Bluetooth widget working that works flawlessly on various Macs, Windows machines, iPhone, iPad and an Android phone.

So while things may be better, they are still far from where they could be, I am afraid.

BlackFingolfin··on South Africa's lottery probed as 5, 6, 7, 8, 9 and 10 drawn
According to a comment elsewhere in this HN discussion, it seems there are rather something like <200 draws a week. That gets us to just a 3% chance of this happening in a given year. That's still quite a bit more than one might intuit, but not quite as drastic.

Of course, as others here already pointed out that there are far more "suspicious" patterns (e.g. other arithmetic progressions like 5-10-15-20-25-30, primes, ...). And of course they often play by different rules, etc.

BlackFingolfin··on South Africa's lottery probed as 5, 6, 7, 8, 9 and 10 drawn
At least those I know in Europe and US are weekly...
BlackFingolfin··on macOS 11 Big Sur compatibility on Apple Silicon
Actually, Homebrew developers have been working on this for months (in their spare time, too, given that they are all volunteers); but the reality is that this is a gargantuan task, 6 months simply wasn't enough.

So no, I don't think "you can have day-one support, if you want it" is accurate at all.

BlackFingolfin··on Why is Apple's M1 chip so fast?
Thanks for the link! Yeah, that's basically the numbers I also found -- although the number of instructions decoded per clock cycle is a different metric from the number of µop that can be issued, so that feels a bit like moving the goal post.

But, fair enough, for practical applications the latter may matter more. For an apple-to-apple comparison (pun not intended) it'd be interesting to know what the corresponding number for the M1 is; while it is ARM and thus RISC, one might still expect that there can be more than one µop per instructions, at least in some cases?

Of course then we might also want to talk about how certain complex instructions on x86 can actually require more than one cycle to decode (at least that was the case for Zen 1) ;-). But I think those are not that common.

Ah well, this is just intellectual curiosity, at the end of the day most of us don't really care, we just want our computers to be as fast as possible ;-).

BlackFingolfin··on Why is Apple's M1 chip so fast?
OK, I could see how one could implement a variable width instruction decoder (e.g. "if there are 8 one-byte instructions in a row, handle them, otherwise fallback to 4-way decoding" -- of course much more sophisticated approach could be made).

But is this actually done? I honestly would be interested in a source for that; I just searched again and could find no source supporting this (but of course I may have simply not used the right search, I would not be surprised by that in the least). E.g. https://www.agner.org/optimize/microarchitecture.pdf#page216 makes no mention of this and calls AMD Zen (version 1; it doesn't saying anything on Zen 2/3).

I did find various sources which talk about how many instructions / µops can be scheduled at a time, and there it may be 8-way, but that's a completely different metric, isn't it?

BlackFingolfin··on Why is Apple's M1 chip so fast?
What do you mean with "8-wide instructions", and what does that have to do with multiple decoders?
BlackFingolfin··on Why is Apple's M1 chip so fast?
Could you explain what you mean with "8-wide decode in many places" ? How is that possible, isn't instruction coding kinda always the same? I.e. always 4-wide or always 8-wide, but not sometimes this and sometimes that.

All sources I could find say it is 4-wide, so I'd also be interested if you could perhaps give a link to a source?

BlackFingolfin··on How to get root on Ubuntu 20.04 by pretending nobody’s /home
/me raises hand

Yes, they do. And then they complain to you that this broke something: they split our package, from the main package A they split off parts into separate packages B, C, ... that depend on A. And then complained to us that B and C had a circular dependency and that this means we had to fix something. The audacity.

Our users still sometimes report issues where I immediately ask "are you using Debian or Ubuntu?" and the answer is usually yes: because guess what, they only install A (which matches our software's name) and then they miss the functionality which Debian moved into B, C, ... We actually print a warning about this when starting the software (along the lines of "Warning, B is missing, some things may not work as expected"), which then Debian patched out, calling it "misleading".

I've never had similar issues with any other downstream Linux distro.

So, no, I really can't agree with GP's statement.

BlackFingolfin··on How to get root on Ubuntu 20.04 by pretending nobody’s /home
> It's not fine, but when the upstream authors do not regard or consider requirements of downstream projects, what can you do?

Well, as one of those upstream authors whose code was patched: I was never contacted about it, so I never knew there was a requirement to be met, and so they carried around a bad patch for years, about which I knew nothing. Once a user pointed this out to me, the next release fixed the underlying issue in a better way. After years in which the Debian folks didn't file an issue or report the problem in any way that I could tell.

Mind you, Debian is not alone in this, it happens with other distros, too.

And to be fair, I think this rather depends a lot on the downstream package maintainer; I've witnessed this with other projects where they were quite good in interacting with upstream to get something sorted out. I am not really sure if any policy Debian/Fedora/... could enact would really help with it; people can (accidentally or intentionally) ignore them.

BlackFingolfin··on Pijul: Towards 1.0
Thrussh is not a "remake" of a ssh, it is simply yet another implementation, and I don't find that particularly unusual or problematic; if one is working on a Rust based project, IMO it makes a lot of sense to work on a Rust based SSH implementation, too (for all kinds of reasons, ease of use and portability being one).

As a matter of fact there are dozens if not hundreds of them out there. For a time, I was tracking some of them to figure out which ones support which particular protocol extension; the result is https://ssh-comparison.quendi.de and the list there is really incomplete (and sadly also outdated -- PRs welcome ;-)), I think I could easily double the number of entries there if I resumed work on it.

The one concern I'd have for a custom implementation is when they roll their own crypto... On a quick glance, that seems (?) to be the case here, see <https://docs.rs/crate/thrussh/0.28.0/source/src/cipher/chach...>, albeit only for chacha20poly1305 which is relatively easy to implement "right" and "securely", but one can still mess that up...

BlackFingolfin··on Pijul: Towards 1.0
Thank you for clarifying this, I think it's much better if this paragraph doesn't distract people from the great work you are doing on Pijul. And being plagiarized totally sucks, as someone who has found his own GPL'ed code in non-open commercial products, I think I can relate, even though this is of course not quite the same. I hope you can find other ways to deal with that, though.
BlackFingolfin··on Pijul: Towards 1.0
Hm, right at the start in the "Warning about licenses" they seem to try to make the GPL apply to a concept, an abstract algorithm -- kinda like a patent? But I don't think that's how licenses like the GPL work? And hence that this is not legally binding in any way? At the very least, it reads rather strangely to me. Perhaps someone who knows more about licensing that me can elaborate?

To clarify: they claim that after reading the article, any independent implementation of the algorithm (even if it didn't involve looking at their code) must be licensed under the GPL. But that seems to go against everything I thought I knew about "clean room reverse engineering"?

BlackFingolfin··on Good Quality DOSBox Video Capture
Relevant blog post: https://pineapplemonacle.blogspot.com/2014/10/dig-dug-vs-mr-...
BlackFingolfin··on Computation of a 30750-Bit Binary Field Discrete Logarithm
Why? Is there a reduction from EC DLP to FF DLP?
BlackFingolfin··on Computation of a 30750-Bit Binary Field Discrete Logarithm
The article is about discrete logarithms in binary finite fields, though, not in elliptic curves; so are the references you give (other than Wikipedia). Perhaps elaborate how you draw conclusions about ECC from this? (I am not saying I disagree, but I feel your comment is oddly disconnected from TFA)
BlackFingolfin··on PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7
I doubt that Julia 1.6.0 will be released next week. There were no rc (release candidates) not even an alpha or beta release.
BlackFingolfin··on Wirecard’s Boon is shutting down
Boon was/is part of Wirecard, which blew up last month as major fraud came to light; see e.g. https://www.washingtonpost.com/business/how-german-fintech-d... or just google for "Wirecard"
BlackFingolfin··on The Polymath Playbook
Actually I don't think you can paint that on a sphere without overlap... you'll need to paint it on a torus ;-)
BlackFingolfin··on How Did Vim Become So Popular?
AFAIK it still tries to stay mostly compatible with regards to how it is controlled, doesn't it? So while the internals are perhaps new, the frontend is not.

But I think Kakoune https://kakoune.org would fit the bill

BlackFingolfin··on Arithmetic Shifting Considered Harmful (1976) [pdf]
There is no standard that says quo/rem or div/mod should mean one or the other. And in fact there are more than just two choices for how to implement these. See e.g. https://en.wikipedia.org/wiki/Modulo_operation
BlackFingolfin··on Mac OS Catalina: more trouble than it’s worth (Part 2)
While I don’t have that particular issue, I have other issues related to external screens, with 10.14 and 2018 MBP: I usually run the laptop with closed lid and an external screen at work and at home; and use it in “laptop mode” during my commute. Now, sometimes (once a week?) when I plug it into the external screen, it just won’t wake up, unless I open the lid, and then it still won’t recognize the external screen. Have not yet found out a reliable way to resolve this, but I usually manage with turning the monitor off and on again and/or unplugging/replugging it, possibly a couple times each.

Much worse is that sometimes (once a month?) during this process macOS completely messed up all my open windows: they are all resized to a tiny size. And I have dozens or hundred of them open. This is horribly annoying, and didn’t happen to me before (in 10.11; I skipped 10.12 and 10.13, for reasons similar to the OP. Before that, I went from 10.8 to 10.11; before that, I never missed a release, often was running beta of the OS etc.; but starting with 10.9, too many issues made this undesirable).

I dread switching to 10.15; unfortunately, I will get a new MBP 16” from work, which normally I’d relish, except that there seems to be no way to use it with anything but 10.15. I’ll see if I can delay it until 10.16 is out and will pray that they started to prioritize bug fixes again, but I have little hope that’ll actually happen.

BlackFingolfin··on O(n^2), again, now in Windows Management Instrumentation
Actually O(2n) did not convey this for me at all, all it did for me was cause confusion. If this ("turn it into two not nested loops") was indeed intended, I'd suggest to spell it out, not abuse notation
BlackFingolfin··on Pagers, faxes and cheques: Things that might seem obsolete, but aren't
But they have major drawbacks, too. Like: no encryption and authentication. And that means that e.g. critical medical data about a lot of people can be trivially snooped from the airwaves. This is not just hypothetical, it really works, and you can find multiple newspaper articles and reports online on this subject by googling a bit.

Worse, it is trivial to tamper with this and insert forged pager messages. A lot of harm could be done with this, possibly even leading to death of patients.

BlackFingolfin··on The Riemann Hypothesis
I think that's a misconception. Mathematicians are keenly aware that there are plenty examples in history were many people "believed" (hoped? expected?) that some result might be true because it would be "beautiful", but it turned out to be false. Or where numerical evidence suggested something only to turn out to be wrong in the end. And where the first counterexample only exists at huge, numerically infeasible bound (see e.g. https://en.wikipedia.org/wiki/Skewes%27s_number)

And hence a well-known suggestion is that when tackling a hard problem, is to try finding a proof on even days, and a counterexample on odd days...

And indeed, lots of people tried (and still try) to find counterexamples to, or otherwise disprove, the Riemann Hypothesis. However, there are indeed many, many results and heuristics that give a strong suggestion that the RH might be true -- far more than mere numerical results computing zeroes of the Zeta function. Of course none of them constitute a proof; but this really goes far beyond a simple hope for "beauty" in the theory.

BlackFingolfin··on Sunsetting Mercurial Support in Bitbucket
They don't need to allow browsing it; but at least have a minimal page which shows the presence of the repository, and allow cloning it.
BlackFingolfin··on Comparisons in C++20
But that first comparison function is usually not what you want, you want lexicographic ordering. This very example is in fact discussed in the article, as an example to how people often mess this up...
BlackFingolfin··on Chicken Scheme 5.1
Is it just me or are most of the navigation links on http://code.call-cc.org broken? I.e., "Download" at the top (which should simply link back to that page) links to https://codecall-ccorg/, "Eggs" links to https://eggscall-ccorg/ and also "API", "Tests" and "Bugs" are similarly broken. Only "Wiki" and "Manual" seem to be right. (And if I go to either of those two, then all navigation links seem to be right).

I tried to report this, but sorry, I can't be bothered to send an email to request an account for the bug tracker, then once granted, report the issue. I also tried to see if I could just make a pull request on their website repo, but I couldn't even find that ;-(

BlackFingolfin··on Mathematics all-in-one cheat-sheet (2013) [pdf]
OK, so, I also hate to be "that guy", but, despite the admirable effort put into creating this by the author, I am sad to say I don't see why some people are excited about this... Because unfortunately after just looking at a few pages, I saw lots and lots of error and misleading or plain confusing statements, basically on every single page I looked at closer, which makes me distrust it. Granted, these vary in their severity, but still...

Examples:

- p. 50, definition of a complex vector space, says " A complex vector space consists of the same set of axioms as the real case, but elements within the vector space are complex.". The vector space does not "consist" of the axiom, it adheres to them. And it makes no sense to say that the "elements" (vectors) are "complex". Rather, that scalars are allowed to be complex, not just real.

- p. 50: definition of a subspace is a mess. To pick just one obvious problem with it: What even are "axioms (a) and (b)"? Perhaps the three unlabeled "axioms" at the top of the page are meant (being closed under addition, additive inverses, and scalar multiplication)? But certainly the third one (axion "(c)"?) needs to be verified, too (whereas the second, about additive inverses, is redundant).

- p. 51 the examples at the top of the page end with mentioning C[a,b], the set of all continuous functions on an interval [a,b]. But then it claims that this is actually not an example, because "it has infinite dimensions". But really this is a perfectly fine vector space (also, we haven't even defined what a "dimension" is yet)

- p. 51, definition of linear independence says "c_1=c_2=c_n=0" which is missing a "=..." before the "=c_n"

- p. 52 the "general vector" given as a column vector doesn't make sense in a general vector space

- p. 53: "Matricis"

- p. 56 "Laprange's theorem" should be "Lagrange's theorem"

- p. 126: "EXPONETIAL"

- p. 167: "Matricies", "Prinicples", "opertaions",

- p. 168: "Determinate"; the formulas for 2x2 and 3x3 matrices implicitly assume a labeling of the entries which is never given, rendering this semi-useless

- one section is titled "MISELANIOUS"

And on page 38, the fields of real and complex numbers, R and C, are introduced as being written with a "blackboard" font (\mathbb), while on page 51 this is not followed (instead, we get \mathcal{R} and plain C). Why even introduce these conventions if they are then not followed?

Sure, many of these are minor and perhaps even "obvious" mistakes. But if you know the matter well enough to spot all of these, maybe you don't need this cheat sheet? Also, as a mathematician myself, my experience is that the number of spelling mistakes in a research paper (or in anything written and submitted by students) is a good first proxy for the quality of the text: if you can't be bothered to even run a spell checker on your text, should I really trust you to have verified all your computations and logical deductions carefully? (And no, I don't apply this to, say, posts here on HackerNews: I hate it when people shoot down a comment, or a twitter post, or whatever, just because it contains typo. But writing a book is a bit of a different affair, isn't it?).

Hence my point that I wouldn't want to suggest this to anybody as a reference. :-(

← PreviousPage 3 of 6Next →