Live data from Hacker News

Viewing profile — hjkgfdfgh

hjkgfdfgh

HN member
Joined
Tue, Feb 11, 2020, 7:31 PM UTC
HN karma
69
Public activity
12 items

About hjkgfdfgh

No profile information was provided.

Recent public activity

  1. comment
    Comment #22867169

    Yes, the described interaction with TM went down prior to contacting Amex, and was relayed to Amex. The form originally submitted for the online dispute detailed that, but the disp…

  2. comment
    Comment #22861098

    Good luck with the chargeback. I tried to open one with Amex online and it was insta-denied with a note to the effect that I needed to work it out with Ticketmaster myself. I'm hop…

  3. comment
    Comment #22835215

    To pile on against X11 over ssh, forwarding on a modern Linux workstation is spectacularly painful. I recently needed to forward a lightweight gtk app from one workstation to anoth…

  4. comment
    Comment #22825745

    If Signal were federated, there would be no single entity to shut down. Alas...

  5. comment
    Comment #22477223

    No. They just purchase votes.

  6. comment
    Comment #22316160

    Where are you trying to go with this? You start off trying to claim the entire class of vulnerability isn't possible because a few vendors made sane architectural decisions. When i…

  7. comment
    Comment #22316077

    In the context of Nextspace, Nextstep, or Windowmaker, it stands for Iconificaiton because it is "clearly a stylized depiction of" the icon that appears when a window is iconified.…

  8. comment
    Comment #22310277

    Passengers are (for the most part) considered equal for W&B calculations. It's about "Is this seat occupied?"

  9. comment
    Comment #22309655

    Seems clear they are interested in the NeXTSTEP aesthetic in addition to the underlying framework.

  10. comment
    Comment #22309604

    I wish something like this existed that could additionally proxy FCM notifications. Allowing push notifications without any Google involvement is the ideal long term goal, but one …

  11. comment
    Comment #22302140

    Qualcomm alone covers 40%, and they're arguably the most likely to correctly implement their MMU (nevermind they've seen quite a few vulnerabilities in their MMU implementations ov…

  12. comment
    Comment #22301864

    That may be true of Apple, and is true of the PinePhone and Librem, but for the majority of Android devices, that's blatantly false. On Qualcomm chipsets in particular heavily util…