Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
JDye
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
by
JDye
5mo ago
Reads like a horoscope, just vague stuff that's always gonna be slightly true... Picture of me in Oslo and it says "he enjoys travel". And then some really weird stuff: "he may also have a penchant for video games, exces
2.
▲
by
JDye
7mo ago
It's more "just put it in A database". If someone said MongoDB I'd be just as happy.
3.
▲
by
JDye
7mo ago
We've had an interesting experience on the interviewing side of this. Asking a system design question and getting answers involving multiple layers of caching, pub/sub, event-driven whatever/etc.. when the real answer is to j
4.
▲
by
JDye
7mo ago
It may look like they're all easily interchangable because the UI and actions are similar (you have a viewport and can do extrudes, etc..) but fundamentally, they're all working on very different objects at their core. Blender and
5.
▲
by
JDye
8mo ago
Residential proxies aren't used for scraping? That doesn't align well with my experience...
6.
▲
by
JDye
8mo ago
Thanks lad. Will get right on it.
7.
▲
by
JDye
8mo ago
I agree that write-actions should be protected, especially now when every other person online is a bot. As for read-actions, I'll continue to profit off those being protected too but I wouldn't be too bothered if something suddenl
8.
▲
by
JDye
8mo ago
I live in the UK and can't view a large portion of the internet without having to submit my ID to _every_ site serving anything deemed "not safe the for the children". I had a question about a new piercing and couldn't g
9.
▲
by
JDye
8mo ago
2k IPs is not enough to do most enterprise scale scraping. Starlink's entire ASN doesn't seem to have enough V4 addresses to handle it even.
10.
▲
by
JDye
8mo ago
Our postgres replication suddenly stopped working and it took three of us hours - maybe days - of looking through the postgres source before we actually accepted it wasn't us or our hosting provider being stupid and submitted a ticket.
11.
▲
by
JDye
8mo ago
I've taken time today to do this. With some of your suggestions, I am seeing an improvement in it's ability to do some of the grunt work I mentioned. It just saved me an hour refactoring a large protocol implementation into a few
12.
▲
by
JDye
8mo ago
We have an in-house, Rust-based proxy server. Claude is unable to contribute to it meaningfully outside of grunt work like minor refactors across many files. It doesn't seem to understand proxying and how it works on both a protocol le
13.
▲
by
JDye
8mo ago
I don't mean that you can't do it, just that there is no company offering it so right now those are the only two options. It's something we're experimenting with currently. the other commenter is right about apple produc
14.
▲
by
JDye
9mo ago
Not really. You can have 100,000 IPs from proxies or use VPNs and have only 5 egress IPs. Anybody who wants to stop the scraper could get browser fingerprints, cross reference similar ones with those IPs and quite safely ban them as its hig
15.
▲
by
JDye
9mo ago
Web scrapers maybe aren't "bad actors", but many sites dont want them. They'll use tons of TCP proxies which route them through a rotating pool of end user devices (mobiles, routers, etc...). Its not really possible to b
16.
▲
by
JDye
9mo ago
BrighData offer H3/QUIC but only in beta and you have to contact their sales team as far as I'm aware. We (PingProxies) might be the only company to offer H3 to the proxy/QUIC to the target using the CONNECT-UDP method public
17.
▲
by
JDye
9mo ago
I mentioned this in a podcast recently; fingerprinting of proxy servers using QUIC is a lot harder as UDP doesnt have enough headers to allow for unique characteristics like a TCP does. Theres no way to include a timestamp in a UDP datagr
18.
▲
by
JDye
9mo ago
The most common method of proxying with residential proxies is still CONNECT tunnels and from my tests it catches a resi-proxy about 50% of the time. More with tuning of the score thresholds.
19.
▲
by
JDye
9mo ago
A request to a HTTPS target through a proxy will use a CONNECT request to establish a tunnel to the target. This tunnel operates at layer 3, where the client sends TCP segments to the proxy, the server unpacks the segments and then repacks
20.
▲
by
JDye
9mo ago
If the proxy can "see" the requests, then this isnt an issue because the headers can be trivially be modified. The problem is that the proxies which are targets of identification - think proxies for large scale web scraping which
21.
▲
by
JDye
9mo ago
Can't even write a comment without an LLM...
22.
▲
by
JDye
9mo ago
I'm testing using our residential proxies. It's a super cool tool, I've been wondering about an open source tool doing this since reading about the technique in one of Nikolai Tschacher's blog posts years ago ( https:&#x
23.
▲
by
JDye
9mo ago
To answer your first question, in my tests its around 50% of requests making it through.
24.
▲
by
JDye
9mo ago
Surprised TCP/IP Illustrated (Volume 1) has only been mentioned 6 times. It's been so helpful for me, so many times. Perhaps it's because most people haven't had writing a TCP stack as part of their day job, but it'
25.
▲
by
JDye
9mo ago
Our codebase is full of this pattern and I love it. Every time I get clean up temporaries and expose an immutable variable outside of the setup, makes me way too happy. A lot of the time it looks like this: let config = { let conf