At this point one must assume that any "free" vpn software is free because it uses its install base for DDoS / other traffic abuse.
2,531 karma · joined September 7, 2014
At this point one must assume that any "free" vpn software is free because it uses its install base for DDoS / other traffic abuse.
For a while, we had to just set off pagers when global traffic exceeded a threshold and manually toggle the extra hardening, but eventually it became a lot more reactive.
The main idea here is that at some point just leaving the scrape running in a way that didn't overwhelm my backend would have resulted in me not caring enough to do that. But now they get nothing. Even if you're borrowing bandwidth and not paying, you should be a good neighbor is all.
There's only so much you can really do when your underlying resource is so limited. Luckily the value of the query is lower than the cost of a recaptcha solve, so the attackers moved on to some other target.
Ironically I could now turn off the endpoint protection (or have it responsive to traffic load), until the attackers return. I shall not go into too many details, no need to give people a map.
I was keeping an eye on it, because we are hard-capped at 100 QPS to our provider, beyond that and they start dropping our traffic (and it is an outside provider, bundling domain registries like verisign and stuff), which makes regular users break if their traffic gets unlucky.
Anyway, after a week of 40qps, they start spiking to 200+, and we pull the plug on the whole thing: now each request to our endpoint requires a recaptcha token. This is not great (more friction for legit users = more churn) but it is successful. IF they had only kept their QPS low, nobody would have cared. I wanted to send some kind of response code like, "nearing quota".
FTR before people ask: it was quite difficult to stop this particular attack, since it worked like a DDOS, smeared across a _large_ number of ipv4 and ipv6 requesters. 50 QPS just isn't enough quota to do stuff like reactively banning IP numbers if the attacker has millions of IPs available.
Under what circumstances would a link you click on a website or an email _ever_ be a trusted file?
Some history. https://elemental.medium.com/the-bizarre-and-racist-history-...
The problem, ultimately, cannot be solved without disassembling neoliberal capitalism. It is more or less endemic to the system. To a large extent that short termist, get returns and move on before the cost is due, mode of being is how we managed to run an economy that requires constant growth (rather than stability) to function. It's also why we won't solve any of our climate or many social issues.
There's no way to change this without drastically restructuring the utility function people apply to decisions, and that just won't happen until the aftermath of whatever collapse is inevitably going to happen when the planet floods.
On the other hand, I recognize that doing this well and correctly (understanding how to pipe together operators instead of creating lots of intermediate subscriptions manually, which I see a lot in example / stack overflow code) requires a high level of understanding.
It is a whole change in how you think about event pipelines and code structure. I don't think I would want to migrate my day job systems to it, because then you need everyone on the team to develop that understanding. I'm sure they _could_, but working with promises and trad event handlers is a lot simpler, as long as you keep the rest of the data / eventing pipelines simple.
As with most things, it depends a lot on the history you have with those people and the psychological safety you feel, so it depends? Definitely not with someone I just met and is interviewing me for a job.
And FWIW I also don't interview anywhere there are questions like this.
personally, i use an xps15/windows/WSL, mainly because i also use the laptop for video games and so on.
It does also prevent accidental zooms when users intend to scroll, so maybe that's a use? Often times the meta viewport tag (which is quite arcane) is just copy-pasted without deep knowledge of what it does.
But, people are pretty remarkably bad at asking for things. It's mostly the "better horse" problem. People ask for fixes to proximal issues (make this faster, cheaper, better) and not the big things.
In my own product, we use gtm to understand where in our sign up funnel people fall off. It is a complicated product and a complicated sign up flow. Since people who fall out of the funnel are unreachable, we can't just ask them why. But we can observe that (say) 40% of users bounce off of step X, so let's make that step easier.
I would suspect that a large number of engineers working in crypto are heavily motivated by money above all.
#define private public
#import <something.h>
then you can interact with your class private fields all you want.I personally wouldn't pay ridiculous prices for them, but as I live in the SF bay area I keep an eye out when they're in season and you can usually buy them for $20 a pound or so (and a pound is a lot of mushrooms). trim off the dirt, slice them, sautee them in a little fat with onion and garlic, add in some soy sauce, white wine, maybe chicken stock, maybe strips of chicken.
The main thing with matsutake is, like truffles, they have not really been domesticated. You have to forage for them.
There's all sorts of interesting things about mushrooms- the mycelium ends up connecting multiple trees together, and they act in symbiotic relationship to each other, in terms of exchanging minerals and nutrients (which is apparently why they haven't been domesticated yet).
There's a general dislike of special-casing all build deploy run pipelines for some team's snowflake needs, since once you put a feature in, you have to support it forever. So one suggestion is that you look really closely at your own service and ask: can you change that to fit the framework? The majority of times an infra eng gets a request that amounts to "we can't use the framework until it does X", the answer is actually, "you should not want to do X, for reasons Y".
This might not be your specific issue, but if you want the thing soon, work on the parts of the codebase you do have control over.
And in general, yes. This is how big companies tend to work. Teams plan out effort far in advance. I have an ask to a sister team right now for 2022 planning, and I would be delighted if they came back and said "Q1". There's a million things all going on at once.
Not sure if you read the linked science article, but there is plenty of evidence that Asperger did some terrible stuff. Not surprising, given the interest in eugenics that was wide-spread at the time, but still terrible enough that yeah, we should probably stop naming things after him.
Parenthetically, if you are interested in making an argument where other people presume good faith on your behalf, avoid the term "cancel culture". Like "virtue signaling" it is a turn of phrase that strongly correlates with bad faith argumentation.
Instead of arguing around the point, go straight for it - don't say "cancel culture is bad therefore we cannot ever question the actions of people who did questionable stuff", instead face the actions directly and say "Yes. Asperger sent kids to be killed because he didn't want their parents to spend time caring for humans he saw as a drain on society, but he did all this other great stuff trying to highlight how 'autistic psychopaths' (his words) would strengthen German society, so we clearly should continue respecting him". Or whatever it is you respect about Hans, you should be able to say, "Despite all the heinous stuff he did, I respect him because of XYZ". Personally, I am all for canceling Asperger (op. cit).
When you just complain about "cancel culture" and don't address the core issue, it is intellectually lazy.
As to the central thesis here- I'm sure that there are different between neurotypical and autistic people. I'm even sure that those differences cluster. That's not the point of the linked article (or its sole source, which others have pointed out is also unsourced) and it is bad faith to argue otherwise.
The linked article claims single causes for most of the claimed observations, almost always rooted in a supposed (and incorrect) universal lack of empathy. Some autistic people behave in a way that implies a lack of empathy, but (a) not all and (b) that only means neurotypicals think they lack empathy, whether or not they do is another thing entirely.
Presenting an unsourced laundry list encourages people to presume that all autistic people are alike, and that the phenomenon is well-understood. It is reductive, and no more useful that any other "scientific" stereotype about race or gender (or zodiac sign for that matter).
On "aspie", I've seen the word used as a dismissive insult too often to consider it a label I'd appreciate applied to me. But that is kind of why I hedged it. If you want to call yourself that, go for it. I mainly wanted to highlight that it is a fraught term and that it is not universally applicable.