Every phone should be able to run personal websites
1–10 of 432 posts
Re: Every phone should be able to run personal websites
#2Limited data plans and connectivity issues make this infeasible. Also security issues on having incoming ports open, of course.
But what if instead of hosting an index.html file over HTTP(S) we could all host via BitTorrent?
A website could be a bunch of files that are referred to by a DHT hash file.
That way everybody who visits the website will also temporarily support the site by hosting it. If your self hosted site is Slashdotted/HNewsed than hosting would still not fail: after all, all the new visitors are temporarily also seeders of the file over BitTorrent.
Re: Every phone should be able to run personal websites
#3Limited data plans and connectivity issues make this infeasible. Also security issues on having incoming ports open, of course. But what if instead of hosting an index.html file over HTTP(S) we could all host via BitTorrent? A website could be a bunch of files that are referred to by a DHT hash file. That way everybody who visits the website will also temporarily support the site by hosting it. If your self hosted si…
there were some projects that explored this actually one which was called chord.
https://en.wikipedia.org/wiki/Chord_%28peer-to-peer%29?wprov...
Re: Every phone should be able to run personal websites
#4Limited data plans and connectivity issues make this infeasible. Also security issues on having incoming ports open, of course. But what if instead of hosting an index.html file over HTTP(S) we could all host via BitTorrent? A website could be a bunch of files that are referred to by a DHT hash file. That way everybody who visits the website will also temporarily support the site by hosting it. If your self hosted si…
You more or less described IPFS. Of course, IPFS grinds my gears because despite oodles of money and time, they still don't have a cohesive ecosystem SDK, haven't rebased on a Rust base, just squandering attention in the space, imo.
Re: Every phone should be able to run personal websites
#5Please no. Phones go into tunnels, run out of battery, and go indoors where there's a poor signal or none at all. They make terribly unreliable servers. Not to mention how much faster this would chew up battery life.
If you want to keep a spare phone plugged in all the time in your closet, connected to Wifi/Ethernet, and hack it to be a webserver, then go ahead. But webservers on mobile devices, being used in a mobile way, are a terrible idea.
Re: Every phone should be able to run personal websites
#6I agree that they should be capable, but I don't think it should be done by almost anyone.
Re: Every phone should be able to run personal websites
#7Any phone can run an onion service if all you need is a website. It's rather annoying that you need to root/jailbreak your phone to use port 80 I agree with that, but it's also not a necessity for running a website.
Aside from the phone use case, the concept of "privileged ports" is pretty silly on any device operated by a single user or used for a single purpose. In an age where any device on a modern network can reserve hundreds of IP addresses without any risk of address space exhaustion, concepts such as reserved ports are next to useless.
One day I'll get myself to waste a few weeks writing an Android mod that gives every app on the system a separate (ephemeral) IPv6 address. The challenge will be to generate enough virtual interfaces for network namespacing to do its thing while assuring it only does so on IPv6 enabled WiFi networks, but I think it can be done.
Re: Every phone should be able to run personal websites
#8On my Nokia N90i, I used to run Apache and PHP and a gallery web app to serve up the phone's camera roll on the wifi interface. Was quite useful at times.
Symbian was a terribly quirky platform to develop for, but there were some quite cool things.
Re: Every phone should be able to run personal websites
#9Limited data plans and connectivity issues make this infeasible. Also security issues on having incoming ports open, of course. But what if instead of hosting an index.html file over HTTP(S) we could all host via BitTorrent? A website could be a bunch of files that are referred to by a DHT hash file. That way everybody who visits the website will also temporarily support the site by hosting it. If your self hosted si…
You more or less described IPFS. Of course, IPFS grinds my gears because despite oodles of money and time, they still don't have a cohesive ecosystem SDK, haven't rebased on a Rust base, just squandering attention in the space, imo.
What does Rust have to do with it?!?
Re: Every phone should be able to run personal websites
#10The article doesn't make sense. It can technically work with a bunch of dynamic DNS systems. An IPv6 address isn't fixed to your device like a MAC address is.
Even assuming it would be doable, it would be a security nightmare, and we'd end up relying on some centralised systems anyway lest we burden the internet with absolutely insane amounts of continual p2p discoveries.
If you want a personal website, why not use a service like neocities? It's free, and just lets you go ham with static content. Don't feel like writing HTML pages manually? Make a TiddlyWiki and upload that.