![]() ![]() HostiFi takes care of server and controller updates.For video storage, the UCK-G2-PLUS functions as an NVR and comes with a 1 TB HDD included, this is upgradeable up to 5 TB for extra storage. Simple easy UniFi and UISP hosting at solid prices. It saves us time, keeps us more secure and it helps us sell more confidently. Then, if I let customers share the files, I'm going to have to deal with dmca bullshit, and I ain't doin' that for free.We shifted to HostiFi from Cloud Keys at dozens of customer sites this has greatly improved our network managed services. ![]() I'm going to need a lot of customers to just fill my first 74 disk cluster. The biggest problem I see with the market is that most consumers don't need that much storage. In a real "race to the bottom" someone at my scale wouldn't be able to make reasonable margins. Now, especially if you are letting users use this for more than just backups, you have per-account overheads like abuse handling.īut yeah, overall? from where I stand? the "race to the bottom" isn't even keeping up with hard drive prices. Now, this doesn't count over-subscription, and if you sell in 100gb blocks, not all of it is gonna get used. (Of course, this is all seagate gigabytes. Now, multiply by 2.2, as I'm going to have 2x replications and make each replication raid6, (10 disk stripes) so my cost is $4.14/month/tb If I'm charging $0.02 per month per gigabyte, that's $20/month per tb revenue. so total cost is going to be around $1.88 per tb per month. a hard drive is going to use 5-10 watts That's $1-$2/month per 4tb. Hard drives are what, $150 per 4tb drive or so, to purchase? Figure that it's another $2000 for every 36 drives for a low-end motherboard and chassis figure a 36 month life, to be conservative, and that's $5.50/month in capital. ![]() 2 replications is about the minimum I'm comfortable with, so the $0.02 per gigabyte/month seems pretty reasonable to me, especially because the big players have access to some pretty dramatic economies of scale that I do not. which is not large) would be around a penny per gigabyte per replication per month. >You've got to love competition, but I wonder at what point Onedrive's race to the bottom in terms of pricing starts to impact Dropbox's valuation?Įh, I've looked into getting into this market, and the price I would feel comfortable with (at my scale. ![]() What about bug finding features like bisect? Or just having a log of when thing happened? Plus what about when you start working with other developers, you cannot all work in Dropbox, you'll get merge conflicts every day. The point is that the state a a whole makes sense. Git (or any DVCS) is good enough that you can commit and push every 5mins if you wanted. Dropbox is good, its gotten better but its still not the right tool for the job. Software development is not one file being edited, its a collection of files in a particular state that give it meaning. If Dropbox went down mid upload or you hibernated your computer before it had completely uploaded (it happens), you then work on another computer and that uploads some files, suddenly you are going to get a merge conflict which Dropbox cannot easily help you with. This complicates the state of a development folder. You are working across many files with many various temporary files. None of us liked that policy to begin with, and then some high-profile false positives helped force the policy to be revised.ĭropbox does those things, however when you are programming you are generally not working in a single file. The scanning policy used to be more aggressive and didn't exclude content that was unshared or only shared to a small set of people. (There's a user-visible message on the web UI.) It's not deleted, and it continues to be fully accessible to the owner across all machines. In those cases, the folder is marked as porn and simply can't be shared again. (A parent's "baby in bathtub" type of photos are not the target here.) In most cases, it's adult pornography or family photos. Clear cases of shared child exploitation porn are reported. It's some highly controlled clean-room environment where a dedicated team tries to determine whether the content is a legal risk or not. If the broad sharing criteria is met and automated flesh tone detection triggers a positive result, that is the only case in which an item is anonymously sent to manual review. The goal is to make flesh tone detection only run during broad sharing.ģ. (This is a change in policy it used to run on upload.) There are heuristics that try to measure whether it's personal sharing or broad sharing, and we're continually improving those. Automated flesh tone detection only runs when a photo is shared. It's only used to identify known child pornography that has already been reported, to make sure it can't be re-uploaded.Ģ. There are 3 processes: PhotoDNA hashing, automated flesh tone detection, and manual review.ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |