Ben Langhinrichs

Photograph of Ben Langhinrichs
E-mail address - Ben Langhinrichs






April, 2018
SMTWTFS
01 02 03 04 05 06 07
08 09 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30

Search the weblog





























Genii Weblog


Civility in critiquing the ideas of others is no vice. Rudeness in defending your own ideas is no virtue.


Wed 18 Apr 2018, 11:11 AM
ROI reaction gif
 
Way back in 1997, I released the Midas Rich Text LSX, a quirky-as-hell product which made manipulating Notes rich text not only easy, but kind of fun. You could sort tables on the fly, access almost anything, search and replace almost anywhere, lots of stuff, and it didn't think of rich text like IBM did, but like its users did. Fairly quickly, Midas became a hit as developers built all sorts of interesting and dynamic applications. It didn't cost very much, either. Personally, I thought it had a window of opportunity of about four years, if I was lucky, before IBM would swoop in and create something that would put me out of business. 
 
My youngest son was 2, and crawled all over me while I answered support calls. Fast forward 20 years, past a great many enhancements and additions and an eventual rename to the  Midas LSX, because it does so much more. The biggest reason people buy Midas these days is to generate high quality HTML/MIME/EPUB/CSV/etc. Some still use it for generating fancy emails or creating tables on the fly. My youngest is out of college now.
 
But about a half dozen times a year, I get a message from a company who has been using Midas for a decade or more, sometimes almost two decades. They've usually fallen off our radar screen, not on maintenance, not upgrading, just running apps that enhance their business year after year. They call because they switch servers or upgrade software, and manage to lose their Midas software or license or change server names so the license doesn't work. They call because this app which is so important suddenly doesn't work. Sometimes they know it is a problem with Midas, sometimes they've long forgotten they even use the product. I help them out however I can, though sometimes the combination of Notes version and Midas version is not only unsupported but dangerous. I'm helping one now that hasn't been in touch since 2004 for a Midas license they bought in 2002. Sixteen years, that app has been chugging along basically untouched. I wonder how many others like that are still humming away.
 
Sometimes, such customers buy a new license. Sometimes, I give them enough information that they get restarted with the old software and license they already have. The ROI is pretty spectacular, either way. Now, with Notes 10 on the horizon and the Notes/Domino sunset seeming further off, many of these companies are happy to spend a little more money and look forward to another decade or two of use.
 
It's been a long strange trip, as the Grateful Dead might say, and with Notes/Domino 10 on the horizon, it isn't over yet. I sell Midas to new customers, to old customers, perhaps even to you. It is not our most successful product if you simply go by total sales (that would be CoexLinks Fidelity), though it is close, but it is the longest running success story we have.
 
Have you tried Midas yet? There's still time to discover the magic, and even more time to enjoy the return on investment.
 

Copyright © 2018 Genii Software Ltd.

Tags:

Wed 4 Apr 2018, 02:39 PM
Inline JPEG image
 
There's a lot of talk about GDPR and its implications for Domino and other software environments. One frequent reminder is that backups and archives are included in the right to be forgotten. Now, if you are a small shop and have infrequent GDPR requests, anonymizing backup and archive copies might be a tedious but doable task. But what it you are faced with many of these?
 
One possible solution is the idea of pre-anonymizing. Imagine that every named person is given a unique id code, and a lookup table is maintained. Then the backup or archive process itself could include a translation process where the named person was replaced with the unique id code. If there were some later point where the named person needed to be forgotten, the archive itself would be left untouched and the index containing the name to id would have the name removed. Thereafter, the id would return "not found" when anyone tried to retrieve the name.
 
This isn't a perfect solution, and there might need to be a periodic garbage collection where all unknown ids were converted to a single UNKNOWN id, but particularly for difficult to access backups stored in long term storage, it would provide a way to "forget" without altering the storage. It also might require too much effort per backup/archive, though it would also conversion of various names, nicknames, email addresses, etc. to the single code, which would also make retrieval of information on a request easier.
 
I do wonder how referenced but non-specific names in rich text would be handled. If the rich text says "Alan told me we could bill Krangdon and CC it to Krangdon's VP of Operations" would Alan and Krangdon's VP of Operations need to be identified by context for both the purpose of notification and anonymization. I imagine there is some level of specificity beyond which you could not be expected to identify a person (e.g., Jim's wife), but if I am wrong, Watson is going to be needed just to find the references. Interesting times.
 
Note: For what it is worth, it would be possible to pre-anonymize working Notes databases, but it would take more effort than seems worth it. For example, in ACLs and such, you could use the id and then have a group named after the id with a single member for each internal user. But other places would be worse, and there would need to be lookups frequently, so I doubt it is a good idea.

Copyright © 2018 Genii Software Ltd.

Tags: