Live data from Hacker News

Show HN: DeepSeek My User Agent

jasonthorsness.com

121–130 of 153 posts

Re: Show HN: DeepSeek My User Agent

#121

Dumbass DeepSeek calling my resolution low when it doesn't seem to know about device pixel ratio, what a noob

I’m surprised this is the only comment mentioning devicepixelratio. Most of the roasts from deepseek seem to involve roasting the window size but that’s misleading without DPR

I was wondering why it was showing mine wrong and why many people's resolution here was surprisingly low. TIL about DPR. Too bad that was the only good roast in my first result.

Refreshing the page gives a new one though, and it's done a pretty good job now!

Re: Show HN: DeepSeek My User Agent

#122
post #87

> Okay, let's tackle this roast based on the user's data. First, I need to pick the three most unusual bits. The user is using Safari 17.6 on Mac OS 10.15.7. Wait, macOS 10.15 is Catalina, which is pretty old now—like from 2019. That's a bit outdated, so that's unusual. Next, the screen resolution is 1024x1366. That's a taller screen than usual. Most common resolutions are wider, so maybe they're using an older iPad…

I got similar results and it was kind of hokey. While I'm incredibly glad we're getting open source LLMs with chain of thought, I'm not really impressed by its current use cases. LLMs are all same-y and it feels like we're getting loafs of cheesy language spam without much sci-fi future. I expect for this kind of tech to have really novel use cases. For it to sit between me and the internet and remove the ads, nuke t…

> It would be delightful if in 10 months from now, internet advertising no longer worked at all

Internet advertising will work as long as the internet exists. Classic targeted advertising on the other hand will no longer work but all it means is that it will be much more subtle and you will struggle to tell it apart in a way that you don't nowadays. Sounds a far more dangerous alternative

Re: Show HN: DeepSeek My User Agent

#123

> Okay, let's tackle this roast based on the user's data. First, I need to pick the three most unusual bits. The user is using Safari 17.6 on Mac OS 10.15.7. Wait, macOS 10.15 is Catalina, which is pretty old now—like from 2019. That's a bit outdated, so that's unusual. Next, the screen resolution is 1024x1366. That's a taller screen than usual. Most common resolutions are wider, so maybe they're using an older iPad…

It is not fair to judge the model performance on those guesses, if you have a look at the website you will see that the model is being told those parameters (os, screen size, etc). The model is not guessing those. Only thing that it might be guessing is your location

Re: Show HN: DeepSeek My User Agent

#124
post #19

Earlier quoted context omitted.

Funny that's basically how "growth" companies work in general

American "growth" companies aren't 100% funded by the USA Gov't with the only goal being to damage foreign national private sector companies. American companies are private sector only and have a business model that's to benefit a company, not a nation. In China all companies function as part of their National Party.

> American companies are private sector only and have a business model that's to benefit a company, not a nation.

How can you believe that when copyright laws only applied when regular people pirate but not when big tech uses pirates content to it train their AI? Also it's known that Pentagon funded many tech companies during cold war https://qz.com/the-pentagon-is-spending-billions-on-big-tech... . Is this not government funding?

Re: Show HN: DeepSeek My User Agent

#125
seems down for me, the POST request (seen in devtools) just gives a 504

    An error occurred with your deployment

    FUNCTION_INVOCATION_TIMEOUT

    lhr1::zcqst-1737978921661-18c020d7118c

Re: Show HN: DeepSeek My User Agent

#126
"Roasting your Hacker News refugee setup: flexing 20 CPU cores to doomscroll like a Linux-dad cyborg in Sherman Oaks, rocking Chrome 131.0.0.0 like you're personally beta-testing Google's most basic Blink update, yet still stuck at 1080p like a peasant who thinks "4K" is a cryptocurrency."

Glorious.

Re: Show HN: DeepSeek My User Agent

#127
post #119

Earlier quoted context omitted.

And that’s why so many kids had trouble registering their iPad on our network. As it would not send the mobile registration to the iPads

It's not an iPad or Apple issue if your registration system is using the User-Agent for weird reasons.

Sure it does, but Apple should be sending the correct User Agent string, not making one up.

Re: Show HN: DeepSeek My User Agent

#128
post #116

Earlier quoted context omitted.

And that’s why so many kids had trouble registering their iPad on our network. As it would not send the mobile registration to the iPads

Don’t know about your particular problem, but I’m pretty sure it was largely a response to iPads being sent to mobile sites with horrible usability thanks to navigator.userAgent.match(/iPhone|iPad|iPod/) or the server-side equivalent. The problem was amplified by the release of the 12.9’’ iPad Pro, so self-identifying as a Mac made sense.

Its not a Mac though. I'd much prefer Apple use the User Agent correctly rather than hack around it like that.

The system we used did use user agents to identify mobile devices or computers. And gave the iPad users a terrible experience because Apple lied.

Re: Show HN: DeepSeek My User Agent

#129

"You spent 46 seconds lurking on Hacker News just to end up here with your four Chrome cores and Linux OS in the tech capital of San Jose—did you compile the courage to click? Your 8.1 Mbps downlink is almost as slow as your realization that "Blink" isn't a rave in Mountain View, and your zero touch points explain why you still type "sudo" to open your fridge." :sob: I'm getting roasted by an AI

I can practically already hear the conversations that will be overheard while waiting in line at Red Rock Coffee later today..

Re: Show HN: DeepSeek My User Agent

#130
post #119

Earlier quoted context omitted.

It's not an iPad or Apple issue if your registration system is using the User-Agent for weird reasons.

Sure it does, but Apple should be sending the correct User Agent string, not making one up.

Browsers have been lying about their identities via their user agent strings since 1995.
Post reply on HN