Government IT is famously expensive, and so often a disaster. I recently needed to open an account with a local agency. The fun started with two date fields on the web form, which turned out (trial and error) to require different formats. I finally received my credentials, but they didn't work. Assuming that the password was likely the problem, I tried the password reset function, only to get a 404 error. The person…
The government probably has outsourced this to the only company which bid based on some "anti-corruption" or "fair-trading" rules which were passed. There is of course no way to hold that outsourced company to account.
The City of Seattle accidentally gave me 32M emails for $40 (2018)
51–60 of 230 posts
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#52Earlier quoted context omitted.
The author's email is at the bottom of their post if you need to reach them to tell them off about their failings from 5 years ago.
Its the author, and idk if the snide extra bit about informing them about their failings from 5 years ago makes any sense. This was posted today.
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#53What happens if he refused the lawyer request to scan his hard drive?
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#54Earlier quoted context omitted.
The dataset was so large they were probably not opening up the files before sending them over. It was clearly a rookie mistake by someone who had never had to do this stuff before and wouldn't have known what to look for. Again, the vast majority of the emails were automated alert/spam emails. So it's unclear if a random sample of the data would have turned up anything interesting to look at if you didn't know what y…
I don't agree, I think opening any of the files would have made it immediately apparent that the first 256 chars of each email were included, if that's indeed what happened as the article said.
Opening a file of that size in Excel would probably crash the desktop. And this was probably a lowly admin without a lot of other tools.
The first 256 char of a lot of system emails are going to just have junk html and header tags. If you don't understand that you are looking at HTML, it's not going to be apparent that you are looking at the body of an email.
It's a rookie mistake to be sure, but the admin was clearly unfamiliar with what was being requested.
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#55Earlier quoted context omitted.
> The job seems awful How hard can it be to do a sanity check of the metadata?
The dataset was so large they were probably not opening up the files before sending them over. It was clearly a rookie mistake by someone who had never had to do this stuff before and wouldn't have known what to look for. Again, the vast majority of the emails were automated alert/spam emails. So it's unclear if a random sample of the data would have turned up anything interesting to look at if you didn't know what y…
This isn't even to ensure my data file doesn't include something private, just to ensure that it actually includes what I intended it to, and I didn't do something dumb like put the data in the same field twice, or duplicate the same record over and over, or whatever.
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#56Earlier quoted context omitted.
In the US emails to and from government workers are generally considered public record. It's important for transparency.
I agree that government records should be open and are good for transparency. The problem comes when people don't realize that something they're doing would put all of the personal information they've submitted into the public record, or when it's required to do this to access a service. In Washington, and Seattle specifically, doing something as simple as reserving a park space or signing up for a constituent newsle…
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#57Earlier quoted context omitted.
I don't agree, I think opening any of the files would have made it immediately apparent that the first 256 chars of each email were included, if that's indeed what happened as the article said.
>Some things about the dataset: It’s very messy – triple quotes, semicolons, commas, oh my. There are a millions of systems alerts. For seattle.gov → seattle.gov communication, there are two distinct metadata records Opening a file of that size in Excel would probably crash the desktop. And this was probably a lowly admin without a lot of other tools. The first 256 char of a lot of system emails are going to just hav…
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#58Hah, that's a much simpler title. :)
How do I find more information out about FOIA requests? Also, in your post I think you mentioned "FOIA junkies" or something along those lines, this implies to me there's a community of people who understand this stuff and talk about it. That sounds really interesting to join. Is there a subreddit or something?
Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#59Re: The City of Seattle accidentally gave me 32M emails for $40 (2018)
#60Earlier quoted context omitted.
The government probably has outsourced this to the only company which bid based on some "anti-corruption" or "fair-trading" rules which were passed. There is of course no way to hold that outsourced company to account.
More like the company made the lowest bid, and their bid was intentionally lower than the actual cost of building what the agency wanted built, so they did the least work possible to get it to vaguely work, and moved on.
Probably a bit of both. I'd be very nervous about jumping through the hoops that come with supplying to government -- hoops the people working in the government don't want, but ones that have been put in by politicians for various reasons.