EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

01.20.20

Mansion of Pedophilia – Addendum: Progress on Police Request

Posted in Bill Gates at 2:52 am by Dr. Roy Schestowitz

“Due the heavy workloads and shortage of staff, the Department needs additional time to complete an installment.” –Seattle PD, November 14th

You drove too fast. Do you know who my dad is? I will check.
Sometimes connections help

Summary: 9 updates from the police department of Seattle but still nothing material/concrete, only promises and major delays

There are numerous ongoing requests (different accounts, albeit similar requests) with the Seattle Police Department (SPD or SPPD). There might even be more on the way, but additional requests would slow down an already-slow process. The pertinent details probably merit an addendum or a few addenda.

“We don’t want to speculate about causes for delay or about sincerity, at least not at this point.”One person who put in a request has just shared recent updates from the SPD. They send similar/identical messages to all requesters. “NAMELY LIBERTY will be publishing all correspondence from SPD related to this request in due time. Stay tuned,” it said, “watch for future updates.”

The introduction says this: “It’s been nearly 5 years now, since Rick Allen Jones was convicted, and these documents seem to have been completely ignored by media. While the Seattle Police Department has been responsive to this request, to date, they have not produced any of the above requested items. In the several status updates they have sent, related to this request, confirmed there to be “over 2000 pages” and that attempting to download the report, at even 1/4 at a time, has caused their system to crash.”

We saw the same updates. We don’t want to speculate about causes for delay or about sincerity, at least not at this point.

“The Three Most Recent Communications From Seattle Police Department,” the site said, are as follows.

December 5, 2019 – SPD sent the following:

Good morning,

I’ve been trying to download the requested report all morning, every time it crashes my system. This report is over 2000 plus pages. I’ve even tried taking 1/4 at a time. It’s still taking forever.

I will need to speak with my supervisor with ideas of getting you this report. I will need to push this request out again. I don’t know how long it will take, but you will hear back from me tomorrow.

I appreciate your patience.

S. Hurst, Seattle Police Department, Legal Unit

December 12, 2019 – SPD sent the following:

The purpose of this communication is to provide a status update regarding your request.

The Seattle Police Department needs additional time to respond to your request due to the following:

*** The report has finally downloaded, and is being reviewed for any redaction’s ***

At this time, we anticipate having a response/installment to you on or about 1/8/2020.

S. Hurst, Seattle Police Department, Legal Unit

January 9, 2020 – SPD sent their most recent update:

The purpose of this email is to provide you with a status update. We are having technical problems with trying to process your request, because this report is over 2000 pages it keeps trashing on us. We are trying to figure out how it get this processed. At this time, we anticipate getting back to you on or about February 17, 2020.

S. Hurst, Seattle Police Department, Legal Unit

Based on public pages such as these from MuckRock, Sauncy Hurst works for the “Seattle Police Department” in the “Public Disclosure Unit”. The style is consistent and the name is already in the public record. So we doubt privacy is being compromised here.

This did not start with Seattle’s PD though. Correspondence record/timeline which was shared with us included: (notice how they discuss redactions whilst also claiming to have issues opening the file):

  • September 13, 2019 – Written request made to King County Sheriff’s Office: “Request is made for the following public records regarding criminal case # 14-1-06789-1: 1. Full police report. 2. Search warrant application and affidavit. 3. CAD report. 4. All transcripts/audio recordings/statements from defendant and witnesses related to this case. 5. Property/Evidence Report.”
  • September 13, 2019 – Received email from Sakilyne Kally | Functional Analyst II | Public Disclosure Unit – Subject: Public Disclosure Request Reference #P039465-091319. Message: “Using the information provided, the KCSO Disclosure Unit has determined that the incident you are referring to occurred outside the jurisdiction of the KCSO. We suggest you contact Seattle Police for records that may be responsive to your request. You may reach them at (206) 684-5481. Your request is now closed.”
  • September 13, 2019 – Submitted same written request to City of Seattle Public Records Request Center. Included additional optional fields for reference: “Incident Number: 14-1-06789-1. Incident Date: March 20, 2014.”
  • September 13, 2019 – Request received by SPPD, reference number is P047691-091319. City of Seattle Public Records Request Center user account created and confirmed by email.
  • September 16, 2019 – Status update received. “Your request status is: Assigned.”
  • September 19, 2019 – Email from Sauncy Hurst, Seattle Police Department Public Disclosure Unit: “Are you involved in this incident? If you are please provide your date of birth to make sure we locate the correct incident.” My only response, same day, was, “No.”
  • September 19, 2019 – Email received with: “Your request status is: Being Researched/Reviewed.”
  • September 19, 2019 – Email received from Sauncy Hurst: “Pursuant to RCW 42.56.520, this is notification that the Seattle Police Department has received your public disclosure records request and needs additional time to respond. At this time, we anticipate having a response or a status update to you on or about 10/22/2019. We are initiating the process of researching your request, collecting responsive records, and/or preparing records for dissemination.
  • October 22, 2019 – Received status update email from Sauncy Hurst: “The Seattle Police Department needs additional time to respond to your request due to the following: Records are currently being reviewed for redactions At this time, we anticipate having a response/installment to you on or about 11/13/2019.”
  • November 14, 2019 – Received status update email from Sauncy Hurst: “Due the heavy workloads and shortage of staff, the Department needs additional time to complete an installment. At this time, we anticipate getting back to you on or about December 4, 2019.”
  • December 4, 2019 – Received status update email from Sauncy Hurst: “I’ve been trying to download the requested report all morning, every time it crashes my system. This report is over 2000 plus pages. I’ve even tried taking 1/4 at a time. It’s still taking forever. I will need to speak with my supervisor with ideas of getting you this report. I will need to push this request out again. I don’t know how long it will take, but you will hear back from me tomorrow. I appreciate your patience.”

Further updates are already out there, quoted at the top. And yes, there’s some communication among petitioners. Coordination? No. But communication. It’s important to advance the request, even if not all stakeholders share the same views/positions/motivations. The public needs and definitely deserves to know what happened there. Nobody is above the law. Or maybe…

“This might be “strategic delaying” (giving you the mere impression of progress while never intending to make any).”File splitting, I might add, is very simple. It should not be hard to process such a request. I assume they use something from Microsoft, possibly even hosted by Microsoft (on a so-called ‘cloud’). They might be using Microsoft tools and maybe Microsoft hosting. If it’s them who saved these files in the first place, can’t they open their own files? Was there tampering? We don’t know and we don’t want to guess. No police department can hold a company accountable if that company controls that department’s IT facilities. That much should be obvious…

In terms of the dates, we all need to wait another month or so. This might be “strategic delaying” (giving you the mere impression of progress while never intending to make any). We’re meanwhile also advancing on the other front: court documents. We’ll post details separately in the next addendum.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. Links 28/3/2020: Wine 5.5 Released, EasyPup 2.2.14, WordPress 5.4 RC5 and End of Truthdig

    Links for the day



  2. IRC Proceedings: Friday, March 27, 2020

    IRC logs for Friday, March 27, 2020



  3. The Fall of the UPC - Part VIII: Team UPC Celebrates Death, Not Life

    Team UPC plays psychological games now; it is trying to twist or spin its defeat as good news and something to be almost celebrated; it is really as illogical (and pathetic) as that sounds



  4. Links 27/3/2020: GNU/Linux Versus COVID-19 and Release of GNU Guile 3.0.2

    Links for the day



  5. When Your 'Business' is Just 'Patent Portfolio'

    Hoarding loads of patents may seem impressive, but eating them to survive is impossible if not impermissible



  6. LOT Network is a One-Man (Millionaire's) Operation and Why This Should Alarm You

    The ugly story of Open Invention Network (OIN) and LOT; today we take a closer look at LOT and highlight a pattern of 'cross-pollination' (people in both OIN and LOT, even at the same time)



  7. Faking Production With Fake Patents on Software

    The EPO with its illegal guidelines (in violation of the EPC) can carry on churning out millions of fake patents that European courts would only waste time on and small companies be blackmailed with (they cannot afford legal battles)



  8. With the Unified Patent Court (UPC) Out of the Way Focus Will Return to EPO Corruption

    Expect the European Patent Office (EPO) to receive more negative attention now that the ’cause’ of UPC is lost and there’s no point pretending things are rosy



  9. IRC Proceedings: Thursday, March 26, 2020

    IRC logs for Thursday, March 26, 2020



  10. Links 27/3/2020: qBittorrent 4.2.2, Krita 4.2.9, pfSense 2.4, Bodhi Linux 5

    Links for the day



  11. IRC Proceedings: Wednesday, March 25, 2020

    IRC logs for Wednesday, March 25, 2020



  12. Still Work in Progress: Getting Those 2,851 Pages of Police Report About Arrest for Pedophilia in Home of Bill Gates

    It’s extremely difficult to get those police records, which were requested exactly one day before the media started attacking Richard Stallman (associating him with pedophiles based on a deliberate distortion)



  13. Links 26/3/2020: Plasma Bigscreen, New Kubernetes, Fedora's New Identity and Bodhi Linux 5.1.0

    Links for the day



  14. Guest Article: Window Managers, Github and Software Disobedience

    "Walking away from monopolies is the essence of freedom"



  15. Links 25/3/2020: LLVM 10.0.0 and UCS 4.4-4 Released, WordPress 5.4 RC4

    Links for the day



  16. 'Team UPC' Last Week

    The looks on Team UPC's faces 5 days ago (before and after the 9:30AM announcement)



  17. The Fall of the UPC - Part VII: Lies and Revisionism About the Reasons for the UPC's Ultimate Demise (to Leave the Door Open for More Failed Attempts)

    The media was lying in a hurry, in a coordinated effort to distort the meaning of the FCC's decision or belittle the impact of this decision; Techrights will carefully watch and respond to these lies



  18. IRC Proceedings: Tuesday, March 24, 2020

    IRC logs for Tuesday, March 24, 2020



  19. Linux Foundation Became Anti-Linux, Run by Microsoft People to Serve Microsoft's Agenda

    Microsoft is taking over the bodies of healthy projects, infecting the hosts in order for them to become slaves of the proprietary parasite; there's still no (known) cure, but we're familiar with the symptoms



  20. Microsoft Continues to Attack and Steal From the Open Source/Free Software Communities

    Microsoft cannot be trusted and there's no "new Microsoft," as another fairly new story serves to show



  21. Targeted Attack Leveraging FSF Servers

    Targeted by a determined and persist perpetrator, I've received over 20,000 E-mails. And the weapon of choice was the FSF's infrastructure, remotely misused against yours truly.



  22. If We Weren't Silencing Founders, Critics and People We Just Don't Like

    "In the long run, history is rarely very kind to tyrants, especially the ones who did little more than lie to people and demand things that served no real purpose."



  23. The Fall of the UPC - Part VI: Drowning in Material

    We're starting to see few good reports on the subject of UPC being rejected by the constitutional court of Germany; we also have a rapidly-growing 'buffer' of rather blatant examples of disinformation (which we'll tackle as best we can)



  24. FFII: EU Software Patent Court Stopped by Constitutional Court, Patent Industry Will Try Again

    The third attempt to validate software patents in Europe via a central patent court (UPC) has been stopped by the German Constitutional Court. The Unified Patent Court (UPC) would have given the keys of the kingdoms to the patent industry, and the last word over software patentability. FFII predict that the patent industry will continue to push for an UPC v2.0.



  25. Links 24/3/2020: Alpine 3.11.5, MythTV 31.0 and Tails 4.4.1

    Links for the day



  26. IRC Proceedings: Monday, March 23, 2020

    IRC logs for Monday, March 23, 2020



  27. Links 23/3/2020: Linux 5.6 RC7, Audacious 4.0, and Git 2.26 Released

    Links for the day



  28. The Fall of the UPC - Part V: Pretending That Opponents of the Unitary Patent Simply Don't Exist

    It's difficult if not totally impossible to find articles from impartial journalists -- let alone from actual scientists -- about the failure of the Unitary Patent and UPC Agreement (UPCA)



  29. The Fall of the UPC - Part IV: IP Kat Became Just a Team UPC Megaphone

    Willem Hoyng (Drafting Committee of the UPC's Rules of Procedure) is 'writing' IP Kat right now; has the blog turned into the very thing it fought to expose?



  30. The Fall of the UPC - Part III: Pure Comedy From Watchtroll and Its UPC Lobbyists From Managing IP

    Two megaphones of European Patent Office (EPO) management and boosters of Team Battistelli, namely Managing IP and Watchtroll, want us to think that UPC is merely “delayed” and that acts of overt corruption can be described as “passed unanimously by the Second Chamber of the Bundestag”


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts