They'd win the Poker World Series. This is a winning hand to show, after all of the recent moves and relatively quiet action regarding the patent battles. Dont buy into the consortium, play victim and complain about others destroying android, then buy Motorola (and their 17000 patents).
Bravo!
The multicast address space in IPv4 is woefully small just a few
IPv6 is much more promising however, given the vast improvement in address space. The only problem with multicast in general, is that content providers dont like the lack of control (anyone can join a multicast stream WITHOUT the provider knowing about it). Providers want total control over every client (somewhat of a common theme with modern media delivery mechanisms).
Perhaps the solution, is some kind of crypto on the streams that clients must negotiate the key for via unicast before getting the stream. But then its scarily close to drm.
Either way, I'm quite excited about the possibility of v6 multicast taking off once v6 is the norm (probably not long after duke nukem forever is released).
For the same reason that any warranty-covered device loses the protection of the warranty if you change something on it - you can't guarantee that you didn't break it yourself.
Read up on the Magnuson Moss Warranty Act. This is an American law but most modern countries have laws with the same principles.
Essentially, warranties cannot be voided by modification unless the manufacturer can prove that the modification caused the fault. This is the reason why
you can install after market wiper blades and other accessories on your car without voiding the warranty. It would be outrageous for a car manufacturer
otherwise. They can only deny warranty repairs when your replacing of a component specifically contributed to that fault.
The same goes for phones - a manufacturer cannot deny a warranty repair on something like a loose screen or faulty button because you installed
an alternative OS on it. Of course, if you install something that lets you overstress a component (eg root the phone to drive an LED flash brighter than the stock OS), then they can deny the warranty on that component. But still would have to repair a loose screen, etc.
My Nexus S phone addresses this somewhat better than most. When you go through the legitimate unlock procedure, it warns that it "might" void some warranty, rather than stating that it "will".
So yeah, please stop spreading the FUD that jailbreaking/etc will void your warranty. It will NOT automatically void your warranty, and you can legitimately
argue with the manufacturer that many warranty claims are still valid.
Back in '06 (prior to the '09 filing date), this guy modded a mouse with a nokia lcd screen. I wonder how many of apple's patent claims are invalidated by this?
I came up with a different answer, based on the summary's wording.
Firstly, the sex of the second child is not determined by the first. Whatever one child is, the other will always be 50% chance of being either.
What we can deduce from the wording is that his other child is not a son born on a tuesday.
We draw a two column, 7 row matrix. The rows are days of the week, and the columns are boy/girl. Write a tick in each cell if that is a valid sex and day for the child. We are left with 14 possibilities. 7 of those are girls (a girl can be born on any day), but only 6 are boys (as according to the wording, only ONE is a son born on tuesday...if the other is a son, it cannot be a tuesday, so we are left with 6 days if it's a boy. We give that probability to the girl column.
Thus we are left with 8 out of 14 chances being a girl, and 6 out of 14 being a boy. In decimal:
Girl: 0.57
Boy: 0.43
QED.
What I'd like to see on Android, though, is a permission that controls whether an app is allowed to spawn background services, which would be listed alongside others in the confirmation screen when app is installed.
Whilst Android does not have this, since version 2.0 they have vastly improved background process behaviour.
Previous to 2.0, a service (ie background app) could request foreground priority, oblivious to the user. This would flag it as important enough such that it would not be killed when the system needed resources. The intention is things like music players needing to always keep playing the music.
Unfortunately human nature rolled in and every developer felt that _their_ app was the most important one on the system, so had useless crap always running (updates, lots of network polling, etc) and so with many apps installed, the system could become sluggish even if there was only one visible app in the foreground.
Since 2.0, the old system call for this (setForeground()) has been turned into a No-Op, and apps wishing to retain high priority privileges in the background are now forced to display a notification in the status bar. Result? Apps cannot quietly hog system resources, but now must inform the user, which has generally resulted in much less resource hungry apps, snappier performance, and better battery life.
Flying Sydney, Australia to California is similar. There have been numerous times when I departed Sydney after lunch on Saturday, spend 14 hours in a plane, then land at San Francisco in time for breakfast on _the same day_.
Amusing chat over IM with a friend one such day:
Them: How's your Saturday?
Me: Good, had lunch in Sydney then breakfast in San Francisco after that.
Them: wtf???
Does that mean that I could be sued for taking a shit after eating a Malay curry, on the basis that I'm making a "derivative work"?
Aren't hard disk prices always at an all time low? Have they ever gone up in price?
http://android-target.googlecode.com/ should be the correct one.
There are ~3500 android apps out there now, virtually every one of them written assuming HTC Dream hardware.
It will be very interesting to see how they all cope when run on emerging hardware with vastly different characteristics and screens to the opening device.
My own Android game is not exempt and will need better adaptability (yeah, hypocrite).
Already possible, alas you need an unlocked G1 for the tethering:
- Wifi, already there
- Sip: http://code.google.com/p/sipdroid/
- Bluetooth tether: http://code.google.com/p/android-wifi-tether/
Brain: Without it, im dead and wont care.
Hearth: Ditto.
Eyes: Can work around blindness ok.
Ears: Ditto.
Genitalia: Easy to be a nerd without.
Fingers: Cant code without fingers..aaaaah!
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson
