626 karma · joined January 10, 2015
At a past job, we used Entrust [0] and I'm aware of Virtru [1] as well.
Edit: I forgot about Sharepoint, which also sort-of fills the ACL document-sharing niche. (though I'm less certain about whether it uses encryption to enforce its access policies)
Honestly, that sounds pretty fantastic. I've been using 3rd party tools/extensions to do this sort of thing in corporate and government environments for years, but having the attestation go all the way down to the hardware level is a big value-add, especially with so much ransomware/spyware/extortion/espionage going on these days.
Can someone please explain to me how the author might see this level of security as a bad thing?
Webserver was a single VM running a Java + Spring webserver in Tomcat, connecting to an overworked Solr cluster to do the actual faceted searching.
Caches kept most page loads for organic traffic within respectable bounds, but the crawler destroyed our cache hit rate when it was scraping our site and at one point did exhaust a concurrent connection limit of some kind because there were so many slow/timing-out requests in progress at the same time.
Asymptomatic spread and a lack of clarity on whether it was even "airborne" plagued our early efforts to contain it.
That being said, the lockdown-related learning loss is also a disaster, and one that will disproportionately impact disadvantaged kids and their communities.
Adjusting for inflation, it's doubled in real value over 25 years, which works out to <3% APR. It's a decent return, but we've also ignored 25 years of property tax and maintenance. (on the other hand, we've also ignored 25 years of effective rent)
I guess the point I'm trying to make is that $1.3M isn't worth what it used to be but it sounds big in our head because we remember a time when a dollar went a lot further than it does today.
0) the scammer somehow acquires Person A's credit card info
1) the scammer sets up an online store on Amazon or similar and sells some popular item at a 20% discount (eg Nespresso pods)
2) the scammer doesn't actually have that item in stock, but when they get an order from Person B, they use the stolen card to place another order with a legitimate seller and set the destination address to Person B's address (basically drop-shipping but where the victim is paying for the cost of the goods being sold)
3) Now the scammer has received already-laundered clean money from an online transaction, and Person B got the product they wanted on-time and at a steep discount. They're happy, and certainly won't be complaining to their credit card company.
4) when Person A reports their card stolen and tries to perform a chargeback, the legitimate seller who acted as an unwitting drop-shipper ends up eating the cost.
As with anything, there are tradeoffs and your requirements can change over time. Maybe the ad networks or malware creators start using new domains every 10 minutes to counter your blocking system so now you have to store more data and disseminate it more frequently.
As engineers, it's our job to weigh the tradeoffs between different solutions given the resources and constraints of the situation. For the situation I've outlined above, I'd at least strongly consider a bloom filter but it's certainly not the only way to do it.
Rather than distributing the entire blocklist to your userbase, you can instead send a bloom filter + an allowlist of the small handful of sites which have a hash collision with one of the blocked sites.
As a bonus, computing the hashes will have great branch prediction characteristics and you'll have fewer cache misses because the bloom filter is tiny and frequently accessed, so your plugin will not add any perceptible slowdown to the user's experience.
I certainly wouldn't trust Comcast to keep malicious ads out of their ad network, either.
[0] https://www.techdirt.com/articles/20140908/07191228453/comca...
>In 2007, the World Cancer Research Fund (WCRF) stated that there is convincing evidence linking the consumption of red and processed meat with the development of colorectal cancer (CRC). The WCRF further stated that the public should limit their intake of red meat to below 500 g per week, and avoid processed meat entirely. A further update from the WCRF emphasized that no safe level of processed meat could confidently be attributed to a lack of risk.
Excerpt from: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6893523/
The thing that makes this a bit trickier is that Zelle is transparently used under the hood by some banks to move money between accounts owned by the same person. I've moved thousands of dollars between two of my accounts with Zelle but the alternative would have been an ACH transfer or depositing a check to myself, not Venmo.
I know it's just one anecdote, but when splitting a check, my social circle always reaches for Venmo, never for Zelle. And yet I've probably moved more total money via Zelle because I occasionally use it for different, higher-value transactions.
There's some selection bias at play for different transaction types (including many where people might not even realize they're using Zelle) so we should be careful looking at only the headline numbers.
Full-disclosure: I work (on completely unrelated stuff) at one of the organizations involved
Also, Oracle v Google opens the possibility of a fair-use defense in the event that Copilot does regurgitate a small snippet of code.
The mechanism by which this is enforced is an "Airworthiness Directive" if you want to read more about it. Source: I used to fly a small 50+ year-old aircraft recreationally
For all we know, their password might be something like "remote_worker"!
Avoiding the temptation to set bigger and more far-reaching precedents than is strictly necessary for the case at hand avoids giving the impression that the judicial branch is doing the job of the legislative branch.
Because the boat is longer than the canal is wide, for any nonzero perpendicular wind speed there is a minimum boat speed below which it would not be able to avoid running aground. The solution is to either not permit such large ships to transit the canal during high wind events or to send them with enough tugboats to counteract the force of the wind.
T-Mobile has a $15/mo prepaid plan without having to pay a year in advance.
I suppose I technically did have "veto power" as my approval was required in order to merge the PR, but nobody ever thought of it in such adversarial terms. We'd comment with questions or things that were unclear, occasionally asking "why are we doing it this way instead of that way?" and more often than not the solution was simply adding/updating comments to make things more clear.
For our team at least, it was a casual and collaborative effort where everyone learned from each other. I wouldn't hesitate to give inexperienced devs veto power over my PRs again unless it was for a time-sensitive hot-fix.
You mentioned that tries have had recent advancements, could you please point me to a paper about these advancements so I can learn more? I did a quick Google search but wasn't able to find anything that seemed relevant.