I'm somewhat out of the loop with my protocols, so can anyone tell me what the advantages are of all the xDAV protocols over SyncML? That's the one bit of information I've been unable to find anywhere - e.g. why Apple decided CardDAV was required instead of just using SyncML, for example.
Because getting rid of the state religion, and the state relationship with the church of england would be problematic. It's not that it can't or won't be done, but there's quite a lot of legal effort involved in the powers of parliament vs the sovereign vs the church as an independent entity.
In some respects it's the same reason why none of the countries have actually settled the legal inheritance issue of if the Duke and Duchess of Cambridge have a daughter and then a son (just a daughter, or multiple daughters doesn't require any rewrite), because it's not that we can't sort this out. But it's a lot of legal paperwork that can be deferred 50 or 60 years if they never have a son after a daughter.
I was under the impression that they sorted this out very recently: http://www.bbc.co.uk/news/uk-20600543
Depends entirely on your requirements of course, but what would be the problem with running a local Apache instance?
Only time it cropped up for me was when I had one slight hiccup and I had to fallback to XSL transforms on the server side when the client didn't support them (but still wanted to use them normally). I was able to quite easily write a protocol handler for PHP that implemented multiviews for local filesystem calls, and it works really nicely!
..or Apache multiviews using the content-accept header.
URLs should identify resources, not files anyway, so "/images/background10.jpg" should have the URL "/images/background10" anyway, then you're free to have multiple formats that can supply said resource on the server and vary depending on the client's preferences.
...I just wish Nokia had had more of a clue and made more of Maemo open so we could see it running on more devices. It's an awesome system...or at least the Debian bits are. The Nokia bits...less so. So much potential though.....
...yet the Victorians managed to convert a large chunk of the Great Western Railway over a weekend from broad gauge to standard gauge. *sigh*
Indeed. You would think that by now people wanting to work on these things would learn the lesson and tie yourself closer to a parent distro like Debian which has some kind of longevity.
A friend of mine who works for the BBC was discussing DAB with a colleague of his and me, and pointed out that apparently, DAB was designed to be used with a satellite acting as in-fill to give the expected blanket coverage. The half-arsed implementation means they skimped on the satellite bit, so that's why you get spotty DAB coverage. Not to mention the ancient crappy codecs.
...and for the people who want to chat with their Windows-using social groups?
I'm being pressured into either letting my users use the official MSN bloat-client or Skype so that they can video conference with other Windows users. Google could have sown this market up if they just put the ruddy jingle support into GTalk rather than GMail. Seriously, who wants to use a web page as an app on a desktop machine?
What I ideally want is Jingle support in Pidgin on Win32 and then native-jingle support in the various xmppmsn gateways.
"There is truth to one of the rumors, however. During WWII the American Red Cross did indeed charge American servicemen for coffee, doughnuts, and lodging. However, it did so because the U.S. Army asked it to, not because it was determined to make a profit off homesick dogfaces.
The request was made in a March 1942 letter from Secretary of War Henry L. Stimson to Norman H. Davis, chairman of the American Red Cross. Because American soldiers were fighting as part of the Allied Forces, matters had to be considered on a Force-wide rather than solely American basis. The Red Cross was asked to establish club facilities for U.S. servicemen overseas where Allied troops would be welcome. Because English and Australian soldiers were being charged for the use of such facilities, it was deemed unfair that Americans were to get similar benefits for free, especially in light of their pay already being higher than that of their Allied counterparts. For the good of the alliance, the American Red Cross was persuaded to exact nominal charges from American GIs for off-base food and lodging."
Fair enough. Personally, I found the phone usable before they added the paging though. The only thing that caused problems was websites that really overdid the flash and crappy layouts requiring constant reflow (*cough*Slashdot*cough*).
I never did understand how a phone with 96MB of RAM struggled whilst an old PC of mine with 16MB used to manage just fine...
My Nokia N95-1 did.
Original firmware: 10.0.018, released 15/03/2007
Latest firmware: 35.0.002, released 22/12/2009
Nokia used to be great
Yeah, I'd pretty much figured that was the case as well. A shame, as it's much more practical to have an application sitting in the system tray than a browser tab/window hogging tab bar/taskbar space.
I really don't see that being the outcome. The Skype stuff will probably just be in parallel to the XMPP stuff. In fact, I wouldn't put it past Skype to try and get Facebook to shut down the XMPP stuff so more users have to use Skype clients to even text chat outside of the Facebook website. Big companies like walled gardens and proprietary protocols.
What I'd have much preferred to have seen would be a XMPP-video based feature, a-la Google's GMail/XMPP Jingle video. Incidentally, does anyone have any idea why the GTalk client doesn't support it, but ruddy GMail and the N900 does?
The lack of any decent Jingle clients on Windows isn't such a hurdle if Facebook were to use a browser plugin like GMail (or indeed, sort out using the same one).
N900 FTW.
The cost of feathers has risen, even down is up!
