2,457 karma · joined February 16, 2018
consoles are sold at a loss, best information i can dig up is that this is still true today, even after all the volume.
unfortunately, no.
and then up the stack a bit, they are confused about DNS' role in attack mitigation, at least generally speaking. perhaps there is something specific to their own DNS setup where this made a difference. they should just strike that part of the PM entirely.
that said, their reaction time is amazing. this would have included live troubleshooting during an ongoing incident! criticism aside, i wouldn't hesitate to use them if I wanted EU service.
instead of "i'd like to give some feedback, may I?" at the end, the interviewer should just ask the damn question in real time. "that description is very high level. that is great for an external summary, when the decision is already made and you want to communicate, not discuss. so i appreciate that. can you go into more detail and justify your choices, as if for an audience of peers and for discussion?"
a good interview should be an interactive exercise, not a one way explanation from the candidate. even LC/DSA type rounds should always find the candidate asking for clarifications, asking if they are on the right track is this what you are looking for, should i be attacking this a different way, etc.
and i would never give unsolicited positive feedback. even when you are the final decision maker, other rounds may uncover weak spots and there may not be a consensus to hire. by giving the positive feedback you confuse the candidate and make a no-hire result even worse. leave it to the recuiter/HR to do that.
as an interviewer i always mention whether i will recommend them for hire (if it's a yes) and that's it. iff asked i provide critical feedback. as a candidate i always ask for critical feedback, which gives me the chance to sharpen any answer when the interviewer doesn't do a good job on asking for what they really wanted.
VPN providers at the tier of Mullvad should be precise about this stuff -- I think it's more than just a nitpick, considering the audience. oh god did I just use an emdash.
Note that you need some flavor of secure DNS to enforce ECH. The protocol is designed to be downgradable.
They can just claim that the user is free to turn off SIP and "modify" the binary bits, or that kernel extensions amount to modification.
I would expect that Linux users want access to age-verified apps just as much as other users, so such a signal will be available.
Also, you're being overly pedantic on the language used. It transfers liability away from the service, more easily allowing operation in about half of the states. "age verification" is a fine lay description.
That is decidedly not a solution. Neighboring APs necessarily need to be on different channels, to avoid Co-Channel Interference (CCI). An AP doesn't answer just on BSSID but also on a specific channel.
this is easily solved with current technology, if they had an incentive to do so.
besides firing folks that get caught, flock themselves should be brought to court.
Also, for domains that are just "parked", not in current use, obviously the parking page can just have a for-sale banner. This is exceedingly common.
> Enquiries that would have been welcome never arrive, and the ones that do arrive are indistinguishable from spam.
Laughable misrepresentation.
i would prefer a thing that was more self-contained, not dependent on a black box service layer underneath.
much apologies if i just have a poor understanding.
Not one-time cost, but rather TCO.
Proto >> Snap-On IMHO. Both in raw quality and in value.
And while Craftsman may have changed significantly even before Sears' demise, there are still some excellent tool lines within the brand.
- it creates the file if it does not exist, not merely truncate. as a tutorial kind of blog post this incomplete description matters IMO.
- it would work the same without the colon (similar for default variable assignment examples). we generally strive not to have "extra" things, like useless use of cat.
- educationally it's useful to demonstrate that redirection, like parameter expansion, works before the command executes (the null command in this case), but the article doesn't explain that at all!
otherwise i <3 this article. some uses of colon i had never thought of or seen before. like file truncation, not sure i'd use them but it was cool to see them.
Well come on. GP really means category cable (twisted pair copper) is not happy at 10Gb distribution lengths (so-called horizontal cabling, although in a home it may span multiple floors without IDFs). That's kind of obvious context.
DACs are not category cable; they are twinax, short, and bulky.
pretty bad advice, if taken only as written, without adding more flavor on top.
the major email providers will penalize you if you generate too many undeliverable emails. thus, if you just send a verification email without any pre-validation, it's pretty easy to get into a DoS situation where current/valid users don't get important email sent to them, or that email is significantly delayed, plus incur huge operating cost to resolve the problem.
some form of rate limiting is needed, plus IMHO it's better to use a verifier service or your own heuristic or ML model to test for email validity including valid but fake/spammy/disposable addresses.
sorry, but we are way past the point of being able to have nice things, esp. when we're talking about email.
the "lies" part of the content is great. people do assume all those wrong things. however the TLDR is just wrong, and potentially harmful.