It took a minute to realize that it requires an internet connection. Maybe you should spell that out?
I thought at first you had compiled a corpus of knowledge, but this is much better, but with the requirement of internet access.
I thought at first you had compiled a corpus of knowledge, but this is much better, but with the requirement of internet access.
This is basically like those old Technet and MSDN programs for Windows, they searched the online Microsoft database for new content. I found that out the hard way when I was asking why I was using so much Internet and then I found out it was my MSDN lookups when encountering bugs in the Windows API calls etc and even if business related, management was counting them. Management didn't know the difference between MSDN and MSN even if they paid a lot for my MSDN subscription. Management was constantly searching MSN for stock quotes and news items BTW because it was the default web page in Internet Explorer.
Moving from Windows 95 and Office 97 to Windows 2000 and Office 2000 was a nightmare, because there were bugs and I was told Microsoft was aware of it and will fix it in the next service pack. We had gone to the latest and greatest of Microsoft's software instead of waiting for service packs to be released to address bugs so it is more stable. My Fax program used a Word Object to copy RightFAX codes into a document and print with a RightFax printer driver to fax out documents. Problem was Word 2000 had a bug that messed up the toolbar after a document was closed using the Word object in Visual BASIC. Microsoft admitted the bug, but didn't release a service pack to fix it yet. Management didn't understand that and had me search MSDN for a solution or maybe a beta service pack to address the issue. Then I am chewed out for wasting five hours searching the MSDN knowledgebase for a solution. I forget how we fixed it, but the work-a-round from Microsoft was to minimum Word 2000 and then restore it and the toolbar bug went away after that. After the service packs were released the bug went away.
While working for that company I suffered a nervous breakdown from the abuse and stress, and ended up on short-term disability, when I returned I was fired two weeks later for having a panic attack at work. They had moved me to an open area, no more cubical, near a bookshelf, and people mocked me and laughed at me as they walked by.
I had the right to sue, but because I am mentally ill, no lawyer would take the case. I am considering writing an ebook on the computer industry, as well as another ebook on what lead up to me becoming mentally ill and no longer able to work as a result.
Yes it was not a good work environment, it ruined my life and career.
You also don't know it until after you are hired, and you find out they install remote access trojans on your Windows workstation, and count the number of characters you type, and monitor your Internet use and don't know the difference between a work related site, a non-work related site, or just accessing ASP rendered pages on the Intranet I was developing for them. Basically it was a Big Brother type of organization, a law firm in downtown Saint Louis MO.
They also have odata endpoints so you should be able to get at the data (updated weekly) that way. It looks like there is a problem with it at the moment, though (I get 'server error'): http://data.stackexchange.com/stackoverflow/atom