I work in government. Link 1 (2018) is essentially a dream. All of government got forced to use MS Dynamics CRM. Basically, anybody with a software requirement for case management, had to use MS Dynamics. I recommended we use Drupal in 2011. That was killed because everything had to be MS. I'm kind of surprised that it is in there given that nobody was allowed to use.
Link 0 and 2 are essentially from TBS and CDS. They coexist together. They are essentially working at the very top as entities that gather information from other departments. They can do whatever they want because they help write the rules.
I'm not trying to discredit your post, just saying that as someone who has brought OSS tools to development at the government and tried to use OSS tools for client (I failed at that), it is nearly impossible at the moment. We are married to Microsoft and its cloud.
I do agree, that it may take an entire generation because right now, 190+ departments are not exactly jumping to FOSS, and in many situations, they are down right told you are not allowed.
In addition, the current de facto document management system is from OpenText. Although many just use Sharepoint Online.
Ironically, as everything moves to the cloud, it would be easier to move to a solution that is FOSS based, and based in the cloud. Technology has matured enough that you don't need executables on a desktop, you just need a browser pointing to a website.
Agreed. I worked on the Canadian side of the legal side and there is a very comprehensive process for redaction. Nobody does redaction unless they follow the process. Never seen anyone 15+ years do something silly like this in the office.
Adobe Pro, when used properly, will redact anything in a PDF permanently.
Whoever did these "bad" redactions doesn't even know how to use a PDF Editor.
We have paralegals and lawyers "mark for redaction", then review the documents, then "apply redactions". It's literally be done by thousands of lawyers/paralegals for decades. This is just someone not following the process and procedure, and making mistakes. It's actually quite amateurish. You should never, ever screw up redactions if you follow the proper process. Good on the X-ray project on trying to find errors.
I just want to add, applying black highlights on top of text is in fact, the "old" way of redaction, as it was common to do this, and then simply print the paper with the black bars, and send the paper as the final product.
Whoever did it is probably old, and may have done it thinking they were going to print it on paper afterwards!! Just guessing as to why someone would do this.
Yeah, we were locking down the phones anyways, so in terms of features, they didn't use much. However, it's interesting you mention email because even in 2019, the Android system was better for email, and supported encrypted emails, Apple did not. We were told it was in the works, and a few months later, we could send encrypted email. We also had some weird bugs to iron out.
I always remind myself, that Apple does not care for corporate clients, just consumers. So I had to assess what we absolutely needed, vs what could be taken away.
Not surprised. I met with Samsung for work purposes to buy hundreds of phone, and the best they could do with their flagship phones was offer 3 years of security updates. This was around 2019. Apple, who didn't meet with us, was around 6 years from our estimate.
From a ROI, for corporate phones, Apple iPhones had a longer lifespan, which is why we bought hundreds of iPhones, and not Androids.
On a personal note, I had the Nexus S, the Nexus 5, and they all died a horrible death either from lack of updates, or just having the physical button break, and the microphone stop working.
And let us not speak of Sony Xperia Z5, which all of sudden removed their fingerprint sensor due to a North American patent problem. They also broke their bluetooth audio so that song names STOPPED being displayed. That was all in a span of less than 3 years.
Never again Sony Android phones.
At that point, I got fed up of custom ROMS and joined the "iPhone, it just works" group and moved on.
I think your comment hits the mark. People now listen to their music off their phones (headphone or bluetooth speakers), or on the go in their car. Nobody sits down to a desktop to listen to music.
Don't forget about bluetooth speakers, etc where the source is your phone or laptop.
Link 0 and 2 are essentially from TBS and CDS. They coexist together. They are essentially working at the very top as entities that gather information from other departments. They can do whatever they want because they help write the rules.
I'm not trying to discredit your post, just saying that as someone who has brought OSS tools to development at the government and tried to use OSS tools for client (I failed at that), it is nearly impossible at the moment. We are married to Microsoft and its cloud.
I do agree, that it may take an entire generation because right now, 190+ departments are not exactly jumping to FOSS, and in many situations, they are down right told you are not allowed.
In addition, the current de facto document management system is from OpenText. Although many just use Sharepoint Online.
Ironically, as everything moves to the cloud, it would be easier to move to a solution that is FOSS based, and based in the cloud. Technology has matured enough that you don't need executables on a desktop, you just need a browser pointing to a website.