Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 15,792 of 16,010    |
|    Daniel to All    |
|    Opinions on a door idea    |
|    02 Jul 24 12:26:25    |
      INTL 3:770/1 3:770/3       REPLYADDR me@sc1f1dan.com       REPLYTO 3:770/3.0 UUCP       MSGID: <87h6d7y4ri.fsf@raspberrypi> 67a75d5c       PID: SoupGate-Win32 v1.05       Hi folks -              I have a door idea and wonder if it's possible. I'd like to create something       of a very limited electronic flight book (EFB) in BBS form. As background,       pretty much all software tools I use to do flight prep is done on my android       tablet. Weather data, maps, etc are all downloaded from sources provided by       the government and displayed in the apps. Laws & Regulations come from       ecfr.gov. Weather data from aviationweather.gov (awc). Aeronautical       Information Manual (AIM) from faa.gov. And etcetera.              Right now, my focus is on ecfr.gov. They have a limited rest API setup for       all matters of querying the database except for the actual regulation. By       that I mean, if I understand all the options correctly, I can't use the API       to pull up an individual regulation, like, 14 CFR part 91.109              If I attempt accessing it with lynx, I get this generic error:              "Due to aggressive automated scraping of FederalRegister.gov and eCFR.gov,       programmatic access to these sites is limited to access to our extensive       developer APIs."              It's funny how they call it extensive. They must be using a government       version of the english dictionary. It goes on:              "If you are human user receiving this message, we can add your IP address to       a set of IPs that can access FederalRegister.gov & eCFR.gov; complete the       CAPTCHA (bot test) below and click "Request Access". This process will be       necessary for each IP address you wish to access the site from, requests are       valid for approximately one quarter (three months) after which the process       may need to be repeated."              I don't get this message on a normal javascript enabled browser. I surmise it       views queries from non-javascript browsers as a curl-like command.              My suspicion is that the undocumented features of the API are used by the       site. So I wonder if such calls could be derived by looking at site's code.              Now, the door I have in mind, would list all the regulation parts suggested       for each particular rating. Select the regulation and it would pull the data       for output. This would be a minimum feature for v1.0 of the door. Various       other queries would be added over time. And, of course, other data from       various sources would fold in too.              Here's the URL: www.ecfr.gov              Now, i considered downloading the entirety of the regulations and simply       writing code to query it. But, these regs change all the time. New regs       appear. Some amended. Some abolished. So, it's an organic thing. I'd rather       maintain API calls to be honest.              Lastly, this door idea would be implemented on my future BBS, focusing on       aviation and radio related hobbies.              Thank you -              Daniel              --- SoupGate-Win32 v1.05        * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)       SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/260 129/305 153/757       SEEN-BY: 153/7715 154/10 30 203/0 218/700 840 220/70 221/0 226/17       SEEN-BY: 226/30 100 227/114 229/110 111 112 113 206 275 300 307 317       SEEN-BY: 229/400 426 428 470 550 664 700 240/1120 5832 266/512 267/800       SEEN-BY: 280/464 5003 282/1038 291/111 292/854 8125 301/1 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124       SEEN-BY: 467/888 633/280 712/848 770/1 3 100 340 772/210 220 230 5020/400       SEEN-BY: 5054/30 5075/35       PATH: 770/3 1 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca