I don't want to be that guy, but.... We should probably appreciate a modern IRCd, but why, why, why wasn't this written in a memory safe language like Rust or Go? Seriously wtf, if you are starting from scratch in 2021 on a remotely accessible application why would you choose C?
I have had a Twilio account for years, and have always used the proprietary MFA implementation from their Authy app. I don’t remember being forced to switch to SMS MFA.
Where could I, or any Internet user, trivially download these details on 533M Facebook users prior to this dump? If nothing else, it seems extremely noteworthy that someone was not only able to obtain the data through scraping or some attack, but has shared with the world.
> The video provides a good overview about the issues surrounding bias in ML, and I think it motivates a discussion that would be useful to have on HN, given the number of people who work on such systems that regularly visit this site.
Have you read any sane discourse on HN in the last few years? The top post on any thread like this will discuss how algorithmic bias is just some SJW conspiracy or concern.
I'm not a lawyer, but can you explain how their privacy policy is privacy-conscious now and going forward, and how centralization of network transit with Cloudflare isn't a bad thing?
Honest question: How do you view it as an improvement? The same data is being shared, and the only difference is that Cloudflare isn't immediately behaving in the same evil ways as Google. But once you concentrate power in an entity, perhaps bad things might happen?
... If there was an on-premise captcha implementation that actually worked, that would be great.
With all due respect to the author here, the arguments presented aren't particularly compelling.
> Apologists for proprietary software like to say, “free software is a nice dream, but we all know that only the proprietary system can produce reliable products. A bunch of hackers just can't do this.”
Absolutely no one says this anymore. In 2014, when the article was written, almost no one would say it.
> Barton P. Miller and his colleagues tested the reliability of Unix utility programs in 1990 and 1995. Each time, GNU's utilities came out considerably ahead.
That's great, but it's 2020 now.
The FSF has done awesome work, but they might be better served presenting modern research and evidence about the reliability of free software.
Is this news? This is a block storage failure on Rackspace. EBS volumes on Amazon fail all the time, as anyone who manages a large number of instances probably knows (0.1%-0.2% per year for normal volumes):
> Amazon EBS offers a higher durability volume (io2), that is designed to provide 99.999% durability with an annual failure rate (AFR) of 0.001%, where failure refers to a complete or partial loss of the volume. For example, if you have 100,000 EBS io2 volumes running for 1 year, you should expect only one io2 volume to experience a failure. This makes io2 ideal for business-critical applications such as SAP HANA, Oracle, Microsoft SQL Server and IBM DB2 that will benefit from higher uptime. io2 volumes are 2000 times more reliable than typical commodity disk drives, which fail with an AFR of around 2%. All other Amazon EBS volumes are designed to provided 99.8%-99.9% durability with an AFR of between 0.1% - 0.2%,
> The Cost Explorer Hourly and Resource level granularity allows you to access hourly granularity for the past 14 days and resource level granularity for EC2 instances. The cost is $0.01 per 1,000 UsageRecords month. UsageRecords are defined as one line of usage. For example, one EC2 instance running for 24 hours will generate 24 distinct usage records at the hourly granularity.
Life is good for Amazon, when they can get their customers to pay extra to see exactly why they're paying so much.
Read the comments in this thread six hours from now and you'll understand.