Live data from Hacker News

Viewing profile — mjw1007

mjw1007

HN member
Joined
Sun, Jan 29, 2017, 10:34 AM UTC
HN karma
4,910
Public activity
997 items

About mjw1007

No profile information was provided.

Recent public activity

  1. comment
    Comment #49113538

    The physical replication docs say "the hardware architecture must be the same", though they don't define "architecture".

  2. comment
    Comment #49113033

    I think the postgresql maintainers don't claim to support moving a database from x86 to arm without a dump-and-reload. The docs tend to say "same hardware architecture". Though if …

  3. comment
    Comment #48122558

    GitHub also centralises abuse detection. I'm not thinking about sophisticated attacks here so much as dealing with plain old spam. That's fairly easy to deal with on a tiny scale, …

  4. comment
    Comment #47239624

    It's common that if you extract a function or a module with a well defined interface, that function or module can't tell whether a "bad" input indicates an expected or an unexpecte…

  5. comment
    Comment #46982178

    Not any more, according to this article you're commenting on, no.

  6. comment
    Comment #46364675

    > If a package hosted by Fedora or Debian or PyPI or crates.io, etc claims to correspond to an upstream git commit or release, then the hosting system should build the package, fro…

  7. comment
    Comment #46110892

    They weren't in any way attempting to rely on security by obscurity. They didn't assume nobody would guess the URL. They did take active steps to ensure the data was only available…

  8. comment
    Comment #46026658

    Is this a real judge, or is an "Immigration Judge" one of those not-actually-a-judge decisionmakers employed by the executive?

  9. comment
    Comment #45844778

    I think what you've written is pretty much what the "almost all programs have paths that crash" was intended to convey. I think "perhaps the density of crashes will be tolerable" m…

  10. comment
    Comment #45626507

    It makes tab completion work.

  11. comment
    Comment #45351066

    One of the things that this group of "stewards" could do to get their costs down is get together and implement a high quality free software caching proxy that understands all their…

  12. comment
    Comment #45061679

    It's clear from that bug tracker that you shouldn't let libxlst see untrusted stylesheets or xpath expressions. I haven't yet seen a problem with running your own transformations a…

  13. comment
    Comment #44927519

    There's still work being done on the Reference, which is being maintained in the same way as it has been since the Rust documentation team was disbanded in 2020. But it's a very lo…

  14. comment
    Comment #44927095

    The plan described in "Our Vision for the Rust Specification", and the linked RFC3355, were abandoned early in 2024. The team that was formed to carry out RFC3355 still exists, tho…

  15. comment
    Comment #44570397

    Also vidir, which is in the moreutils package in popular distros.

  16. comment
    Comment #44525146

    It's supposed to be 10^5 W heating per square metre, and the aeroplane's cross-section is much smaller than a square metre.

  17. comment
    Comment #44479396

    My mistake. The support for writing CGI programs in Python is in wsgiref.handlers.CGIHandler .

  18. comment
    Comment #44478819

    The Python maintainers are removing the module _named_ cgi, but they're not removing the support for implementing CGI scripts, which is CGIHTTPRequestHandler in the http.server mod…

  19. comment
    Comment #44385727

    It would be better if there was a layer of maintainers between the free software authors and the end users that could act as a buffer in cases like this, in particular to take care…

  20. comment
    Comment #43749662

    I agree it can be domain-specific, but I think it's more common than not that empty containers, and the number zero, are corner cases rather than typical values. So I think it woul…

  21. comment
  22. comment
    Comment #43747119

    I've found in practice that shrinking to get the "smallest amount of detail" is often unhelpful. Suppose I have a function which takes four string parameters, and I have a bug whic…

  23. comment
    Comment #43514872

    I suggest it would be helpful if the README's intro expanded a little more on the project's scope. "for postgres" is a bit vague, and "focusing on developer experience and reliable…

  24. comment
    Comment #43499320

    A year or so ago I read through one smallish section (basically function calls) and filed issues for the problems I found that were easy to write up crisply. They fixed the easy bu…

  25. comment