Officially supporting Linux would consume far more resources than revenue it would generate. It's math. I'm sorry you feel that way, but we are running a business, not a charity.
I personally would love to be able to support Linux. Distrowatch will sell you CD's for over 4000 versions of Linux. Are you kidding me? We provide services to consumers. The goal is to make this something that's approachable for your grandma. If you're a programmer or system administrator, then great. The necessary info is in the.mobileconfig and all the instructions are on various web sites. But if you're not, then what do you suggest we do? Even if we chose one, or a few distributions then we'd have trolls like you pounding down our doors because we support Elbow Linux but not Spring Chicken Linux when they're almost exactly the same, except in the most important way.
I wish it were easy to say. Hulu kind of hates us. Well, really hates us. Part of the reason we change IP addresses every day is to try to make sure all sites are accessible. Hulu blocks us a lot, and their blocking pattern adapts as well. We don't try to actively ensure access to Hulu, but we do hope that IP changing will have that as a side effect.
Everything I said about Android above applies hundredfold for Linux. First of all the VPN requires kernel support. What if yours doesn't include it? Secondly, should we support GNOME? KDE? XFCE? Blackbox? FVWM? WindowMaker? Or maybe command line only? Sysv-init? Sysv-rc? Upstart?
I personally would love to support Linux, but it's just not practical. The possibilities are endless. But you can extract the necessary information from the.mobileconfig and follow some instructions found online to set it up.
No, it isn't. iOS provides us a consistent interface. We use the built in IPSEC/L2TP client and configure it with a.mobileconfig.
At this time, it is not compatible with the iPad 2.
I have no idea why that's in the FAQ. It works perfectly with any iOS device, including iPad 2.
I know what you meant, though - it just takes more work to support the Android platform, and Anonymizer does not feel, at this time, that there is sufficient return of investment to justify supporting the Android platform.
Still, it would be nice if you did.
It does take more work. Each Android device is different and the IPSEC/L2TP client isn't always [included/exposed?]. Manufacturers like to put their own UI on top of Android. And the Kindle Fire? We can't keep up. That being said, it does work, but you have to do it yourself. You can extract the necessary information from the.mobileconfig and if you know how to configure your VPN you're set.
But the only way we could officially support Android would be with an app where we either activate the VPN on our own, or provide our on VPN. That is significantly more work, and we don't have any Android developers. If you want it, buy it for your PC then contact support and ask for Android support. If the demand is there it'll eventually happen.
I'm biased because I'm the senior systems engineer at Anonymizer, but I recommend us.
Anonymizer Universal is an IPSEC/L2TP VPN, support for Windows, Mac OS X and iOS (we don't support Android, but it works. We don't supply instructions because Android is a moving target). Total Net Shield is SSH tunneling+Apache proxy. Supports anything with an SSH client. Take your pick. In either case we don't log traffic.
Traffic egress is from the U.S. and your IP address changes every day.
World IPv6 day is unfortunately DOA due to Cogent being a bunch of jackasses and not allowing certain peering arrangements. There are unfortunately two IPv6 Internets. One of people who use Cogent and one for everyone else.
Google, Yahoo! and Hurricane Electric, as well as many other sites are all on Cogent's "no peer with you" list. If you're a Cogent customer you should get on the phone.
On 6/8 there will be both A and AAAA records for www.google.com. Almost all operating systems (that is, at least every one I've used over the past year) will prefer v6 over v4 if there is a functioning stack. And a functioning stack being defined as a globally unique address on at least one interface and a route to the intended destination, although some operating systems will prefer v4 over v6 if the only global address an automatic tunnel (6to4 or Toredo).
If you only have v4 you will not be affected by v6 day at all. This is only meant to test how many users who have a broken v6 connection.
1. For each teleconference location you need the following
* Mac Mini -> $600 * Logitech USB Webcam -> $100 * Video Projecter -> $1300 * iChat -> $0 Total -> $2000
2. You will also need one XMPP server. Here are cheap and easy options * One of those Mac Mini's runs the server edition and turn on iChat server -> $1000 (instead of $600) * Run OpenFire (Java based) on one of those Mac Mini's -> $0 * Run OpenFire (or any other open source XMPP server) on any other server you already have -> $0
3. Your boss thinks you're awesome for deploying a full teleconference solution that costs less than $100,000 (unless you're deploying to 20 conference rooms, in which case you're awesome for a solution that costs less than $10,000,000).
What kind of games can you build on top of Twitter? You do realize that it's limited 140-character text strings, right? I'm not really sure there's a market for Hunt the Twumpus.
Many open source programs have horrendous documentation. If you can read and write in English (or any other language) and are even remotely capable of reading source code then document it. Parts that you don't understand you can ask the developer to explain it to you. Pick a project you like, e-mail the maintainer and ask if you can contribute documentation.
Most engineers hate doing documentation. It takes up a ton of time that we'd rather spend writing code. If they're smart, they'll love you for it.
My company has conveniently solved this. We're engineers (like Scotty).
IT is the guy that fixes your desktop. We are Software Engineers or Network Engineers.
Take the job and don't say anything about it except maybe in passing. Then always refer to yourself as Engineering. Get your subordinates to call it Engineering. Get other departments to call it Engineering. Put it in your email signature. Answer the phone "Engineering, <name>". Call the people that print business cards and tell them your department should read <something> Engineering.
Once the mindshare is won everything else will follow.
This goes back to the 80's, or possibly even 70's and deals with how computers work on a fundamental level. As you know, copyright means that the rights holder is the only one allowed to authorize copies. When a program runs, it is copied from the storage medium (i.e., disk, but back then it was tape) and into RAM. That's a copy. Copyright law was modified to explicitly permit these types of copies (I believe they are termed "transient copies") for license holders.
Apple's argument goes back to this statute. Apple's license says that you can only run Mac OS X on Apple hardware. Thus, the copy from disk to RAM on non-Apple hardware is an unauthorized copy.
It makes sense, from a letter-of-the-law point of view, and I find it very interesting because by and large nobody thinks about software copying in that sense anymore, but back in the day it was a very hot issue. I'm not saying I endorse this argument, but IIRC, this is how the law is written. Also, IANAL, so if you want to know more about this, go look it up yourself.
What really concerns me is that now we've got Klingons attacking Earth establishments and we have no sign of Romulans. I fear that Enterprise was right all along.
For what it's worth, though, nothing would be different if your software were closed source, except that your user base would probably be smaller and, depending on how necessary your software is, open source competitors would be even more eager to push you out.
Which explains all of those open sourced calendaring solutions that beat the pants off of Exchange. Oops, there aren't any that even come close. Oh well, so much for that idea.
It's not "an internet standard email solution". They use a proprietary and embarrassingly insecure login sequence which can be replayed to gain access to a user's mail at any time.
Slashdot Mirror
Dumbing down of Final Cut Pro
This is how Apple progresses. Rewrite the future generation from scratch with 80% features. Finish over the next few years.
Refusal to sell non-glossy screens
Anti-glare is the only option on the MBA, and MTO on the MBP.
Poor value hardware
You're joking, right?
Officially supporting Linux would consume far more resources than revenue it would generate. It's math. I'm sorry you feel that way, but we are running a business, not a charity.
I personally would love to be able to support Linux. Distrowatch will sell you CD's for over 4000 versions of Linux. Are you kidding me? We provide services to consumers. The goal is to make this something that's approachable for your grandma. If you're a programmer or system administrator, then great. The necessary info is in the .mobileconfig and all the instructions are on various web sites. But if you're not, then what do you suggest we do? Even if we chose one, or a few distributions then we'd have trolls like you pounding down our doors because we support Elbow Linux but not Spring Chicken Linux when they're almost exactly the same, except in the most important way.
Can you confirm hulu access please?
I wish it were easy to say. Hulu kind of hates us. Well, really hates us. Part of the reason we change IP addresses every day is to try to make sure all sites are accessible. Hulu blocks us a lot, and their blocking pattern adapts as well. We don't try to actively ensure access to Hulu, but we do hope that IP changing will have that as a side effect.
Everything I said about Android above applies hundredfold for Linux. First of all the VPN requires kernel support. What if yours doesn't include it? Secondly, should we support GNOME? KDE? XFCE? Blackbox? FVWM? WindowMaker? Or maybe command line only? Sysv-init? Sysv-rc? Upstart?
I personally would love to support Linux, but it's just not practical. The possibilities are endless. But you can extract the necessary information from the .mobileconfig and follow some instructions found online to set it up.
It's available in our business offerings. It's been discussed for consumer. I can't say when or if it will ever happen.
And iOS is not a moving target?
No, it isn't. iOS provides us a consistent interface. We use the built in IPSEC/L2TP client and configure it with a .mobileconfig.
At this time, it is not compatible with the iPad 2.
I have no idea why that's in the FAQ. It works perfectly with any iOS device, including iPad 2.
I know what you meant, though - it just takes more work to support the Android platform, and Anonymizer does not feel, at this time, that there is sufficient return of investment to justify supporting the Android platform.
Still, it would be nice if you did.
It does take more work. Each Android device is different and the IPSEC/L2TP client isn't always [included/exposed?]. Manufacturers like to put their own UI on top of Android. And the Kindle Fire? We can't keep up. That being said, it does work, but you have to do it yourself. You can extract the necessary information from the .mobileconfig and if you know how to configure your VPN you're set.
But the only way we could officially support Android would be with an app where we either activate the VPN on our own, or provide our on VPN. That is significantly more work, and we don't have any Android developers. If you want it, buy it for your PC then contact support and ask for Android support. If the demand is there it'll eventually happen.
I'm biased because I'm the senior systems engineer at Anonymizer, but I recommend us.
Anonymizer Universal is an IPSEC/L2TP VPN, support for Windows, Mac OS X and iOS (we don't support Android, but it works. We don't supply instructions because Android is a moving target).
Total Net Shield is SSH tunneling+Apache proxy. Supports anything with an SSH client.
Take your pick. In either case we don't log traffic.
Traffic egress is from the U.S. and your IP address changes every day.
World IPv6 day is unfortunately DOA due to Cogent being a bunch of jackasses and not allowing certain peering arrangements. There are unfortunately two IPv6 Internets. One of people who use Cogent and one for everyone else.
Google, Yahoo! and Hurricane Electric, as well as many other sites are all on Cogent's "no peer with you" list. If you're a Cogent customer you should get on the phone.
On 6/8 there will be both A and AAAA records for www.google.com. Almost all operating systems (that is, at least every one I've used over the past year) will prefer v6 over v4 if there is a functioning stack. And a functioning stack being defined as a globally unique address on at least one interface and a route to the intended destination, although some operating systems will prefer v4 over v6 if the only global address an automatic tunnel (6to4 or Toredo).
If you only have v4 you will not be affected by v6 day at all. This is only meant to test how many users who have a broken v6 connection.
This is what happens when I click the "Quote Parent" button? Really slashdot?
:::::::: Post?
::.
Don't the 0000 all collapse?</quote>
So do contiguous colons. What you mean is
This is news?
That's what.
That's what the navigational deflector shield is for!
1. For each teleconference location you need the following
* Mac Mini -> $600
* Logitech USB Webcam -> $100
* Video Projecter -> $1300
* iChat -> $0
Total -> $2000
2. You will also need one XMPP server. Here are cheap and easy options
* One of those Mac Mini's runs the server edition and turn on iChat server -> $1000 (instead of $600)
* Run OpenFire (Java based) on one of those Mac Mini's -> $0
* Run OpenFire (or any other open source XMPP server) on any other server you already have -> $0
3. Your boss thinks you're awesome for deploying a full teleconference solution that costs less than $100,000 (unless you're deploying to 20 conference rooms, in which case you're awesome for a solution that costs less than $10,000,000).
What kind of games can you build on top of Twitter? You do realize that it's limited 140-character text strings, right? I'm not really sure there's a market for Hunt the Twumpus.
Many open source programs have horrendous documentation. If you can read and write in English (or any other language) and are even remotely capable of reading source code then document it. Parts that you don't understand you can ask the developer to explain it to you. Pick a project you like, e-mail the maintainer and ask if you can contribute documentation.
Most engineers hate doing documentation. It takes up a ton of time that we'd rather spend writing code. If they're smart, they'll love you for it.
Strong words from somebody who makes a browser that can't pass Acid3.
My company has conveniently solved this. We're engineers (like Scotty).
IT is the guy that fixes your desktop.
We are Software Engineers or Network Engineers.
Take the job and don't say anything about it except maybe in passing. Then always refer to yourself as Engineering. Get your subordinates to call it Engineering. Get other departments to call it Engineering. Put it in your email signature. Answer the phone "Engineering, <name>". Call the people that print business cards and tell them your department should read <something> Engineering.
Once the mindshare is won everything else will follow.
This goes back to the 80's, or possibly even 70's and deals with how computers work on a fundamental level. As you know, copyright means that the rights holder is the only one allowed to authorize copies. When a program runs, it is copied from the storage medium (i.e., disk, but back then it was tape) and into RAM. That's a copy. Copyright law was modified to explicitly permit these types of copies (I believe they are termed "transient copies") for license holders.
Apple's argument goes back to this statute. Apple's license says that you can only run Mac OS X on Apple hardware. Thus, the copy from disk to RAM on non-Apple hardware is an unauthorized copy.
It makes sense, from a letter-of-the-law point of view, and I find it very interesting because by and large nobody thinks about software copying in that sense anymore, but back in the day it was a very hot issue. I'm not saying I endorse this argument, but IIRC, this is how the law is written. Also, IANAL, so if you want to know more about this, go look it up yourself.
Ever hear of HINFO or TXT records?
Whatever.
What really concerns me is that now we've got Klingons attacking Earth establishments and we have no sign of Romulans. I fear that Enterprise was right all along.
I thought the story was going to say they like American Idol.
For what it's worth, though, nothing would be different if your software were closed source, except that your user base would probably be smaller and, depending on how necessary your software is, open source competitors would be even more eager to push you out.
Which explains all of those open sourced calendaring solutions that beat the pants off of Exchange. Oops, there aren't any that even come close. Oh well, so much for that idea.
It's not "an internet standard email solution". They use a proprietary and embarrassingly insecure login sequence which can be replayed to gain access to a user's mail at any time.
It's already been documented:
http://blog.dave.cridland.net/?p=32
And let's all welcome Timothy to last year, because it's been around for a while.