TZUTC: -0500
MSGID: 1204.consprcy@1:2320/105 2cc3f6b3
REPLY: 1:135/250@fidonet 685dd4ec
PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/acc19483f Apr 26 2024 23:04 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
>  It should be easy for the gov't to produce an app that would be used by
> elected officials.

>  Different levels of encription could be divied out to different portions of
> gov't.

You would think so.  My limited experience with government programming
shops and web applications would be that, due to the pay gap vs. private
industry, the talent pool would be limited.

They'd either wind up with something not too secure or some "closed
source" application that was created "for government use" by a third-party.

That experience comes from watching employee turn over rates, and also from
working on disaster recovery exercises, where your inadvertantly learn some
things about what the web apps are doing in the background (like making
calls to servers for CSS, etc., that are outside of the government server
network).  Lots of "no-nos" can be exposed when doing disaster recovery on
a closed network.  ;)

Mike


 * SLMR 2.1a * (((((This message in Stereo where available)))))
--- SBBSecho 3.20-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 111 114 206 300 307 317 400 426 428
SEEN-BY: 229/470 664 700 705 266/512 291/111 320/219 322/757 342/200
SEEN-BY: 396/45 460/58 712/848 902/26 2320/0 105 304 3634/12 5075/35
PATH: 2320/105 229/426