Solution: Start telling MSIE users to upgrade when they show up at your website, and if they don't, tell them to shove off.
Yeah, I pretty much do that on my site (www.sff.net/people/N7DR/). I don't suppose it's ever caused a single person to switch, but it sure makes me feel better.
Oddly, I've never had anyone tell me my site is "broken" (which is what I expected). Perhaps the text that says: "This web page has been verified by the W3C HTML and CSS validators" is read as a warning not to argue.
Or Google's Jabber client. I have a Jabber server, but I never use it. Does anyone use Jabber?
Well of course the silly answer is, Yes. The slightly less silly answer is that I too have a jabber server, and have been happily running it for several years, and using it essentially every day. Right now, I'm using it to read the commentary on a cricket match.
Sure I have accounts on a couple of the commercial IM networks, and it's true that sometimes one does have to resort to using them, but only for the same reason that people seem to put up with Windows: they'll put up with the commercial IM networks because no amount of arguing will convince them that there could be anything better. (At least, no amount of arguing from me ever seems to have any effect.) If someone asks for my IM handle, I never volunteer one of my commercial names unless I really want to talk to them, and even then I make a point of telling them that I'm on jabber but going through a gateway to get to their commercial network. Even if it doesn't make them change, I figure that if they want to talk to me, they might want to talk to other geeks, and if they hear the same thing from a few people they might eventually want to consider switching, even if it's only as far as google.
Then last == never. Because it's never had ads. Ever. That's the whole point of the license: it makes the Beeb independent of commercial interests. At least in theory. From my experience that independence has had the interesting side-effect of pretty much forcing commerical TV in Britain also to act fairly independently of the people that advertise on their channels.
Well it's a disaster on my Mandriva 2006.0 system. It doesn't crash, but the mosaics have bits and pieces of land and sea scattered seemingly at random all over the globe.
There's nothing like a CW QSO with someone who doesn't speak the same language as yourself, or a long CW ragchew with an old timer, or breaking a pile-up while knowing that you are weaker than many other signals in the pile-up. I rarely get on SSB, but CW is most definitely still fun.
But it is sadly true that in the US interest in CW has declined precipitously. If I tune across the CW end of 20 metres during a work day, there will usually be only one or two signals from the US (at least that's all I hear here in Colorado). Fortunately, CW still seems to be going quite strong in the rest of the world. Although in Colorado conditions need to be fairly decent for us to hear them.
From what I saw, his MAIN complaint is that it froze and spontaneously reboot often, had poor battery life, and a relatively long boot time.
I didn't understand these at all. I have had exactly one freeze/reboot -- immediately after installing a 512MB card and symlinking a bunch of system files so that they actually resided on the card instead of the N770's internal RAM. I did have a nasty moment when that reboot occurred, wondering if I'd broken something badly, but in fact after it rebooted everything was fine (and actually the instructions said to reboot anyway, so it's possible that it may even have been added to the install script to save one the effort of booting manually).
So, apart from that one instance: no freezes, no reboots. Battery life is not great (like 3-4 hours browsing; but then I can't imagine why anyone would want to browse for an extended period with a pocket device anyway).
Boot time is quite long -- but then how often does one reboot? I've only done it about three times while messing around with hacky sorts of things, and under normal use I don't know why one would want to reboot.
So I'm really happy with mine. And BTW it does take standard cellphone batteries, so one can always carry a cheap spare if one wants to, although I really don't see the need.
It was a Z-5500. The big advantage of the N770 to me was that this has a real web browser in it, and has built-in wifi (i.e., the very things that it's advertised to have).
The downside is the poor PIM software -- but on the other hand, I never found any decent PIM software for the Z either. I loaded our corporate contact list on to the Z (running Opie). And now it takes 24 (count 'em... 24) seconds just to open the Contact list.
I have every hope that the GPE PIM suite is going to evolve to be a lot more usable than the PIM software on the Z. There are a couple of programs on my Z that I miss, but again it's early days for the N770, and I have reasonable expectations that usable substitutes will appear in due course. Neither device is perfect (some sort of combination of the two would be awfully close to perfect), but of the two I much prefer the N770.
One real bonus for the N770: if one misses a program, there's a good chance that a web-based substitute will be available. Not a perfect solution, but workable until the application base for the N770 expands a bit.
I fully expect the successor to the N770 to be a really dynamite machine, assuming that Nokia doesn't just kill the line. But the N770 as-is is good enough for me not to want to wait for the next model.
I have seen several reviews of the N770 that for the most part come down "this device is no goo because it doesn't do X", for some value of X that the reviewer seemed to think vital.
All I can say is that I finally saw one of these about three weeks ago, and immediately (as in, next day) went to CompUSA and bought one. I love it. It does exactly what I want, and the only complaint I have is the lack of software -- but that will be quickly solved as the community ports apps to it. www.maemo.org is very active.
So it does what I want, and I think it's great. Obviously, if it doesn't do what you want, you'll think it's awful/pointless/a waste of money.
It has replaced my Zaurus (and has the added benefit that the form factor is almost identical to the Zaurus, so I can even use the same case for the N770).
Except for the handwriting recognition, they were available five years ago. There apparently aren't many people who share your needs (although I'd count myself in that group).
I never understood why the Rex didn't become ubiquitous and make the inventors very, very rich. Mind you, I had the same thought about the Crosspad which was an utterly brilliant piece of hardware doomed by some of the most awful pre-beta software I've ever encountered.
...this seems to solve exactly the inverse problem to the one I see.
In an interaction between an autistic person and a "normal" person, what I see is that it's the autistic (and/or emotionally challenged) person who gets bored and simply walks away, with little or no prior warning. I have seen this happen too many times to count. I don't think I've ever seen the "normal" person be the one to react by becoming bored; usually simply trying to comprehend what the other person is saying/doing is enough to keep them engaged.
but which C and C++ can't really make use of given the complete lack of compiler support.
I wouldn't know about C, but this statement is utterly false as applied to C++. Replacing the default new and delete routines is perhaps not for the inexperienced C++ programmer, but to say that there's an complete lack of compiler support is simply wrong. It is true that out-of-the-box C++ does not have a compacting garbage collecter, but one can certainly be written (and used, of course) with any conformant compiler.
... SuperKaramba. Desktop widgets, and it's been out for years.
And unfortunately it crashes almost daily, at least on my machine. Because of the instability of superKaramba, I have been waiting for Konfabulator to be ported to Linux, but maybe this KDE4 feature will arrive first. I will say that I originally thought that all these desktop thingies were nothing but eye-candy, but it turns out that I actually find them very useful.
Mandriva Linux 2006 includes xen0 and xenU-enabled kernels and the Xen supervisor utilities package. The Community version of Mandriva 2006 can be downloaded from many Linux mirror sites.
But unfortunately it's broken on 64-bit machines. (see bug #18432 at qa.mandriva.com; Mandriva says that they will upload the x86_64 glibc-xen packages when they have verified that xen works
with their x86_64 kernels, which they currently don't).
So: consumers are entitled to run applications and use services of their choice, subject to the needs of law enforcement.
Which, translated into English, means: "if you want to use service X, but Law Enforcement can't tap service X, then you no longer are entitled to use X". For "X" substitute whatever service you like. Wonderful.
I have a project that's about 1/3 the size of yours, with VC++ 6.0 as the development environment.
Out of interest I purchased VC++.NET 2003 a while ago.
Once I fired it up and tinkered a bit with the IDE, all thought of porting the project went away. Things look quite different (and, at least in my case, the help that came in the package was a big fat zero). I eventually worked out how to build a small test project and have it run. But to take a complex pre-existing project looked like a job that one would take on only if one absolutely needed something that was only available in 2003.NET. (In fact, my first reaction on seeing the IDE was: Good Grief! Why does everything nowadays have to be so complicated? I had hoped for a reaction along the lines of: Oh good! This looks like something I'm used to. But it was Not To Be.)
Now, rumour has it that the 2005.NET compiler is going to have lots of support for fancy stuff like template metaprogramming. So I can see using it for new projects if the new stuff is going to be useful in those projects. But as for porting an old project, I have to assume that 2005 is going to be at least as far removed from 6.0 as 2003.NET was. And since you already have the project building and working under 6.0, I would not recommend the switch.
Maybe if you have the capability and version control resources to keep using 6.0 as your mainline code while you tinker to get 2005.NET working, then that might be reasonable. But unless you have spare people/time, I honestly don't think it would be wise to try to make the switch
Of course, a lot of professionally typeset books have truly awful typography as well these days, either through using poor technique, or through trying to be a bit too clever.:-(
Or, I have to say, simply through being clueless. Having published several books of various types with several publishers, I am consistently appalled that a non-professional such as myself who has taken the time to read and understand Knuth's musings on TeX, LaTeX and MetaFont ends up knowing far more about typography than any of the people with whom I have interacted at publishing houses.
I knew that the sky was falling in when O'Reilly told me to use Word instead of TeX, because they no longer had anyone who knew enough about TeX. No one seems to care any more about using typography properly. It's very sad. I miss the days when people took pride in stuff like this.
PacketCable VoIP security
on
VoIP Security
·
· Score: 4, Interesting
This is why the PacketCable 1.0 VoIP security spec runs to nearly 400 pages. (www.packetcable.com)
Of course, now ask how many cable compaines are actually deploying fully PacketCable-compliant systems with all the security turned on the way it was designed to be.
Will the new Mandriva distribution use urpmi, if not, could it be similar to apt?
I've seen posted somewhere that it will support both urpmi and apt. I too have suffered from urpmi doing some weird things, and am looking forward to trying apt.
Actually, I wonder why no distro seems to be using autopackage (www.autopackage.org); it seems to claim to solve dependency hell in a distribution-neutral way. (I confess that I am pretty fed up of not being able to install newer versions of my favourite apps on my Mandrake 9.2 systems. Whenever I try, I enter dependency hell and quickly give up.)
I have little doubt that for most people there are few if any issues.
However, if one builds long, complicated documents one begins to see several problems.
I author standards documents, so my typical document is somewhere between 100 and 200 pages long, has quite complicated formatting and internal cross-referencing, and has changes tracked. I emphasize the last because I suspect that it is the cause of most of the problems I see. The documents circulate among several companies and several varieties of Word; as far as I know, I am the only contributor who uses OOo.
OOo2 beta tends to be more accurate in formatting than does OOo 1.1.4 (one frequently hears about OOo 2's improved Word support, and I think that this is mostly what is meant). However, almost all the recent OOo 2 betas have crashed when trying to open this sort of document, even though Word and OOo 1.1.4 have no trouble with the same document. I expect (well, I hope) that they will fix this before OOo 2 is released.
The kind of things that I see when passing these documents around: changes are improperly tracked (often I will make an edit, but if I then save the document and re-open it, deletions re-appear, or other bits of text are deleted); adding captions crashes OOo; Word crashes when opening a document produced by OOo; Figure placement is different if I open a document in Word as compared to OOo; sometimes, the same Figure appears multiple times.
This all sounds pretty bad, but let me reiterate that these problems only seem to occur in complicated documents that are being passed around in.doc format among several organizations using multiple versions of Word.
The sad part is that because the documents always contain proprietary information, I can't simply send the documents to the OOo developers so that they can duplicate the problems and fix them.
It is tempting to suggest that even if OOo wasn't in the picture, some of these problems would exist because of the use of multiple versions of Word -- however, I have never seen that happen. I have seen minor formating differences among the different versions of Word, but that's all.
Worse, even for stand-alone use, the upgrade process just installs a new copy over top of the old. (redundant add/remove program item, desktop icons, and all!)
Yes, I couldn't believe it when I was noodling around Add/Remove Programs on a Windows systems recently and saw a slew of FF/TB entries. I removed an old one, and promptly discovered that the current installation stopped working. I shifted the disk back five minutes with GoBack so no harm was done, but it did strike me as something that surely should have been fixed before releasing these programs to the general public.
That means with many users, each user could end up with dial-up speeds. Correct?
On average, yes. But the typical cable modem connection in the US also offers somewhat less than dial-up speed. If every user tried to access the Internet at exactly the same time, they would receive between 40 and 50 kbps service, depending on which cable provider they used. Of course, due to the magic of stat muxing, this never happens, and people are (mostly) very happy with their multi-megabps download speeds. (DSL, of course, is a different matter entirely, since that access network is not a shared medium.)
They'll need that head start.. Has anyone here actually tried developing for the Mozilla platform? It isn't a walk in the park. The documentation available on XULplanet, mozilla.org, etc, although improving, is rather sparse and frequently out of date. Even some books on mozilla development are out of date already - RAD in Mozilla (published this year I believe) has some wrong details about XUL tree selections, for example. One thing that the mozilla development community needs badly right now is a php.net, wiki-style website to encourage anyone and everyone to frequently update documentation easily and in small pieces.... This basic documentation step needs to be done to encourage people to develop sites and applications for the Mozilla platform....
I couldn't agree with this more (and I wish that I hadn't already posted elsewhere in this article, so I could mod this up:-( ).
I have on three separate occasions started to attempt some some-scale Moz-based Web Service development stuff, armed with books and the lastest available info off the mozdev site. On all three occasions the result was the same: after about eight hours of massaging examples with increasing frustration, I finally admitted defeat and decided to wait until someone else has done something sufficiently similar so I could look at it and figure out how this stuff really works.
Now, I readily admit that I was doing this simply for fun to try to understand how things like SOAP are supposed to work in Moz -- so I wasn't in the usual panicy desperation mode that absolutely forces one to figure things out at any cost, but even so I found it disheartening that I couldn't simply read an article and example or two and make stuff work.
Doesn't work here: the enigmail XPI file installs, but the enigmime one won't install because TB 1.0 says that the enigmime module is only for versions 0.8 to 0.9+:-(
Since the enigmime module is unchanged, I have a feeling that if only I could tell TB "ignore the warning and install and use it", everything would be OK. But there doesn't seem to be any way to do that.
Slashdot Mirror
Yeah, I pretty much do that on my site (www.sff.net/people/N7DR/). I don't suppose it's ever caused a single person to switch, but it sure makes me feel better.
Oddly, I've never had anyone tell me my site is "broken" (which is what I expected). Perhaps the text that says: "This web page has been verified by the W3C HTML and CSS validators" is read as a warning not to argue.
Well of course the silly answer is, Yes. The slightly less silly answer is that I too have a jabber server, and have been happily running it for several years, and using it essentially every day. Right now, I'm using it to read the commentary on a cricket match.
Sure I have accounts on a couple of the commercial IM networks, and it's true that sometimes one does have to resort to using them, but only for the same reason that people seem to put up with Windows: they'll put up with the commercial IM networks because no amount of arguing will convince them that there could be anything better. (At least, no amount of arguing from me ever seems to have any effect.) If someone asks for my IM handle, I never volunteer one of my commercial names unless I really want to talk to them, and even then I make a point of telling them that I'm on jabber but going through a gateway to get to their commercial network. Even if it doesn't make them change, I figure that if they want to talk to me, they might want to talk to other geeks, and if they hear the same thing from a few people they might eventually want to consider switching, even if it's only as far as google.
Then last == never. Because it's never had ads. Ever. That's the whole point of the license: it makes the Beeb independent of commercial interests. At least in theory. From my experience that independence has had the interesting side-effect of pretty much forcing commerical TV in Britain also to act fairly independently of the people that advertise on their channels.
Well it's a disaster on my Mandriva 2006.0 system. It doesn't crash, but the mosaics have bits and pieces of land and sea scattered seemingly at random all over the globe.
But it is sadly true that in the US interest in CW has declined precipitously. If I tune across the CW end of 20 metres during a work day, there will usually be only one or two signals from the US (at least that's all I hear here in Colorado). Fortunately, CW still seems to be going quite strong in the rest of the world. Although in Colorado conditions need to be fairly decent for us to hear them.
I didn't understand these at all. I have had exactly one freeze/reboot -- immediately after installing a 512MB card and symlinking a bunch of system files so that they actually resided on the card instead of the N770's internal RAM. I did have a nasty moment when that reboot occurred, wondering if I'd broken something badly, but in fact after it rebooted everything was fine (and actually the instructions said to reboot anyway, so it's possible that it may even have been added to the install script to save one the effort of booting manually).
So, apart from that one instance: no freezes, no reboots. Battery life is not great (like 3-4 hours browsing; but then I can't imagine why anyone would want to browse for an extended period with a pocket device anyway).
Boot time is quite long -- but then how often does one reboot? I've only done it about three times while messing around with hacky sorts of things, and under normal use I don't know why one would want to reboot.
So I'm really happy with mine. And BTW it does take standard cellphone batteries, so one can always carry a cheap spare if one wants to, although I really don't see the need.
The downside is the poor PIM software -- but on the other hand, I never found any decent PIM software for the Z either. I loaded our corporate contact list on to the Z (running Opie). And now it takes 24 (count 'em... 24) seconds just to open the Contact list.
I have every hope that the GPE PIM suite is going to evolve to be a lot more usable than the PIM software on the Z. There are a couple of programs on my Z that I miss, but again it's early days for the N770, and I have reasonable expectations that usable substitutes will appear in due course. Neither device is perfect (some sort of combination of the two would be awfully close to perfect), but of the two I much prefer the N770.
One real bonus for the N770: if one misses a program, there's a good chance that a web-based substitute will be available. Not a perfect solution, but workable until the application base for the N770 expands a bit.
I fully expect the successor to the N770 to be a really dynamite machine, assuming that Nokia doesn't just kill the line. But the N770 as-is is good enough for me not to want to wait for the next model.
All I can say is that I finally saw one of these about three weeks ago, and immediately (as in, next day) went to CompUSA and bought one. I love it. It does exactly what I want, and the only complaint I have is the lack of software -- but that will be quickly solved as the community ports apps to it. www.maemo.org is very active.
So it does what I want, and I think it's great. Obviously, if it doesn't do what you want, you'll think it's awful/pointless/a waste of money.
It has replaced my Zaurus (and has the added benefit that the form factor is almost identical to the Zaurus, so I can even use the same case for the N770).
I never understood why the Rex didn't become ubiquitous and make the inventors very, very rich. Mind you, I had the same thought about the Crosspad which was an utterly brilliant piece of hardware doomed by some of the most awful pre-beta software I've ever encountered.
In an interaction between an autistic person and a "normal" person, what I see is that it's the autistic (and/or emotionally challenged) person who gets bored and simply walks away, with little or no prior warning. I have seen this happen too many times to count. I don't think I've ever seen the "normal" person be the one to react by becoming bored; usually simply trying to comprehend what the other person is saying/doing is enough to keep them engaged.
I wouldn't know about C, but this statement is utterly false as applied to C++. Replacing the default new and delete routines is perhaps not for the inexperienced C++ programmer, but to say that there's an complete lack of compiler support is simply wrong. It is true that out-of-the-box C++ does not have a compacting garbage collecter, but one can certainly be written (and used, of course) with any conformant compiler.
And unfortunately it crashes almost daily, at least on my machine. Because of the instability of superKaramba, I have been waiting for Konfabulator to be ported to Linux, but maybe this KDE4 feature will arrive first. I will say that I originally thought that all these desktop thingies were nothing but eye-candy, but it turns out that I actually find them very useful.
But unfortunately it's broken on 64-bit machines. (see bug #18432 at qa.mandriva.com; Mandriva says that they will upload the x86_64 glibc-xen packages when they have verified that xen works with their x86_64 kernels, which they currently don't).
Which, translated into English, means: "if you want to use service X, but Law Enforcement can't tap service X, then you no longer are entitled to use X". For "X" substitute whatever service you like. Wonderful.
I have a project that's about 1/3 the size of yours, with VC++ 6.0 as the development environment.
.NET. (In fact, my first reaction on seeing the IDE was: Good Grief! Why does everything nowadays have to be so complicated? I had hoped for a reaction along the lines of: Oh good! This looks like something I'm used to. But it was Not To Be.)
.NET compiler is going to have lots of support for fancy stuff like template metaprogramming. So I can see using it for new projects if the new stuff is going to be useful in those projects. But as for porting an old project, I have to assume that 2005 is going to be at least as far removed from 6.0 as 2003 .NET was. And since you already have the project building and working under 6.0, I would not recommend the switch.
.NET working, then that might be reasonable. But unless you have spare people/time, I honestly don't think it would be wise to try to make the switch
Out of interest I purchased VC++.NET 2003 a while ago.
Once I fired it up and tinkered a bit with the IDE, all thought of porting the project went away. Things look quite different (and, at least in my case, the help that came in the package was a big fat zero). I eventually worked out how to build a small test project and have it run. But to take a complex pre-existing project looked like a job that one would take on only if one absolutely needed something that was only available in 2003
Now, rumour has it that the 2005
Maybe if you have the capability and version control resources to keep using 6.0 as your mainline code while you tinker to get 2005
Or, I have to say, simply through being clueless. Having published several books of various types with several publishers, I am consistently appalled that a non-professional such as myself who has taken the time to read and understand Knuth's musings on TeX, LaTeX and MetaFont ends up knowing far more about typography than any of the people with whom I have interacted at publishing houses.
I knew that the sky was falling in when O'Reilly told me to use Word instead of TeX, because they no longer had anyone who knew enough about TeX. No one seems to care any more about using typography properly. It's very sad. I miss the days when people took pride in stuff like this.
Of course, now ask how many cable compaines are actually deploying fully PacketCable-compliant systems with all the security turned on the way it was designed to be.
I've seen posted somewhere that it will support both urpmi and apt. I too have suffered from urpmi doing some weird things, and am looking forward to trying apt.
Actually, I wonder why no distro seems to be using autopackage (www.autopackage.org); it seems to claim to solve dependency hell in a distribution-neutral way. (I confess that I am pretty fed up of not being able to install newer versions of my favourite apps on my Mandrake 9.2 systems. Whenever I try, I enter dependency hell and quickly give up.)
However, if one builds long, complicated documents one begins to see several problems.
I author standards documents, so my typical document is somewhere between 100 and 200 pages long, has quite complicated formatting and internal cross-referencing, and has changes tracked. I emphasize the last because I suspect that it is the cause of most of the problems I see. The documents circulate among several companies and several varieties of Word; as far as I know, I am the only contributor who uses OOo.
OOo2 beta tends to be more accurate in formatting than does OOo 1.1.4 (one frequently hears about OOo 2's improved Word support, and I think that this is mostly what is meant). However, almost all the recent OOo 2 betas have crashed when trying to open this sort of document, even though Word and OOo 1.1.4 have no trouble with the same document. I expect (well, I hope) that they will fix this before OOo 2 is released.
The kind of things that I see when passing these documents around: changes are improperly tracked (often I will make an edit, but if I then save the document and re-open it, deletions re-appear, or other bits of text are deleted); adding captions crashes OOo; Word crashes when opening a document produced by OOo; Figure placement is different if I open a document in Word as compared to OOo; sometimes, the same Figure appears multiple times.
This all sounds pretty bad, but let me reiterate that these problems only seem to occur in complicated documents that are being passed around in .doc format among several organizations using multiple versions of Word.
The sad part is that because the documents always contain proprietary information, I can't simply send the documents to the OOo developers so that they can duplicate the problems and fix them.
It is tempting to suggest that even if OOo wasn't in the picture, some of these problems would exist because of the use of multiple versions of Word -- however, I have never seen that happen. I have seen minor formating differences among the different versions of Word, but that's all.
Yes, I couldn't believe it when I was noodling around Add/Remove Programs on a Windows systems recently and saw a slew of FF/TB entries. I removed an old one, and promptly discovered that the current installation stopped working. I shifted the disk back five minutes with GoBack so no harm was done, but it did strike me as something that surely should have been fixed before releasing these programs to the general public.
On average, yes. But the typical cable modem connection in the US also offers somewhat less than dial-up speed. If every user tried to access the Internet at exactly the same time, they would receive between 40 and 50 kbps service, depending on which cable provider they used. Of course, due to the magic of stat muxing, this never happens, and people are (mostly) very happy with their multi-megabps download speeds. (DSL, of course, is a different matter entirely, since that access network is not a shared medium.)
I couldn't agree with this more (and I wish that I hadn't already posted elsewhere in this article, so I could mod this up :-( ).
I have on three separate occasions started to attempt some some-scale Moz-based Web Service development stuff, armed with books and the lastest available info off the mozdev site. On all three occasions the result was the same: after about eight hours of massaging examples with increasing frustration, I finally admitted defeat and decided to wait until someone else has done something sufficiently similar so I could look at it and figure out how this stuff really works.
Now, I readily admit that I was doing this simply for fun to try to understand how things like SOAP are supposed to work in Moz -- so I wasn't in the usual panicy desperation mode that absolutely forces one to figure things out at any cost, but even so I found it disheartening that I couldn't simply read an article and example or two and make stuff work.
Take it for what you think it's worth, but IE 6.0 also passed with no errors on my WinXP SP2 system.
Doesn't work here: the enigmail XPI file installs, but the enigmime one won't install because TB 1.0 says that the enigmime module is only for versions 0.8 to 0.9+ :-(
Since the enigmime module is unchanged, I have a feeling that if only I could tell TB "ignore the warning and install and use it", everything would be OK. But there doesn't seem to be any way to do that.
If it isn't beautiful, it isn't true.