If you would like an operating system that doesn't arbitrarily and irrevocably yank support for applications, I suggest Debian or another GNU/Linux OS.

This becomes more relevant every day: http://magnatecha.com/moving-from-ubuntu-to-debian/

What about ISPs that block port 80? Does arkOS handle that? I don't see how it could.

https://github.com/cznweb/deluge - Server for DynDNS/request tunnelling to arkOS nodes https://arkos.io/deluge

^ is in the works

I've made ngrok completely open source and permissively licensed, I'd suggest using it rather than reinventing your own. Feel free to contact me about it.

Thanks -- we are checking it out and definitely considering working it into our implementation

I've got a 'Pi next to me now - which has open reverse ssh tunnels routing ports 25 and 465 from a DigitalOcean $5/month VPS to itself. (I'm working on getting Vagrant and Ansible set up so it can provison and configure inexpensive vpses and update dns MX records to suit on the fly…). The 'Pi lives behind my home NAT gateway - I can get to it's local network only port 443/ssl webmail if I vpn into my home network.

> inexpensive vpses

http://lowendtalk.com/ is my reference.

I'm experimenting with DigitalOcean, Hetzner, and NineFold (it's more about spreading out jurisdictions than absolutely minimising costs).

I see this as a persistent issue that seems to surface every few months. I think Google's fiber network permits running servers for 'non-commercial' use which is whole other can of worms entirely. Does anyone know of any sort of legal movement/petitioning going on currently to try and get ISPs to allow home servers?

You ask them politely to unblock it. Then if they refuse you ask impolitely. I wonder what right they have to do it.

Virtually all consumer-level ISPs in the US explicitly disallow running any sort of persistent listen server as part of their TOS (Terms of Service). The "right" they have to do it is that you agreed to the TOS at signup time.

There will be a tool that will help with dynamic DNS and port proxying for certain services (this may be against your ToS though). Or you will be able to use arkOS on a VPS too, if hosting at home is not a match for you.

Cjdns could handle that.

Examples:

Resource limit for SNAP: http://www.dpw.state.pa.us/foradults/supplementalnutritionas... -- translation: "Have less savings, get SNAP".

Patient Assistance Programs at hospitals: http://abcnews.go.com/blogs/health/2013/03/28/real-money-hid... -- translation: the government says your hospital has to "give back to the community" by not making you pay your bill if you say you can't.

I wonder how much happiness stems from aggregate "good" weather across the locations at whcih people are tweeting. I would wager that it correlates quite nicely.

Then I would, once again, question why the hell people live in gloomy places when most of them enjoy sunshine (and lollipops?)

Although to me the book is much more valuable, making $200k off of it is not bad.

Exactly. I think it's somewhat unhealthy for both the employee and employer (even if they're the same person) for the employee to seek non-work-related interaction on even a weekly basis. I'm talking about the "birthday drinks", ping-pong tables, etc mentioned in the article. It just seems distracting.

If you want to hang out with people then do it, but not when you're trying to get work done.

A combination sounds good: soundproof office for when you really need intense focus, but leave the door open or step out and mingle when you feel like socializing with colleagues.

Aside from the beauty of this restore, I thought it was cool to see the UI influences the NeXT's OS had on Mac OS. I've never seen screenshots until now, but you can definitely see aspects carried through to its successor.

Varnish is pretty awesome, but gets complicated when you have user-specific content. You can use things like edge-side includes and such, but it becomes more than plug and play at that point.

For a lot of sites, either using ESIs or including dynamic content via AJAX is a fairly simple solution that still leaves you with the benefits of caching.

For light page customizability like Hello Username. I will include the username in a browser cookie and use some JavaScript to insert it into the page. This way I can still use Varnish to serve most pages.

to make sure I understand, you meant it becomes more plug and play when you use ESI?

I believe he is saying it becomes less plug and play. By saying "it becomes more than plug and play at that point," he means it becomes more effort than plug and play.

That's my read on it, anyway. It always gets dicey interpreting the intent of others :)

Correct, it "becomes more complicated" is what I meant.

ah yes, that makes sense.

thanks.