it's the other way around: `wait_for` waits for the next refresh (there is configurable refresh interval, 1s by default), `refresh: true` forces refresh without waiting for the next refresh interval.
the difference is that waiting for refresh assures that the data will be available for search after the "insert" finishes. forcing refresh might be foot gun that will criple the servers.
in my case, i ultimately introduced linters, formatters, git hooks, gh actions, etc. i've tried to explain and tried other things, but it felt like babysitting at that point. if someone is unaware of their own weaknesses, there isn’t really much you can do about it; you'll just end up fighting, which will make both of you resent each other
make everything as code, introduce linters, formatters, hooks and checks. when you work in a small team with people of a relatively similar mindset, such things aren't necessary, but when the team grows, there will always be issues with such things. so having a mechanism to enforce rules is necessary for your own sake
very nice. there are things that won't show up in the network panel and you had to resort to proxy for debugging, especially when you are using puppeteer/etc for testing.
recently had to research "residential proxy", and the number of websites that claim that they have millions of IPs on hand was very strange. then the fact that a lot of them work in the exact same way, and a lot of them accepted payment mostly in crypto was very strange. so now connecting the dots, makes sense now why these "residential proxy" websites looked and worked the same way
Additionally, there's almost no ethical use for a residential proxy. The purpose is always to deceive, at best you get lightly unethical uses like "avoiding georestrictions on IP distributors like netflix", or "avoiding controls in dictatorships" which is acknowledging that it is used to break the law, but maybe it's the wrong kind of law.
Even these soft reasons to use VPNs and residential proxies are like an alibi for bad actors, is IP 25.14.xx.xx creating a fake account on twitter to spread malware or is he downloading a show that wasn't available before? I guess we'll never know such are the limits of privacy I guess.
It's analogous to people using other people's accounts (with or without their well-informed permission) for small to moderate amounts of illegal transactions. It's a simple strategy but it's actually very hard for authorities to completely stop as your illicit activity gets lost in the huge amount of everyday noise
I've been thinking about building an actually-ethical residential proxy system, for censorship-evasion purposes.
The internet in a growing number of countries is censored, but different content categories are censored in each jurisdiction. Many sites and services also block known VPNs (i.e. non-residential IPs), so that doesn't work as a bypass in all cases.
I have trusted friends in other countries, so by mutual agreement we could set up wireguard links for each other to use (subject to agreed terms). It just needs some way to intelligently route traffic depending on which jurisdictions will allow which requests (i.e. "which is the lowest-latency link that will allow this request").
> there's no such thing as an ethically sourced residential proxy.
There is, just like you giving your attention and cpu to watch free ad supported content on the internet. It's the same in apps that give users access for free in return for bandwidth, or free VPNs that allow you to share bandwidth. There's also ISP "residential" proxies where ISPs re-sell some of their address space to proxy providers.
If it’s to enable users to fetch their own data, it’s absolutely ethical. These websites can offer API’s so people can access their own data “above the board” but instead make it incredibly difficult.
"Users fetching their own data" is probably less than a hundredth of a percent of traffic passing through residential proxies, I'd even bet some money on that.
Not much different than blocking access to people without JS enabled, blocking people stuck behind NAT, blocking whole countries or require them to solve Cloudflare captchas.
What does any of this have to do with residential proxies? If you can't access a website because you have disabled JS, you won't be able to access that website with a residential proxy either.
I was referring to the fact that many websites block / force users to use the resource in a certain way, why shouldn't they in return have the right to bypass these restrictions.
A residential proxy can not be used to bypass the restriction on JavaScript. Regarding the other items on your list, sure, a residential proxy could be used, but why do you need it? Why not a regular datacenter proxy?
This was a general statement, no need to nitpick every detail. DC proxies are not as accurate for geolocation, they are also often flagged as such or face higher scrutiny from bot protections.
Okay, sure, in theory someone could use a residential proxy to evade unjust blocking. Whether that has happened at any point in history or not, I'm not sure.
In practice, the vast majority of residential proxy usage would be for other (non-ethical) purposes.
it happened because the story of dependencies (system & application) was terrible. the ability to run the app on different distribution/kernel/compiler/etc was hard. there were different solutions like vagrant, but they were heavy and the DX wasn't there
exactly, i'm using "google phones" since nexus s, and they always have some discounts few months after release. other thing is that they currently offer 5y of updates, so even one year later with heavy discounts the phones are still good. i've got my P8 Pro with 1/3 discount
it is madness, you would be surprised how many ppl take things too serious. been there, had talk with HR cause i've said that the solution is mediocre and we have to do something better than that.
the difference is that waiting for refresh assures that the data will be available for search after the "insert" finishes. forcing refresh might be foot gun that will criple the servers.