Live data from Hacker News

Viewing profile — codys

codys

HN member
Joined
Thu, Oct 06, 2011, 5:53 PM UTC
HN karma
1,276
Public activity
415 items

About codys

podcast-again-1k@icloud.com

Recent public activity

  1. comment
    Comment #48951866

    Prompt regurgitation. Model was likely instructed to create the app to do this piece "by hand" (or a phrase with similar interpretation) because the author wanted to avoid pulling …

  2. comment
    Comment #48854603

    It'd be very unfortunate if Postgres didn't have regression tests for data loss due to bad io patterns. Should be possible to do some checks against those in an appropriate test ha…

  3. comment
    Comment #48527934

    Yes, I agree it would be very nice to have a way to integrate ACME into zeroserve. I'm not sure if zeroserve's plugin system might allow one to add a plugin to support it?

  4. comment
    Comment #48527871

    zeroserve doesn't use the Linux kernel's eBPF runtime to run the eBPF it uses, so the constraints of the Linux kernel's eBPF runtime (chosen because of how the Linux kernel thinks …

  5. comment
    Comment #48262667

    I hope this signals a departure from us being stuck without web usb in firefox too. It's a shame that I've been stuck using chrome for it. And maybe we'll get web bluetooth too.

  6. comment
    Comment #48153219

    I think their site is just slow, potentially because more people than they are used to are trying to view it. I was unable to load it initially (got an error from firefox) and had …

  7. comment
    Comment #48004199

    The idea with either requiring very wide band or frequency hopping on the 900Mhz band is to make it so that usages of the 900Mhz band 1. are tolerant to some loss (ie: by temporary…

  8. comment
    Comment #47732361

    The Apple way for hardware is more to design the thing so it breaks under normal use very quickly, and then refuse to replace it under warranty.

  9. comment
    Comment #47097323

    It's not a leading colon: It is a colon separator between the username and password, and the command used has the username as an empty string.

  10. comment
    Comment #47079039

    > Also, the "obvious reason" that American politics sent zero ex-presidents to prison is that Biden chickened out. So, there's that. Don't forget Ford deciding to protect his polit…

  11. comment
    Comment #47057704

    I'm not sure I follow. This outage seems like it occurred for less than 1 day. The post you link to is about having certificates expire after 45 days. What's the connection you see…

  12. comment
    Comment #47040917

    Seems you could use a single SQL statement for that particular formulation. Something like this, using CTEs is possible, but alternately one can reformat them as subqueries. (note:…

  13. comment
    Comment #47019143

    Garbage collection is not required for memory safety. Languages that have garbage collection are not all memory safe.

  14. comment
    Comment #46976630

    It seems like the messenger might endorse the message though, and is attempting to be coy. Folks should be careful of people using the "messenger" title to attempt to obtain the ap…

  15. comment
    Comment #46653961

    > So no one that actually has to renew these certificates. I believe google, who maintain chrome and are on the CAB, are an entity well known for hosting various websites (iirc, it…

  16. comment
    Comment #46653865

    OpenBSD does start X. And subsequently OpenBSD apparently hangs (or did so previously) when OpenBSD was running under Qemu. The subject in the parent comment changed to OpenBSD whe…

  17. comment
    Comment #46626666

    Possibly a better comparison (though a bit dated now) would be AT&T (or whatever telephone monopoly one had/has in their locality) charging an additional fee to use a telephone tha…

  18. comment
    Comment #46454806

    > I am assuming the message durability guarantees lean towards YOLO rather than ACID? "Core" nats doesn't have durability. Nats jetstream is the api built on top of nats that in th…

  19. comment
    Comment #46422558

    It seems it's just a part of a doc on style in tigerbeatle, in a similar way to the various "Google Style Guide" for code. These rarely have something new, but document what a part…

  20. comment
    Comment #46393170

    You've linked to a bug that was unintentional and was fixed. Go allowing torn writes for their slices and interfaces (their fat pointer types) is intentional behavior in the go imp…

  21. comment
    Comment #46389799

    Here's an example where a bug could exist in go due torn writes in a real program. I found this by searching for places where folks reload there config at runtime, as they are gene…

  22. comment
    Comment #46389421

    In that case, I can just refer back to my original comment: https://news.ycombinator.com/item?id=46388948 And then note that memorysafety.org says this (in case folks haven't read …

  23. comment
    Comment #46389382

    "at the moment" implies that Go would need to change for that statement to change, but instead we're waiting on a programer to make a mistake (A mistake that memory safe languages …

  24. comment
    Comment #46389157

    Interesting interpretation of that phrase. I think saying "probabilistically memory safe" would be more accurate (and more clearly communicate that idea), because we're betting on …

  25. comment
    Comment #46389125

    It sounds like you have a definition of memory safety you aren't disclosing. Please fully provide your definition of memory safety. Not interested in trying to figure out what it i…