To be fair, the thread is called "What are you working on", so it's by definition work-in-progress.
> Also: why would I as an applicant add more data for money? The landlord has the benefit, they should pay for that.
In many hot rental markets (My experience mostly with Berlin), you are mostly not in a position to say "the landlord should pay that" and everyone is desperate to supply the best, most complete and most convincing documents even if it feels bad to fork over that much personal data to a random stranger on a platform.
I know you said inspired, but it still feels a bit wrong to just copy paste the exact same landing page style and replace some words on it (https://once.com/campfire)
Yeah, I used it as a starting template. But beyond the layout, the copy and product are completely different. It just helped me get started faster, and I’ve always been open about that. Everything else (including the installer) is fully self-made.
Apple Music is not buttery smooth and was just a web view for a long time. I feel like I read that this changed a few years ago. This didn’t change the fact that it’s very slow.
There's also some parts of System Settings that were always web views, which I always found surprising for a company trying to make the case for native apps.
> 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.
Especially if you use any of the features that make Postgres nice to work with (For example good jsonb handling) these are immediately different than on sqlite and then won't work for development. Don't think there's a good reason for not running the same DB in both environments.
A nice benefit of prefixing by your-name/issue-1234-some-description is that many git clients will show it in a folder structure that way and it's easy to differentiate yours from other branches.
reply