Live data from Hacker News

Viewing profile — dejanseo

dejanseo

HN member
Joined
Wed, Oct 22, 2014, 7:23 AM UTC
HN karma
331
Public activity
24 items

About dejanseo

I use machine learning and mechanistic interpretability to optimize brand visibility in AI search: https://dejan.ai/

Recent public activity

  1. comment
    Comment #49458599

    Bulls eye! https://z.ai/blog/glm-5.3-flash

  2. comment
    Comment #49450249

    PS: https://z.ai/blog/glm-5.3-flash

  3. comment
    Comment #49431604

    This looks spot on, where is it from?

  4. comment
    Comment #49431558

    Hey, it may be trivial, I'm pretty proud of it :)

  5. comment
    Comment #49431548

    Hello! I wrote the above article and did the NCD on model outputs. The same thought crossed my mind when I saw Gemma misclassified as Gemini quite frequently. And GLM almost as Cla…

  6. comment
    Comment #49431459

    Author here. Tell me more. How do you use NCD and what is your concern about its application here? Should I have use da larger reference sample? You can test it in action here: htt…

  7. comment
    Comment #49255141

    > "Claude models launched on or after August 2, 2026 support marking at launch." No Anthropic model has been launched in August.

  8. comment
    Comment #17827589

    Google? When I brought a serious issue up in 2012 https://dejanseo.com.au/hijack/ Google never fixed it: In summary, I can take any of your (or anyone else's content) pass more pag…

  9. comment
    Comment #17827533

    The irony...

  10. comment
    Comment #17827518

    Trying to be objective and understand my own motivations here. Obviously I didn't do anything out of malice. But yes, I could have told Google directly about the problem, but then …

  11. comment
    Comment #17827470

    I hope so, and I also hope Chrome gets a fix for this.

  12. comment
    Comment #17827465

    Thank you! :)

  13. comment
    Comment #17826561

    Thank you. I'm not having a good time at the moment. Anyway, the basis of my test hypothesis is that people are easily fooled by URL both by HTTPS and brand recognition (e.g. subdo…

  14. comment
    Comment #17826490

    Thank you, I did mess up and wish I could take it back. To everyone bashing on me, I'm truly sorry to offend so many people. That was not the intention. This was purely as you desc…

  15. comment
    Comment #17825447

    Not the first time either. Every now and again I get an interesting idea, test it and share it with the world. The test that was left forgotten had no commercial impact on anyone a…

  16. comment
    Comment #17825318

    I just added a screenshot from search console: https://dejanseo.com.au/competitor-hack/ There's no manual penalty notice.

  17. comment
    Comment #17825310

    Where did I say I'm proud of this? Everyone keeps saying "proud". I chose to share it in public because it's a serious problem that others may be using it to do real harm. I blog a…

  18. comment
    Comment #17825199

    That would be marvellous.

  19. comment
    Comment #17825190

    You're welcome.

  20. comment
    Comment #17825188

    Hey, that's not very nice.

  21. comment
    Comment #17825184

    That's exactly right. Google has already punished me once for exposing a flaw (which they still haven't fixed): https://news.ycombinator.com/item?id=4748094

  22. comment
    Comment #17825177

    Thank you Cyrus. I thought it would be obvious that this isn't a practical tactic a reputable brand could risk doing.

  23. comment
    Comment #17825137

    Hi everyone! I did this. It was just a random cool idea I wanted to try. It worked a little too well and I quickly moved it to a disposable site to test if the page will get penali…

  24. story