Live data from Hacker News

Viewing profile — rebane2001

rebane2001

HN member
Joined
Sun, Nov 11, 2018, 4:03 PM UTC
HN karma
617
Public activity
129 items

About rebane2001

[ my public key: https://keybase.io/rebane2001; my proof: https://keybase.io/rebane2001/sigs/4HkMB7oA7B6H8AEWU_hxCpivtZX1EEixF0aYbsc1Yxg ]

Recent public activity

  1. comment
    Comment #48786040

    this reads like slop

  2. comment
    Comment #48739638

    No, the API will not return the admin-only removal reason. The code path that causes this is in the post.

  3. comment
    Comment #48738878

    wait what the heck yeah, this is the same post as from a few days ago, i guess the comment and post timestamps got glitched??

  4. comment
    Comment #48617309

    (author of x86css) Not possible, but it would be possible to reimplement Quake's logic and controls in CSS to have it run without JS. I was considering doing that for my next CSS c…

  5. story
  6. comment
    Comment #48256731

    You cannot close HTML tags that way anyways, and are the same, as are and . The spec defines whether an element self-closes, the slash is just ignored.

  7. comment
    Comment #47576685

    (author of x86css) not only do i think doom in css is possible, but both me and another css person were also planning on actually making it into reality but it sort of feels demoti…

  8. comment
    Comment #47337183

    the difference is that knowing 2^8 is generally not useful to people who don't know it this here is something that's pretty useful to most ssh users, yet seldom spoken of a better …

  9. comment
    Comment #47336895

    tldr is so good, i wish it was a part of the os the same way manpages are just to help out newcomers

  10. comment
    Comment #47143335

    it's a placeholder that gets replaces by the python script on build

  11. comment
    Comment #47143148

    Yes, CSS binary data transfer is possible in bith directions.

  12. comment
    Comment #47140599

    clock != looping, those examples already loop (dont need a line per iteration), but just dont have a built-in clock and requiring a clock is imo dismissable, because pretty much al…

  13. comment
    Comment #47138242

    I think x86 is still good because it's easily understandable. If I say it's an 8086 emulator, people who aren't familiar with the 8086 aren't gonna go "oh so like an older version …

  14. comment
    Comment #47136169

    It's really easy, I was considering adding it. The easiest way is to make an @property that's animated at ridiculous speeds that can be sampled to get (sort of) random bits.

  15. comment
    Comment #47134790

    I did not use any AI

  16. comment
    Comment #47134551

    When you download an x86 program you're making a lot of other assumptions too, such as what the target operating system and hardware are. Even 8086 MSDOS software won't directly wo…

  17. comment
    Comment #47134429

    That wikipedia article lists the 8086 in its "Chronology of x86 processors" section as an x86-16 CPU.

  18. comment
    Comment #47134415

    Why is the 8086 not equivalent to x86? PCLMULHQHQDQ is from the CLMUL extension, which only began appearing in CPUs in the early 2010s - are CPUs from before then not x86?

  19. comment
    Comment #47134374

    I wasn't sure whether to address the disconnect in the FAQ - I wanted it to be short and readable. The idea is that, since a long time ago, there has always been demos that prove t…

  20. comment
    Comment #47134348

    8086 is x86 https://en.wikipedia.org/wiki/X86

  21. comment
    Comment #47132733

    i'm glad llms won't be coming after my niche anytime soon

  22. comment
    Comment #47132725

    I do actually have a CSS CVE[0] in Chrome, but it was in the changelog as "in Animation" instead of "in CSS", so no fun stories/headlines for me :c [0] https://chromereleases.googl…

  23. comment
    Comment #47132696

    It relies on a few things, but @functions, if() statements, and container style queries are the main ones.

  24. story
  25. comment
    Comment #46871508

    I've now added the algorithm explanation to the GitHub README.