Even though many of these doodles are there to surreptitiously showcase standards-based alternatives to Adobe Flash, this doodle actually requires Adobe Flash to play the audio.
It's too bad that even with the Kindle reader you will not benefit from Amazon's patented e-ink anti-aliased fonts. These excellent fonts are the reason I own a Kindle. After using a Kindle you won't tolerate an e-ink Nook, Kobo, or other e-reader.
Apply for a software engineering or systems engineering job at Google and see if you can get a phoner with a member of the GMail team. You will sustain an injury as you fall of your chair laughing at how the interviewer describes to you how GMail is "designed," as if it really were "designed."
Google is a superb search engine, but that's about it.
The largest SIM cards today cannot hold even the smallest video. The authors of these articles surely meant an SD card or MicroSD card, but definitely *not* a SIM card.
I knew a guy in college who got a new job when he sent his computer in for repair. They liked his resume. He was a Computer Science major and got an interview followed by a job offer after he picked up the computer.
Banzairun is correct about the character generators--they were way earlier than 1996's SGI O2. I'm talking about 1979.
The other thing that I'm talking about is the WeatherStar decoder that The Weather Channel used that superimposed the local conditions at the bottom of the screen and did the local forecasts (the "Local on the 8s" segments). I'd sure like to learn more about those. They appeared in the early 1980s.
Character generators were big business for cable television operators. Before computers were so ubiquitous the need to show text on the screen was a challenge. They needed one for each channel that was to show text, especially for public access channels and their schedules. Later, special units were designed for use by The Weather Channel that would genlock and overlay the text onto the video.
Today only a few people remember how difficult it once was to get text on a television screen. As a kid I remember watching U/A Columbia's public access channel schedule update. Someone was typing into it and directly changed what you see on the screen as they typed it. I guess they're supposed to do that when the channel is off-air or at 4:00 AM.
Not in this case. While collecting WiFi is akin to iPhone's collecting WiFi to create a higher quality tracking database, in Google's case, GPS should have been enough and Google's collecting of WiFi data has no legitimate use.
To crack a TrueCrypt volume, you do not need to decrypt the data itself, but only the encryption that protects the key. This encryption is also very strong and can be protected further by keying it with external data, like a USB thumb drive, but the whole key is still there in the volume.
I had once asked if TrueCrypt could add a feature that would allow us to completely remove the key from the volume but that was not popular with the developers. I think TrueCrypt would be even more secure if the key was physically separated. That way an adversary would need to decrypt the unknown/unpredictable cleartext inside the volume data itself, not just by attacking the little key data in a well-known format.
They use more than just Xen but they don't really publicize it. With paravirtualization they can use anything they want, but Xen seems to be the most prevalent. Some of my instances say "xen" and others say "paravirtual." Just because the kernel says "xen" or "paravirtual" does not necessarily mean that the hypervisor is Xen or something else.
Also, speaking towards migrating instances between "availability zones," I found out that I cannot use Windows Server EBS boot volumes on anything but the instance I created it with. You can do this with most of the Unix instances, though. I found this little oddity a bit maddenning when I wanted to move a Windows Server instance from a t1.micro to t1.small. No-can-do with boot volumes. Well, not officially, anyway.
The other thing I don't get is why I should be able to use my Amazon.com shopping account to log into AWS. It seems, well, silly, even with the two-factor authentication dongle, that the same account used to buy Kindle books and Fisher-Price toys is paying for my AWS usage.
I don't know what bothers me more: the outage itself or the alternative codes Amazon used for punctuation in that email that made my post look messed up only after I posted it.
Starting at 12:47AM PDT on April 21st, there was a service disruption (for a period of a few hours up to a few days) for Amazon EC2 and Amazon RDS that primarily involved a subset of the Amazon Elastic Block Store (âoeEBSâ) volumes in a single Availability Zone within our US East Region. You can read our detailed summary of the event here: http://aws.amazon.com/message/65648
Weâ(TM)ve identified that you had an attached EBS volume or a running RDS database instance in the affected Availability Zone at the time of the disruption. Regardless of whether your resources and application were impacted, we are going to provide a 10 day credit (for the period 4/18-4/27) equal to 100% of your usage of EBS Volumes, EC2 Instances and RDS database instances that were running in the affected Availability Zone. This credit will be automatically applied to your April bill, and you donâ(TM)t need to do anything to receive it. You can see your service credit by logging into your AWS Account Activity page after you receive your upcoming billing statement.
Last, but certainly not least, we want to apologize. We know how critical the services we provide are to our customersâ(TM) businesses and we will do everything we can to learn from this event and use it to drive improvement across our services.
Sincerely, The Amazon Web Services Team
This message was produced and distributed by Amazon Web Services, LLC, 410 Terry Avenue North, Seattle, Washington 98109-5210
I dare say that HIPAA and SOX, and others, have something to say about that. They do, indeed, address the destruction of data-at-rest. The chain of custody does not end with bankruptcy or change of ownership of a data medium.
Amazon and Microsoft have to distinctly different views of "cloud computing."
When I first learned about "cloud computing" I automatically assumed it meant that there would be an arbitrary number of different services available to an arbitrary number of web servers which would then be served to the user. No one service would depend on the other.
Amazon's "cloud computing" is centralized upon the virtual machine as the hub of the "cloud." Microsoft Azure, on the other hand, originally offered the approach that I had thought about, where everything is just a service, no VM required.
Today Amazon still depends heavily on the VM concept. You can't have a web service on Amazon without one. This also makes it excessively difficult to "load balance" or provide "failover" because you are actually expected to stand up new VM instances to scale up and down and need separate VM instances on each "availability zone." In addition it's not easy or affordable to share data between availability zones. This isn't what I thought the cloud was going to be.
Microsoft eventually added VMs to its Azure service so they could compete with Amazon's VM-centralized concept. I still think the idea of separate, independent services talking to each other was what the "cloud" was supposed to be, and if these services didn't have to depend on these VMs (which they do not have access to because AWS is intermittently down) they would have still been working from the other data centers.
Off-brand MP3 players do this, too. The "manufacturer" puts in a memory module of 1/2 or 1/5 the size it says on the box and they disable "media full" errors which results in the looping effect that the drive in the article had.
Slashdot Mirror
Didn't this hit the regular news over two months ago? What's new this time?
Call me back when Picasa is a native application. I don't now nor will ever use Wine.
The Kindle 3 has the improved fonts. It's very obvious side-by-side.
Even though many of these doodles are there to surreptitiously showcase standards-based alternatives to Adobe Flash, this doodle actually requires Adobe Flash to play the audio.
It's too bad that even with the Kindle reader you will not benefit from Amazon's patented e-ink anti-aliased fonts. These excellent fonts are the reason I own a Kindle. After using a Kindle you won't tolerate an e-ink Nook, Kobo, or other e-reader.
You want fun?
Apply for a software engineering or systems engineering job at Google and see if you can get a phoner with a member of the GMail team. You will sustain an injury as you fall of your chair laughing at how the interviewer describes to you how GMail is "designed," as if it really were "designed."
Google is a superb search engine, but that's about it.
Naturally, but it's most certainly not the SIM card. They don't have the capacity nor the ability to hold multimedia files.
The largest SIM cards today cannot hold even the smallest video. The authors of these articles surely meant an SD card or MicroSD card, but definitely *not* a SIM card.
Supporting CentOS is the same as supporting Red Hat. Why is this significant in any way?
Marshall did the same thing years ago.
I knew a guy in college who got a new job when he sent his computer in for repair. They liked his resume. He was a Computer Science major and got an interview followed by a job offer after he picked up the computer.
Banzairun is correct about the character generators--they were way earlier than 1996's SGI O2. I'm talking about 1979.
The other thing that I'm talking about is the WeatherStar decoder that The Weather Channel used that superimposed the local conditions at the bottom of the screen and did the local forecasts (the "Local on the 8s" segments). I'd sure like to learn more about those. They appeared in the early 1980s.
Character generators were big business for cable television operators. Before computers were so ubiquitous the need to show text on the screen was a challenge. They needed one for each channel that was to show text, especially for public access channels and their schedules. Later, special units were designed for use by The Weather Channel that would genlock and overlay the text onto the video.
Today only a few people remember how difficult it once was to get text on a television screen. As a kid I remember watching U/A Columbia's public access channel schedule update. Someone was typing into it and directly changed what you see on the screen as they typed it. I guess they're supposed to do that when the channel is off-air or at 4:00 AM.
Not in this case. While collecting WiFi is akin to iPhone's collecting WiFi to create a higher quality tracking database, in Google's case, GPS should have been enough and Google's collecting of WiFi data has no legitimate use.
To crack a TrueCrypt volume, you do not need to decrypt the data itself, but only the encryption that protects the key. This encryption is also very strong and can be protected further by keying it with external data, like a USB thumb drive, but the whole key is still there in the volume.
I had once asked if TrueCrypt could add a feature that would allow us to completely remove the key from the volume but that was not popular with the developers. I think TrueCrypt would be even more secure if the key was physically separated. That way an adversary would need to decrypt the unknown/unpredictable cleartext inside the volume data itself, not just by attacking the little key data in a well-known format.
Don't be evil.
Part of the motto is that you should also not give the perception of being evil. A mirror evaluation goes a long way in this respect.
Unfortunately, that's why we call it "bankruptcy."
They use more than just Xen but they don't really publicize it. With paravirtualization they can use anything they want, but Xen seems to be the most prevalent. Some of my instances say "xen" and others say "paravirtual." Just because the kernel says "xen" or "paravirtual" does not necessarily mean that the hypervisor is Xen or something else.
Also, speaking towards migrating instances between "availability zones," I found out that I cannot use Windows Server EBS boot volumes on anything but the instance I created it with. You can do this with most of the Unix instances, though. I found this little oddity a bit maddenning when I wanted to move a Windows Server instance from a t1.micro to t1.small.
No-can-do with boot volumes. Well, not officially, anyway.
The other thing I don't get is why I should be able to use my Amazon.com shopping account to log into AWS. It seems, well, silly, even with the two-factor authentication dongle, that the same account used to buy Kindle books and Fisher-Price toys is paying for my AWS usage.
I don't know what bothers me more: the outage itself or the alternative codes Amazon used for punctuation in that email that made my post look messed up only after I posted it.
That analogy is just like Irwin Allen's movie "The Towering Inferno."
Dear AWS Customer,
Starting at 12:47AM PDT on April 21st, there was a service disruption (for a period of a few hours up to a few days) for Amazon EC2 and Amazon RDS that primarily involved a subset of the Amazon Elastic Block Store (âoeEBSâ) volumes in a single Availability Zone within our US East Region. You can read our detailed summary of the event here:
http://aws.amazon.com/message/65648
Weâ(TM)ve identified that you had an attached EBS volume or a running RDS database instance in the affected Availability Zone at the time of the disruption. Regardless of whether your resources and application were impacted, we are going to provide a 10 day credit (for the
period 4/18-4/27) equal to 100% of your usage of EBS Volumes, EC2 Instances and RDS database instances that were running in the affected Availability Zone. This credit will be automatically applied to your April bill, and you donâ(TM)t need to do anything to receive it.
You can see your service credit by logging into your AWS Account Activity page after you receive your upcoming billing statement.
Last, but certainly not least, we want to apologize. We know how critical the services we provide are to our customersâ(TM) businesses and we will do everything we can to learn from this event and use it to drive improvement across our services.
Sincerely,
The Amazon Web Services Team
This message was produced and distributed by Amazon Web Services, LLC, 410 Terry Avenue
North, Seattle, Washington 98109-5210
Whom else is reminded of AOL's 19-hour outage in 1996? Routers misconfigured to send data to the wrong place, cascading into failure?
I dare say that HIPAA and SOX, and others, have something to say about that. They do, indeed, address the destruction of data-at-rest. The chain of custody does not end with bankruptcy or change of ownership of a data medium.
Amazon and Microsoft have to distinctly different views of "cloud computing."
When I first learned about "cloud computing" I automatically assumed it meant that there would be an arbitrary number of different services available to an arbitrary number of web servers which would then be served to the user. No one service would depend on the other.
Amazon's "cloud computing" is centralized upon the virtual machine as the hub of the "cloud." Microsoft Azure, on the other hand, originally offered the approach that I had thought about, where everything is just a service, no VM required.
Today Amazon still depends heavily on the VM concept. You can't have a web service on Amazon without one. This also makes it excessively difficult to "load balance" or provide "failover" because you are actually expected to stand up new VM instances to scale up and down and need separate VM instances on each "availability zone." In addition it's not easy or affordable to share data between availability zones. This isn't what I thought the cloud was going to be.
Microsoft eventually added VMs to its Azure service so they could compete with Amazon's VM-centralized concept. I still think the idea of separate, independent services talking to each other was what the "cloud" was supposed to be, and if these services didn't have to depend on these VMs (which they do not have access to because AWS is intermittently down) they would have still been working from the other data centers.
Off-brand MP3 players do this, too.
The "manufacturer" puts in a memory module of 1/2 or 1/5 the size it says on the box and they disable "media full" errors which results in the looping effect that the drive in the article had.