davenaff

Guns are now the leading cause of death for people under the age of 24 in the US (and have been for several years). Yes, they exceed motor vehicle deaths.

https://www.economist.com/graphic-detail/2022/05/25/guns-are...

I do think Filecoin is closer to cloud storage than 'free hard drive space'. The hardware requirements for miners (storage providers) are pretty significant and pretty much guarantee that miners are running dedicated hardware. While I'm sure some storage providers operate out of data centers, I don't think a server needs to be located in a data center to be called cloud storage.

This. The comparisons to S3 are specious. Filecoin is doing some interesting things such as their proof of storage and collateralized contracts, but there are significant differences between S3 and Filecoin: - Filecoin is 'cold storage' similar to AWS Glacier. Retrieval times can be really long and certainly aren't web time. - Redundancy is left up to the user (or the user's client). Sure, you can store your files with multiple providers, but good luck determining the reliability of your hand-rolled storage logic. - Retrieval prices are known up front with S3 and other cloud providers. Given that retrieval prices aren't part of storage contracts, costs of retrieval can vary widely (and change). A user's only defense against usurious retrieval pricing is to store with multiple providers. - Bandwidth available to users is largely unknown and likely pretty variable - Miners serve a 'dumb box interface' that will serve anyone any data that they are holding.

In the end, users are still writing contracts with individual storage providers, each of which has their own degree of experience, expertise and proven service history.

Obviously, the Filecoin community is working on improving many of these, but costs will certainly change as Filecoin evolves closer in functionality to s3 and other cloud providers.

BrandVerity |Seattle, WA| Full-time Onsite Python Developers

At BrandVerity we think big and we don't cut corners. The internet is full of bad guys trying to trick unsuspecting users and make a quick buck. Our mission is simple: Clean up the internet. We're a small company and the only way we can deliver on this mission is if everyone we hire is talented, passionate, and committed to doing things the right way.

We do a lot of web crawling to trace the flow of web traffic, or identify places where their brand is being used incorrectly or inappropriately in specific offers, free form text, or even images. Directing a crawl against big chunks of the web and filtering the results to find the needle in the internet haystack has many challenges, and certainly puts our core work in the "Big Data" realm.

We're looking for an experienced engineer who is a strong individual contributor but also wants to share their experience with some extremely capable but more junior team members. We’re very collaborative, and our engineers are some of the best communicating people around, because we appreciate that even if you can solve a problem well, being able to communicate about it is just as important. The strong developer we’re seeking will have the foundations to easily adapt to a new stack, so we’re not looking for specific skill buzzwords. Experience with Python, AWS, and non-relational data storage would help you ramp up faster, but we’re willing to invest the time if you come with the right stuff but not the same stack.

If this sounds worth having a conversation about, please drop us a line at jobs@brandverity.com

BrandVerity |Seattle, WA| Full-time Onsite Python Developers

At BrandVerity we think big and we don't cut corners. The internet is full of bad guys trying to trick unsuspecting users and make a quick buck. Our mission is simple: Clean up the internet. We're a small company and the only way we can deliver on this mission is if everyone we hire is talented, passionate, and committed to doing things the right way.

We do a lot of web crawling to trace the flow of web traffic, or identify places where their brand is being used incorrectly or inappropriately in specific offers, free form text, or even images. Directing a crawl against big chunks of the web and filtering the results to find the needle in the internet haystack has many challenges, and certainly puts our core work in the "Big Data" realm.

We're looking for an experienced engineer who is a strong individual contributor but also wants to share their experience with some extremely capable but more junior team members. We’re very collaborative, and our engineers are some of the best communicating people around, because we appreciate that even if you can solve a problem well, being able to communicate about it is just as important. The strong developer we’re seeking will have the foundations to easily adapt to a new stack, so we’re not looking for specific skill buzzwords. Experience with Python, AWS, and non-relational data storage would help you ramp up faster, but we’re willing to invest the time if you come with the right stuff but not the same stack.

If this sounds worth having a conversation about, please drop us a line at jobs@brandverity.com

And anything in the trash gets automatically deleted in 30 days.

In gmail you can setup a filter that automatically deletes messages. Not quite /dev/null but pretty close.

Interesting analysis for sure, but I think the only solid takeaway here is that (unsurprisingly) Google's private backbone between regions offers a huge performance advantage over the public Internet between EC3 regions.

As the analysis stands, the individual IO stats aren't meaningful. EC2 instances offer a range of I/O throughput in different instances: a t1.micro has 'low' I/O, an m1.small has 'moderate' and an hi1.4xlarge offers 1.1 GB/s write and 2.0 GB/s write. Cost has to figure into a benchmarked analysis here.

And CPU. One of Google's big claims at launch was that CPU time was notably less expensive than on EC2. I'd love to see some data here and clicked the link expecting to find that analysis.

If I recall correctly, as an independent company Feedburner charged a modest fee for CNAME feeds.

Once Google acquired Feedburner, Google made the feature free.

I'm pretty sure the consumer got a nice win here.

A great outcome for a truly hilarious collection of tweets. I've always wondered whether the 'dad' was real, but I ultimately decided it didn't matter - the tweets are simply hilarious.