> 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…
Show HN: DeepSeek My User Agent
131–140 of 153 posts
Re: Show HN: DeepSeek My User Agent
#132Earlier quoted context omitted.
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.
The only thing it doesn't identify as is Internet Explorer.
(Yes it's an old version, no I will update when I feel like it. Shush.)
Re: Show HN: DeepSeek My User Agent
#133Earlier quoted context omitted.
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
I don't know. You're probably right, but more and more it seems like mainstream websites aren't meant for human consumption. The less ads a page have, the more likely it is to have relevant content.
Classical targeted ads, where some sales person actively goes out and buy ad space on a few select locations, I feel like that's more valuable than ever, but not heavily used anymore.
Re: Show HN: DeepSeek My User Agent
#134seems 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
#135Earlier quoted context omitted.
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
#136Re: Show HN: DeepSeek My User Agent
#137Re: Show HN: DeepSeek My User Agent
#138> Okay, let's tackle this roast based on the user's browser info. First, I need to pick the three most unusual bits. The Safari version 18.1 stands out because that's a future version not released yet. The screen resolution of 1223x772 is an odd, non-standard size. The location is $LOCATION, which isn't too common, and the referrer is empty, meaning they came directly here. Wait, the referrer is empty. That's unusual. So maybe include that they came from nowhere. Also, the Safari version is ahead of current releases. The screen resolution isn't a typical size, so that's another point. $LOCATION could be linked to the screen size, like a quirky local landmark. Need to make sure to relate location to another attribute if used. Also, roast should be three sentences, concise. Let me structure it: start with the Safari version, mention the screen resolution, tie in $LOCATION with the screen size, and the empty referrer. Make it funny and snarky.
And the result is... well, what you'd expect given that reasoning:
> Safari 18.1? Nice try, time traveler—Apple hasn’t even heard of that version yet, but enjoy your 1223x772 screen resolution, the exact dimensions of $LOCATION's least impressive corn maze. You arrived here directly like a cryptid emerging from the woods, which tracks, because only a mythical creature would still run Mac OS 10.15.7.
Re: Show HN: DeepSeek My User Agent
#139Earlier quoted context omitted.
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…
I've been working on exactly this. Great to know there's some demand for it. It's now my daily driver for web access. It monitors for content I'm interested in (that's how I found your comment), handles all my searches and feeds, can dynamically adapt its interface, and is working on integrations to submit content for me so that I don't have to leave that interface to write these replies. Hoping to release it early M…
Anything that gets me closer to that original intention requirement before getting served content is a must-have in my books! Sign me up!
Re: Show HN: DeepSeek My User Agent
#140seems 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
DeepSeek is having major issues their https://platform.deepseek.com page now just 404s and https://status.deepseek.com is a red bar