391 karma · joined August 31, 2009
My "friend" used to use megaupload, filesonic, and other services to watch all his tv content every night, and even paying for a megaupload account (never putting any money back to the creators of content). It was really convenient and the price was right. Now without it, even in the last few days, the pain point has shifted enough that he started buying the seasons of shows he is interested in on itunes. (giving a cut to the creators)
There was a point even a year ago that he could get the latest film on piratebay so easily that there was no point going to the theatre. Now it seems a little harder to find the releases, or at least more inconvenient, so my friend has gone to the movies a lot more.
Now I personally get the whole internet freedom side of things, but at the same time I have seen my friend screw the content creators out of their cut because some middle man made it a lot more convenient to get the content.
I get the idea that some people have used these services for personal content, but if the business model of a service is _primarily_ around the sharing of copyrighted content then something should be done. And especially if the service pays the uploader based on how popular the stolen content they upload is.
At least in my friends case, he spent $100 on itunes in the last day, _only_ because megaupload was not there, and there was enough pain to look for another source.
If there are millions of people out there like my friend, that is a lot more revenue for the creators/studios.
And no, I'm not a troll from the film industry. This is just a real observation.
This allows us to keep everything on google and we do not need move our MX somewhere else. Also we keep our "upload" email on the same domain.
Pretty simple solution with no additional costs.
It's all starting to take me back to my youth watching Robotech and remembering the Zentradi, an advanced race with awesome technology and tools that were developed for them generations ago, but none of the understood how any of it worked or how to fix it, they could only use it. If it broke, they just start over with a new copy instead of debugging it. I hope that the our new generation wont end up like that.
I recently interviewed a recent CS grad that had no idea of the correlation of array of characters and pointers to those characters. You know that it's all just addresses to memory, right?
Anyway, of course there are those who truly dissect and get all the languages and their benefits but are few and between.
Give me a dev that "gets it" in one language any day, instead of someone who thinks remembering the function call or some syntax in 10 languages is of value.
If I hire someone here is how I rank them... 1. 5 years experience in C 2. 5 years experience in PHP 3. 5 years experience in Rails 4. 5 years experience in Rails, Python, erlang, java, php, c, other languages dujour.
Ok, there are people that are just picking up PHP and don't know squat, but at least they know they are beginners and are teachable.
Go without any plans, any future, just go and see what happens. You'll be free. It may be dangerous, you might not make it, but if your other choice was death the day before, then everything now is just gravy anyways. Don't worry about it.
This may sound silly and simple and extreme, but if you _are_ at that stage then this should be your stop gap. From now on when you're in that dark spot just think about when you're going to pull the trigger on this, not on yourself.
Of course there are lots of things you can do before it comes to this, but if you're past that, just leave your current life totally.
The cto at the time convinced them that there is really no point of keeping things inhouse since the majority of the management, for convenience, forwarded all their company email to their personal gmail account anyways. Funny how security is not about what you think but what you do.
The costs are dirt cheap these days. You can get a full rack, power and a gigabit feed for about $800 in many colos in texas. We opted for equinix in san jose, which is all fancy with work areas, meeting rooms, etc when you are there, but the funny part is, we're never there!
I do like the virtualization for some maintenance/flexibility so we have a few servers that are hosts and we run our own private cloud where we get to decide where/what runs. Database servers on bare metal with ssd drives in other cases. Best of both worlds.
It's so cheap you get a second colo in a different part of the country to house a second copy of your backups, and some redundant systems just in case something really bad happens.
Oh yeah and don't get me started on storage. We store about 100TB of data. How much is that on S3 per month? $12,000/month! A fancy enterprise storage system pays for itself every couple of month of s3 fees.
To fix you need segregation. A ultra code/tech area, a business/start up area, and a fanboy/fluff area. You basically want to give high signal to noise ratio for the different groups of people. For example for me, I would just visit the code/tech area and not have to deal with all the noise of the other sections.
if ($network=='at&t') { $initcwd=1; } else { $initcwd=10; }
I think a reasonable increase in initcwd for mobile makes sense. I imagine most mobile pages are smaller too. The way I look at it, I want to increase initcwd to fit the page size in it.
1. net.ipv4.tcp_slow_start_after_idle By default this is set to 1, which means, in a longer keep-alive connection, your connection will revert back to slow start (whatever you ended up setting it as per article) after "idle" (idle is 2 seconds last time i checked). Of course in a keep-alive connection you may have opened up your window from slow start to max, and you probably dont want it do default back to initcwd on subsequent requests. Especially applies on static file/cdn type servers where you probably are running longer keep-alives. You can just set this in sysctl.
2. the last time i checked (years ago) if you run conntrack and turn off tcp_no_metrics_save, you get the benefit of the window opening up to the last remembered window size from your previous connection.
The concepts on increasing initcwd are particularly advantageous in the mobile arena where the rtt is usually much higher.
Perhaps there is some business reason you have for this but it seems like a lot of wasted cycles.
That is a very small amount of traffic to experience issues with. If you want to inform about how much load was put on your systems, you should show pageviews and also show/look at stats on the static content (if you are using one server to serve it all).
middle number: for the graphical choices as it's common/easier to get a valid first click in the middle of the slider.
high number: for the key entry as if most people are right handed it's easier to get to the high numbers instead of going across the keyboard.
all that is predicated on the fact that people are lazy instead of random when using this.
Example of message: http://www.pinkbike.com/photo/6305769/
Imagine if many sites did this to spur the upgrade process. I'm really curious to see the results of this...will traffic plunge by 1.5% or will the usage of ie6 switch to other browsers. Note: no ie9 upgrade choice.
Also this argument of comparing home internet bandwidth overage is only valid if you are serving a site like this from your home :) If you think you're going to get impacted by this overage because of your surfing habits, you'd have to surf...
1GB/150= 6 666 666 pages in the month
since there are 2 592 000 seconds in a month, you're looking at 2.5 page loads per second. You're probably not there.
Also the main page load is 1.5M (including all the resources) so the 150 bytes is even less of a burden.
I think you'd be better off looking at optimizing/saving money somewhere else ;)
There are no real hardware/product reasons for websites to support webm right now.
h264 on the other hand gets the benefit of working with all the iphone and more recently apple tv. Promised new update this year will even allow HTML5 video to be streamed to apple TV directly from the browser of iphones, ipads, and i imagine safari. This is one of these technologies that will really increase the use of h264.
I run the larges cycling site and we handle 100s of niche video uploads per day so I follow this closely, and as much as I'd like to jump on webm, I'm going to definitely hold of. Currently we convert videos to 3 formats to try handle all cases, and having to now multiply that by 2 with another codec is a lot of extra resources.
2.5 mbit h264 web HD/appletv h264 1 mbit h264 for web SD/iphone 300 kbit mobile
- webm makes no sense in the short term. - you need apple support to make webm happen faster
Think about all the extra resources, time, effort that you are asking from companies in the world to support the 2 formats. If you want to be efficient with society, keep the support of h264 while webm development happens, transition once all the big players support the new format. Alternatively take all the money/time/efforts and get apple to transition. If apple does not jump on the wagon, it's going to be years and years of wasted resources in society.
One thing that may not be obvious about minimization is that it does not yield much size reduction when coupled with gzip. You may see 30% decrease in size with minimization on the plain file, but when you gzip both the plain and minimized you may only see a difference for a couple of hundred bytes. If you are worried about speed, you should be using gzip for static content.