6 ms·
It is way more relevant than you think. At some point, someone is paying for these devices (running where? Home networks? Cheap VPS? Turn-key application hostin
by rglullis 12y ago
It is way more relevant than you think. At some point, someone is paying for these devices (running where? Home networks? Cheap VPS? Turn-key application hosting like webfaction?) and most importantly, someone is paying for the storage of photos and videos.
It is pretty much like wordpress. And while I can see some of the more tech-savvy running this out of their home server, most people would want to have this in an actual datacenter, and they would need something on the order of hundreds of GB of storage. Unless you piggyback on other services (flickr for photo storage, youtube/vimeo for video), I don't see this costing less than $10/month. Even removing the cost of storage, $5/month seems like the lower bound.
So, how do you finance the operational costs? If you tell me there are people willing to pay $12-15/month to get out of facebook, I'd say there is a business. Otherwise the numbers will never match and this idea of a private cloud will always be some hackers's wet dream.
- dredmorbius 12y agoYes and no. Device cost is trending to zero. People already _have_ the devices, often many of them, and frequently simply gathering dust. We're stuffing computers into phones, refrigerators, toasters, security cameras, set-top boxes, and fnord knows what else. A gumstick is sufficient to serve personal content. The costs come elsewhere. You need a stable Net connection (pretty easy to come by). Distributed data means that any single system loss is pretty much a non-event. Abuse and bad behavior are far bigger issues, all the usual suspects: child pr0n, adult pr0n, copyright violations, threats and bullying. Policing those on a fully-distributed infrastructure would be a nightmare (maybe we'll just give up that fight). Identity and credential recovery are actually pretty big issues. I could see a market where these are actually turned to a benefit, through localized service provision. A local business or enterprise with an interest in knowing who you are and/or establishing your identity might take on the task of maintaining base nodes. It would depend on costs and benefits. Retail, banking, insurance, healthcare, comms provider or other local institutions. Possibly education or government (there are those of us whose first Internet experience came by way of college or university, though we're starting to die out). And as I've observed elsewhere, "Who are you" is becoming the most expensive question online. Craigslist comes to mind. A very small segment of activity funds a great deal else on the site, including a pretty extensive forums section (though that's got various issues). The biggest cost is almost certainly direct customer interaction. Convert this to a model where that's already happening or can be converted to a benefit, and you may well have a win. That $12-$15/mo isn't what you need someone to _pay_ you directly for the service, but what you need to be able to recover from them, net. Or, possibly, much less. I suspect your $5/mo floor is illusory.
- rglullis 12y agoSorry, what? I think we are talking about very different concepts, Looks like you are talking about a "distributed data system", where the OP (and me) were heading to the idea of a "personal website with social functions". For me at least, I am thinking of a system that would be some kind of "personal cloud + feed syndication + acls based on friendships". I want the opposite of a business paying to know who you are. Diaspora got the initial momentum precisely because it was pushing for a privacy-aware version of Facebook. The way I read OP, the one thing that Diaspora got wrong was by putting the "social network" as the focus of their development, while it should've been the person. I am not even going to argue about your idea, because it seems completely far off from what OP mentioned. Yeah, of course we could a have a system that could provide Facebook features in a distributed manner, and still have business paying for it. Turns out that "have someone paying for it" violates the requirement zero (user owned, personal cloud) of the product! Lastly, I am sorry, but there is no way I can get my fridge to run a web server, connect to the home router and store gigabytes of data, _all the while keeping your personal network secure*. Saying that the cost of devices is trending to zero is just as magic-thinking of those in the 2000s who were selling that companies could save by switching immediately just by dumping their office licenses and switching to free software. This is flat out wrong[1] [1]: http://www.joelonsoftware.com/articles/StrategyLetterV.html http://www.joelonsoftware.com/articles/StrategyLetterV.html
- dredmorbius 12y agoLooks like you are talking about a "distributed data system", where the OP (and me) were heading to the idea of a "personal website with social functions". Those are very nearly the same thing. Most websites and online services (and I've engineered several of them) are basically: 1. An application engine, which is a fancy term for "database wrapper script". Much of this can be dispensed with if you build a largely static site, though access control and some scripted / scheduled events are likely still necessary. This talks to ... 2. A data tier. Often multiple levels of caching and / or distributed data and or map reduce and / or nosql and / or database. Again, largely dispensible in a static site. 3. A lot of front-end caching and load balancing. The less content you actually have to serve, the better. It's better to think of a personal cloud + feed syndication (pretty much my formulation as well, BTW) as a cache-tier seed. That is, whatever kit you're running pumps data out to a distributed caching framework (think DNS or bittorrent). If a request cannot be met from cache, or it's expired, then your origin gets a request. But if it can be, you're serving content without actually taking the hit. And if the caching is demand-responsive, then you actually have the situation where you get better at serving data the more requests there are. A DDoS would simply result in more caching peers feeding your data. You also get the benefit that should your residential (or colo) link go down your cached data remain accessible online. Law of large numbers says that any given user is going to have relatively little traffic, but when the vast searchlight of the Internet Hive Mind takes an interest in you, you're swamped. So the sensible thing to do is to set up nodes such that the serve both as origin for their own data and as chache peers for other nodes. And I've got some sense of how activity levels distribute across users in social networks: https://ello.co/dredmorbius/post/nAya9WqdemIoVuVWVOYQUQ https://ello.co/dredmorbius/post/nAya9WqdemIoVuVWVOYQUQ It's also possible that there might be a value in providing more robust caching services for others on a wider scale. The remaining question is: what are the enabling technologies to make all of this happen? ∙ Reasonably inexpensive hardware. ∙ Reasonably inexpensive and reliable Internet connections. ∙ Zero-configuration software. ∙ Sufficiently compelling value proposition. ∙ As for your fridge running a Web server, you'd be amazed at what does. I've found all sorts of nutty stuff scanning networks, and a webserver is a trivially simple piece of software (there are kernel-space webservers and have been for over a decade). The truth is that hardware costs are falling massively. The $35 Raspberry Pi has served 1,000 Web requests per second. A terrabyte MicroSD card will fit on your thumbnail. Power draw is around 5W. https://www.jeremymorgan.com/blog/programming/raspberry-pi-web-server-comparison/ https://www.jeremymorgan.com/blog/programming/raspberry-pi-w... https://plus.google.com/+GuidoStepken/posts/9LGGyKASb8q https://plus.google.com/+GuidoStepken/posts/9LGGyKASb8q What you permit past your network firewall is your call, but my point is that we already are polluted with server-capable computers. The question is how to harness them. As to the "providing this as a service" aspect: not everyone will, can, or wants to run their own server, no matter how zero-maintenance they are. So, if your neighborhood school, or church, or community organization, or retail center, or local ISP, or other entity, wants to take care of doing this, and can handle user request by literally having them show up at the door, well, then all the better. It's not that you have to use a service such as this. But if that works for you, so much the better and power to you. My point as that this is an option, and that there might be ways to tie this to other reasonable but revenue-positive activities.