niwork

Nice windup but I'll take the bait. It's hardly the same, is it? Doing something known to be very safe versus doing something known to be very dangerous, knowing full well that you're violating the law. What do you propose instead?

That sounds nice in practice, but in our post-truth, post-evidence world I am not sure what else we can do. It's impossible to dissuade some of these people and many people viewing YouTube are vulnerable to falling for their bullshit.

How would it work if you had a VPN and a private certificate installed on your browser?

1. Traffic encrypted in browser using SSL

2. Traffic routed to VPN server

3. Traffic routed to target web server over public internet*

4. Back to VPN server

5. Back to browser

*I assume at this point the Kazakh government can intercept the traffic and decrypted the HTTPS traffic, but that would itself be garbage because it's been encrypted by the VPN. Is this correct?

Your comment made me look into this in further detail and you may be right; it seems the situation isn't as bad as it once was.

> in April 2018, when the high court found the government’s power to order private companies to store communications data, including internet history, to be in breach of citizens' right to privacy.

It seems the original proposal has been watered down and then challenged in court. I'm wondering if someone more knowledgable can chime in.

Still, I don't want some government agency to be able to pull my entire browsing history, now or in the future.

My main reason for using a proxy is to prevent my government from tracking and logging all my internet activity (when you look at the huge list of agencies the UK government has allowed access to that information you can see why).

I skimmed through this article but I don't think it addressed this use case. Sure, my VPN could be tracking me, but I have much more trust in Mozilla than I do any other internety company. This article seems to be arguing that because perfect browsing privacy isn't possible that you might as well not bother with any.

Thanks for the pointers.

Achieving the parallax seems to be easy enough, but combining it with all these aminations seems a bit more tricky. The animations are more complex than animate.css's approach of just animating when the component is displayed - you can play the animation in reverse by scrolling up rather than down.

I've seen the New York Times and BBC produces stories told in that parallax / animated type way and it's very effective. I'm guessing therefore that they use a standard parallax approach and them one or more animation libraries together; I was hoping there was one neat library that brought it all together but maybe that's asking for too much.

Know of any libraries that will achieve this kind of parallax scrolling-to-reveal rather than just scroll between pages?

This kind of design has its place but this probably isn't it.

I am curious what they've used to achieve the endless scrolling type parallax. A while back I looked for libraries to achieve this and didn't find anything other than fullPage.js which doesn't seem to have an option for this (only full page transitions).

The fix for this is supposed to be go to into your Android settings and turn off battery optimization for Google Home and each app you cast.

It didn't work for me but loads of people reported success with it. It's a shame because I loved the Chromecast but had the exact same issue as you describe.

How relevant is architecture for someone like me - a 5-10 years of experience dev who has worked in non-managerial developer positions in small teams.

When I look at architecture patterns I feel so much of it is aimed at enormous projects, in which case I think you need actual experience of working in an enormous project alongside others from whom you can learn rather than just reading it from a book.

And there's so much difference between them.. which is the "right" one? Is Robert C. Martin's "Clean Architecture" approach right in condition X, or some other approach in condition Y?

Can you give an example of that? What have you been doing?

> i imagine they don't appear on public places like linkedin

Can they do that? Just hire through a small network of people in the know? Sounds like a recipe for cronyism.

I'm not sure about Italy but in the UK companies legally have to advertise a job publicly and, if they receive an application that meets the criteria, I think they have to at least consider it, if not conduct an interview. That's not to say there is no nepotism, but there are measures to control it.

Remote jobs paying 6 figures? Aren't they flooded with Indian applicants? Why can I hire an outsourced Indian or Ukrainian for £10,000 PA then? Sounds weird..

What about starting salaries, salaries at 2 years, 5 years etc.?

Where in the UK are you based?

Don't get disheartened when you read these big salaries online. The average reader isn't bothering to post theirs.

The UK is actually pretty good when it comes to IT salaries. Go to France, for example, and they're much lower. The attitude to devs is quite poor in a lot of places, treating us like we're one rung above car mechanics. We also have a good contract market in the UK; in many other EU countries (even Australia) contractors make peanuts in comparison.

Outsourcing and the low barrier-to-entry have all dampened IT salaries. Immigration has also played a part in the UK over the last 15 years; a lot of devs from Eastern Europe have gone where the money is - i.e. here. I know it's a contentious issue here but I say that with no malice. I'd do it too if I was them, and a lot of them are talented devs, but there's no point pretending it hasn't had an impact.

That's a very poor salary for your job, if you don't mind me saying. Are you in Italy? What's the cost of living like?

Salaries in Europe are generally quite low for devs compared to the US. I think it's best in the UK.

Starting salary will average ~£25k, rising to ~£35k as you get more senior, then maybe £~45-55k one you're 5-10 years in.

This is excluding London and contract-based work, of course.