Everything Sad Is Untrue Epub

0 views

Skip to first unread message

Edward

unread,

Aug 3, 2024, 4:14:36 PM8/3/24

to hattyveme

Conspiracy theories might get new life in the age of the internet, but as long as there has been the possibility of conspiracy, there have been conspiracy theories. What motivates otherwise rational human beings to suspend logic and indulge in ideas that to everyone else seem rather far-fetched?

Today, we seek out our own experts. We can read the first few results in Google (which probably ended up so near the top because they paid for the space), or scan articles posted by others on social media, or rely on email newsletters or podcasts. Before, the news was curated for us from the same few trusted sources; today we choose our news, based not only on ease but on ideological assumptions and biases.

This is not altogether bad. There are some real benefits to the deregulation of news. Stories that might have been ignored in a previous era because of certain biases of the mainstream media networks now get coverage. And yet the danger is that because we self-sort and find our information based on our political ideology, we can be extremely susceptible to believing what is untrue.

Third, there is an impulse, especially among Christians, to distrust the media or any source of news. Too often mainstream journalists seem to have a bias against Christians in the way they cover religion or in the stories they emphasize. Too often media outlets highlight the craziest conservative, no matter how obscure, as an avatar for the whole movement while being hesitant to cover scandals that make liberals look bad. Still, we should admit that our willingness to entertain the outrageous and untrue is, in part, due to the fact that we want these stories to be true.

Conspiracy theories, by contrast, are frustrating precisely because they are so intricate. Each rejoinder or contradiction only produces a more complicated theory. Conspiracy theorists manipulate all tangible evidence to fit their explanation, but worse, they will also point to the absence of evidence as even stronger confirmation. After all, what better sign of a really effective conspiracy is there than a complete lack of any trace that the conspiracy exists? Facts, the absence of facts, contradictory facts: everything is proof. Nothing can ever challenge the underlying belief.5

Thankfully, he was stopped before he could commit real violence. But #pizzagate was not just harmless internet chatter. Nor is the growing movement of white nationalist ideology that is fueled by dangerous conspiracy theories that see people of color as societal problems. A young man from Plano, Texas, indulged these fantasies so much that he murdered twenty-two people in an El Paso Wal-Mart in cold blood. And the rise in Holocaust denial has often led to violence against Jewish people around the world.

The dots, for us, have been connected. And Jesus, the victor, has triumphed over the enemy. So while we participate with him in renewing and restoring the world, we can rejoice when evil is exposed without indulging dark and false fantasies.

In doing so, we may not convince our conspiracy-loving uncle at Thanksgiving, but our pursuit of truth can set an example that might push back against lies and our public witness might point people to the end of our pursuit of knowledge: Jesus, the wisdom of God.

Cookies enable you to enjoy features such as social sharing. They also help us analyze general site traffic so we can improve the website for everyone. By continuing to use the 9M website, you consent to the use of cookies. More information is available on our Privacy Policy.

I'm trying to export a text document in the Documents directory and running into file permission problem in a Mac app that does not use the App Sandbox. As a workaround for the issue, I tried turning on the App Sandbox and giving read/write access to the Documents directory, but when I add the App Sandbox capability, I have the following entries for file access:

Since the file is a text file, exporting to any of the folders in the list makes no sense. If I give User Selected File read/write access, I still get file permission errors when I export. The UI in Xcode provides no way to add folders to the File Access list.

I'm developing a SwiftUI app. I was using SwiftUI's file exporter to export the document. I took robnotyou's suggestion to use NSSavePanel, but I still get the file permission error, with or without the App Sandbox. I get the following message in Xcode's console:

I'm running macOS 11.5.2. If I open the Privacy preferences in System Preferences and select Files and Folders, I can see that some previous apps I developed appear in the list and have a checkbox selected that grants the app access to the Documents folder. The list of apps has an Add button, but it's disabled.

I tried giving this app full disk access and adding it to the Developer Tools list of apps that can run software locally that does not meet the system's security policy. But the file permission error persists.

I'm exporting the file in a folder inside the Documents directory. The file has read/write access for my user account and my group. The Documents folder has custom access when I get info on the folder in the file.

No, just that you have to use the right API to find the correct place to put your temporary. Specifically, see the discussion of .itemReplacementDirectory in the url(for:in:appropriateFor:create:) docs.

What I am trying to do is export a collection of Markdown files into an EPUB book. To create the EPUB book I start by creating a file wrapper that has everything the EPUB needs. I finish by using the ZIPFoundation framework to compress the file wrapper into a valid EPUB/Zip archive.

This error occurs both with the SwiftUI file exporter and NSSavePanel. The only way I can get the error message to go away is to turn on the App Sandbox, give the Downloads folder read/write access, and export my books in the Downloads folder.

When I write the file wrapper to disk, I can't write the wrapper at the location variable's URL because location is the destination for creating the book's Zip archive. I have to temporarily create the file wrapper with a different file name than MyBook.epub.

Does this mean my creating the temporary file wrapper is forbidden in the App Sandbox? For now I can avoid using the App Sandbox, but these permission errors also occur with the App Sandbox turned off.

The material in the url(for:in:appropriateFor:create:) docs provided the solution. The file permission problem was caused by the temporary file wrapper being in the same folder as the published book, The solution is to create a temporary directory for the file wrapper. Here's the code for anyone else who may have the same problem in the future.