Cloud computing

[KichigaiNeko]

This is the general consensus of opinion Phish.

[Phish]

This is the general consensus of opinion Phish.

believe me or not i always log out of google and clear all my cookies before i go to the dark side of the internet. Like porn for instance

[KichigaiNeko]

I also Phish.


I resent that my page loading is slowed by http://www.google-analytics.com

[Phish]

I also Phish.


I resent that my page loading is slowed by http://www.google-analytics.com

you can disable this function by installing ghostery. Great app

http://www.ghostery.com/

Enjoy!

[KichigaiNeko]

I hope so. Did the Opt out extension in Google Chrome and it does fuck all especially on this site atheistforums.org

[Angrboda]

There's another side beyond the dark side? Who'd a thought.



It occurs to me that it probably wouldn't be all that difficult to set up a local proxy server with a dynip or static domain, and redirect all externally hosted cloud content through that proxy. That way, if a cloud host goes down for the count, I'll just move the content elsewhere and change the location that the proxy points to for that content. I probably don't have the terminology entirely correct, but I don't see why that wouldn't work. (And I've been meaning to buy a domain for quite a few years. My current ip is dynamic, but regardless. And the device was only $15; buy a second and have a pre-configured spare to assume proxy/hosting duties if one fails.)


I've got 135 pages to read by Monday, and my ILS worker is coming over to help organize on Friday, but rooting that little pogoplus device sounds a lot more fun than any of that.

[Jackalope]

Apo - for your particular use case (persistent links) you really do need to control both your local and global namespace. That is to say, you need your own domain, and you need to be able to control in it's entirety, how the local path is presented. In other words, something that approximates a traditional web server.

While you can certainly self-host, it's not the best solution to the problem - though, it may serve your needs with no incremental cost.

[Angrboda]

Apo - for your particular use case (persistent links) you really do need to control both your local and global namespace. That is to say, you need your own domain, and you need to be able to control in it's entirety, how the local path is presented. In other words, something that approximates a traditional web server.

While you can certainly self-host, it's not the best solution to the problem - though, it may serve your needs with no incremental cost.

I'm not sure what virtues to not self-hosting you see that are important. (Availability would be largely under my control, and likely not significantly worse in practice than a cohost or hosting service. [There's conflicting info on exactly how complete the linux implementations which run on these devices is, but surely more than adequate for the role I'm imagining; that leaves the reliability of myself, my internet connection, and my name servers (I have a friend who has offered free use of high quality name servers, but that's just details).]

I guess I'm wondering if I'm missing some of the specifics of what you are saying by assuming that I know what I'm talking about. What are you referring to, specifically?

(I've been having issues with my internet connection, but I'd have to investigate the source of those.)


And then there's the problem of committing to a specific name, of course. I'd more or less settled on kadesha.org, but I might reconsider things. Any recommendations on registrar? (Just for parking purposes, mainly.)

[Jackalope]

Apo - for your particular use case (persistent links) you really do need to control both your local and global namespace. That is to say, you need your own domain, and you need to be able to control in it's entirety, how the local path is presented. In other words, something that approximates a traditional web server.

While you can certainly self-host, it's not the best solution to the problem - though, it may serve your needs with no incremental cost.

I'm not sure what virtues to not self-hosting you see that are important. (Availability would be largely under my control, and likely not significantly worse in practice than a cohost or hosting service. [There's conflicting info on exactly how complete the linux implementations which run on these devices is, but surely more than adequate for the role I'm imagining; that leaves the reliability of myself, my internet connection, and my name servers (I have a friend who has offered free use of high quality name servers, but that's just details).]

I guess I'm wondering if I'm missing some of the specifics of what you are saying by assuming that I know what I'm talking about. What are you referring to, specifically?

(I've been having issues with my internet connection, but I'd have to investigate the source of those.)

The bolded above is a big one. Having sufficient upload bandwidth is another. Some ISPs block inbound ports, or will, if they catch you running a server. Hosting services will usually keep you patched up-to-date, so security may be better. There may be other considerations, depending on what a particular provider offers.

Personally, I used to self-host email, web, and several other services. It became too much of a pain in the ass to continue to do, so I don't do that anymore. Self-hosting isn't necessarily a BAD option, it's just frequently not the best option.

P.S. If you do go this route, and continuity is important to you if your hosting provider goes bye-bye, keeping domain registration and name service separate from hosting is a good idea.

P.P.S. It's always possible to sublet space from someone who has hosting and doesn't mind sharing it.