148 karma · joined November 30, 2016
Wait until you hear about the US Dollar.
I switched to Postmark years ago and never looked back.
Sacrificing performance for a faster lookup time makes no sense in 2026. This is the one area where I continue to use Google DNS as it just works. Use anything but Cloudflare in this case, please.
Parent pro-tip: Next time the iPad is having Bluey episode playback issues, check to see if you're actually using Cloudflare DNS.
450 million pageviews on a single 16c/32t OVH box with nginx and a 3 Gbps connection = $245
Rally cars also must be street legal because they are driven on public roads between stages.
This comment made me chuckle a little bit because blockchain has been around since at least 2009, which was ~15 years ago.
I'm going to stereotype a bit here, but Tesla YouTubers/Tweeters/Fanatics and the two groups above aside, everyone else is generally "against" EVs. If you own one, you know exactly what I'm talking about. The Cybertruck is Tesla's attempt to change that. Don't convince them on the green-ness or potential cost-savings of home charging, convince them because it's cool. It's something that no other manufacturer can compete against. (for now)
If the customer buys it, they switch to an EV platform, thereby accelerating Tesla's mission of "transition[ing] to sustainable energy".
Leading with "it's an EV" is the primary reason why "legacy auto" has been scaling back their EV manufacturing, because people generally don't care about "EV". They do care about something "cool" though.
Start thinking that way and it will take you to a whole new universe.
TIL you shouldn't run a blog on Cloudflare Workers due to rate limiting.
Chevy Bolt is $25k, before a bunch of credits. After it can get down to $16k or so.
The average commute from home to work is about 15 miles each way, or ~26 minutes.
I think the common misconception here is that chargers are often compared to gas pumps. Do you visit the gas pump every day with your car? Most people don't. Most EV owners charge at home, often during night hours, to take advantage of cheaper TOU electricity rates.
The clear difference here is that with an EV, you can wake up every morning with a "full tank". That eliminates the need to use a public charger unless you 1) forgot to charge 2) are on a road trip or 3) drive a lot. The average commute is ~15 miles the last I checked, so I think #3 will happen, but it won't be very common.
tldr: You can't really leave for your destination in an ICE with a full tank. With an EV, you can.
"Well new EVs cost 40-60k"
You've now been presented with information that shows otherwise.
Why would you toss it up on IPFS? IPFS isn't a decentralized storage network, it's a data routing/transmission protocol with a DHT.
1. We've been building Filebase since 2018 and have been live in production since 2019. We are relatively well known in the Sia and decentralized storage ecosystem. IDC, 451, and GigaOm have all done reports on us.
2. We are targeting web2 and web3 developers. You can safely ignore all of the NFT and Web3 mentions. Most customers today use us as a S3 compatible storage service.
3. Storing data directly on Sia absolutely costs more than $2 per TB. Their website is unfortunately outdated and that same number has been listed for years. Sia is a decentralized storage marketplace - hosts set their own pricing and compete against each other. Filebase goes to this marketplace and acquires storage capacity.
4. The Sia network is one of the leading decentralized storage networks today and has been live since 2015. I can't speak for the entire network since it's decentralized, but for Filebase specifically, we have over 10,000 users and are about to approach 1 billion files processed.
5. A Filebase website re-design is coming soon and will include your suggested ideas of metrics and logos.
Simple example: You have 1TB of data stored in a us-east-1 AWS S3 bucket. Virginia gets hit with a natural disaster, and all of us-east-1 goes offline. You no longer have access to your data. The only "easy button" way you could have prevented this scenario is if you had setup backup or bucket replication policies prior to the event. You decide to follow AWS docs. Disaster recovery 101 typically calls for 3 copies of your data at a minimum. You are now paying $70.66 for storage ($23.55 per TB x 3 regions) and $40.96 for inter-region bandwidth ($20.48 per TB x 2 replicated buckets) for a grand total of $111.62 just to store 1 TB of data. These costs don't even cover you or your customers downloading any of that data either.
At Filebase, we store your data on the Sia network. A 10 of 30 erasure coding profile is used, effectively creating a 3x redundancy overhead. Datacenters and clouds have been using EC for a while too. The critical difference here is that each shard is stored on a different server, spread geographically across the world. An entire portion of the internet can go down, and Filebase can simply fetch the shards it needs from other parts of the world. With a 10 of 30 profile, we only need 10 of those shards to fully reconstruct the file - we can suffer 20 servers or hosts going offline all at the same time.
If Filebase's infrastructure goes down, our health checks fail, and our DNS-level load balancer seamlessly redirects your HTTP requests to another Filebase edge location. And since all Filebase edge locations talk to the same decentralized Sia network, your data is magically available, and you may not even realize you were redirected. That same 1TB of data storage on Filebase will cost you $5.99, a ~95% cost savings.