2,185 karma · joined September 27, 2010
Users install these (free) extensions on a whim, installation takes 2 clicks and seconds. They make a point-in-time decision: "I find this useful today, and I trust the extension is not malware today"
But what they are really saying is: "I trust the (changeable) owner of this extension with whatever data this extension has access to forever and ever" (Nobody uninstalls these extensions, and now Chrome will even sync your extensions when you buy a new device.)
It's the imbalance of that decision that is the problem, no amount of filtering and UI changes and API updates will fix that imbalance.
And their slogan "Our mission is to increase the GDP of the internet" https://stripe.com/about also alludes to the strategy of helping actually create more online businesses, as opposed to just getting all online businesses to use Stripe.
They're just saying:
- Normally, one in 5.5 million UK residents tests positive for ADEM each year
- Since COVID-19, those odds are looking more like one in 1.4 million
Does it actually prevent the large media elements from downloading? how?
Who is happy about H1B Visa suspension? Who was advocating for it?
I think they also use Bing to serve (and earn a commission on) Bing ADS too, but I don't see that documented in the Search API so it may be separate.
DigitalOcean gives 3TB bandwidth on a $15 2CPU/2GBMEM/60GBSSD instance. If you ran 1350 of them it'd cost you ~$20k/month and get you your 4PB egress within bandwidth allowance.
- Take a paywall'ed URL: https://www.nytimes.com/2013/05/05/magazine/y-combinator-sil...
- Add a dot after the domain: https://www.nytimes.com./2013/05/05/magazine/y-combinator-si...
voila, no paywall. Would love to hear an inside story about why this bug appeared.
As a security team employee, I think it's easy to react defensively to every vulnerability report, to take them as critiques of the quality of your work. So it's natural for the first reaction to be jumping to "this is not a real report" or "this is a dupe".
But people in this position should think about the upside/downside of their actions.
ACCEPT - Upside: You show that your security team is responsive, you build trust with an active security community member. Downside: Your company pays out some fee (so tiny in big picture)
DENY - Upside: Your company doesn't pay out a fee. Downside: Usually a net negative for your company's reputation in security community, some chance you cause PR issues for your company.
Just to be clear: Cloudflare is only changing the _provider_ of CAPTCHA's. They are not changing the _criteria_ for showing CAPTCHA's.
So users who have robust cookie blocking in place will continue to be penalized.
I wouldn't put much weight in the specific wording of job descriptions, they're often an amalgamation of previous similar roles at the company and other companies.
>There is some crazy cognitive dissonance out there.
I agree, the hiring decision process within a company seems so susceptible to one simple narrative like "are they a specialist?" taking way too much importance. I think it has something to do with the fact that most of the decision makers are spending most of their time on other things, don't have time to think deeply about who to hire.
When combined with a handwritten font like humour sans[0] You can instantly turn a chart into something that looks more like an XKCD drawing.
No idea why, but I find the hand-drawn look is universally more engaging for charts and diagrams, causing people to actually pay attention and ask questions. It looks like some of the example links[1] need updating. But the WiredJS[2] site is a good demo of the look I am describing.
[0] https://github.com/shreyankg/xkcd-desktop/blob/master/Humor-...
1. It's cool to take photos and apply filters (Instagram 1.0)
1a. It's not cool to take photos and apply filters (Cameras get better, filters are over-used)
2. It's cool to take videos and use AR filters (Snapchat/Instagram evolved)
2a. It's not cool to take videos and use AR filters (filters are over-used)
3. It's cool to decorate real world to look like a filter, take unfiltered photos (2d cafes)
Considering the alternatives, that sounds really appealing for me. I'd also buy it for my less tech-literate parents.
As a note: you'll have to add a valid payment method on DigitalOcean to activate your account, but once you're in it's free to use all the DNS features, and you can automate via the API, docs here: https://developers.digitalocean.com/documentation/v2/#domain...
Aren't these SaaS tools like Stripe (payments) and Checkr (background checks) already built in a way that allows you to never have sensitive PII like payment info or SSN touch your servers?
Although the change has the awkward effect of splitting ddg reporting into the two groups based on date of traffic.
Just out of technical curiosity, does your dataset contain PII or just UUIDs and location data?
If no PII, how to buyers of the data join it to their own datasets?
They're adding a header to identify Brave browser to sites they have partnerships with, like MarketWatch.com and Cheddar.com.
For example, if you add the header: `X-Brave-Partner: cheddar` to your headers in Chrome, and navigate to cheddar.com you get 3 free months of their paywalled content. (Who pays for a subscription to Cheddar.com?!)
If you think about it, you can start to see why they HAD to add a new Header and not just use a custom Brave UserAgent string.
They currently use Chrome's UA string, if they used a uniquely identifiable string, publishers who weren't on-board with Brave's ad network could start nagging users/trying to get around Brave's ad-switching technology.
cloudcraft.co is another tool that takes a more literal approach to AWS architecture diagrams, someone built an add-on that purportedly allows you to export your diagram as Terraform configurations https://medium.com/devopslinks/modules-tf-convert-visual-aws...