The lawyer for one of them doesn’t seem to think this will have any effect. If that’s the case, surely jail would have been a better option?
The lawyer for one of them doesn’t seem to think this will have any effect.
“I doubt the church will see a dime,” Norm Pattis, counsel for Mr. Biggs, said in an email. “None of the defendants appeared to contest the case,” he added. “I don’t think anyone is losing any sleep over this.”
If that’s the case, surely jail would have been a better option?
Thank you but I have had three different browsers, chrome, edge and firefox refuse to open it because it is supposedly not a 'secure link'. Do you have any advice?
Thank you but I have had three different browsers, chrome, edge and firefox refuse to open it because it is supposedly not a 'secure link'. Do you have any advice?
Hmm. Strange. It works fine in all three of those browsers for me. But as an alternative, the Internet Archive also has a snapshot of the article, which may work better for you.
Hmm. Strange. It works fine in all three of those browsers for me. But as an alternative, the Internet Archive also has a snapshot of the article, which may work better for you.
That worked. Thank you. I'm not sure what the deal was. Re the article, I am happy to learn that the destruction was only of a sign. It's not good that they did it, but actual church burnings have...
That worked. Thank you. I'm not sure what the deal was.
Re the article, I am happy to learn that the destruction was only of a sign. It's not good that they did it, but actual church burnings have been known to happen to show racial hatred in the past.
Their SSL cert is valid and hasn't expired, so I'm not sure what the issue is either. You could try clearing your browsers' caches to see if that helps, but given it failed on all 3 of your...
Their SSL cert is valid and hasn't expired, so I'm not sure what the issue is either. You could try clearing your browsers' caches to see if that helps, but given it failed on all 3 of your browsers, that seems unlikely.
I was also getting a secure connection error on iOS Safari that persisted even after clearing my cache. I turned on my VPN (which I hadn’t realized had been turned off) and it worked. If I turn...
I was also getting a secure connection error on iOS Safari that persisted even after clearing my cache. I turned on my VPN (which I hadn’t realized had been turned off) and it worked.
If I turn off the VPN and clear my cache, it doesn’t work again. I also tried it with Firefox iOS to the same effect.
I'm not able to on my phone (that I know of?), but I did a DNS query from my laptop and it looks fine. My router is actually using NextDNS, so the ISP shouldn't be hijacking it even from my phone...
I'm not able to on my phone (that I know of?), but I did a DNS query from my laptop and it looks fine. My router is actually using NextDNS, so the ISP shouldn't be hijacking it even from my phone (which is connected to the router).
In playing around with different settings and digging deeper, and it looks like the culprit might be iCloud's Private Relay. When I turn that off, the site loads fine. When I turn it back on, I get the same secure connection error. From what I understand (which is admittedly very little -- I'm way out of my depth on all of this) a VPN and Relay don't work together, so it makes sense that when I turn on my VPN, it stops going through Relay, which is why it's working in that case. This is all uninformed supposition on my part though, so, grain of salt.
Also, what's weird is that, based on the browsers @boxer_dogs_dance listed, I'm assuming they're not using iCloud Private Relay? So maybe there's more to this story.
The short answer is that archive.is blocks Cloudflare's DNS resolver (1.1.1.1), which might be what iCloud Private Relay is using (or it might be using another DNS resolver that hides your...
The short answer is that archive.is blocks Cloudflare's DNS resolver (1.1.1.1), which might be what iCloud Private Relay is using (or it might be using another DNS resolver that hides your location for privacy reasons). archive.is's owner disapproves of services that don't send the location data, so its DNS servers send invalid responses instead.
The lawyer for one of them doesn’t seem to think this will have any effect.
If that’s the case, surely jail would have been a better option?
This was a civil case against the Proud Boys organization, not a criminal trial against the specific perpetrators.
Mirror for those hit by the paywall:
https://archive.is/DxNIY
Thank you but I have had three different browsers, chrome, edge and firefox refuse to open it because it is supposedly not a 'secure link'. Do you have any advice?
Hmm. Strange. It works fine in all three of those browsers for me. But as an alternative, the Internet Archive also has a snapshot of the article, which may work better for you.
That worked. Thank you. I'm not sure what the deal was.
Re the article, I am happy to learn that the destruction was only of a sign. It's not good that they did it, but actual church burnings have been known to happen to show racial hatred in the past.
Their SSL cert is valid and hasn't expired, so I'm not sure what the issue is either. You could try clearing your browsers' caches to see if that helps, but given it failed on all 3 of your browsers, that seems unlikely.
I was also getting a secure connection error on iOS Safari that persisted even after clearing my cache. I turned on my VPN (which I hadn’t realized had been turned off) and it worked.
If I turn off the VPN and clear my cache, it doesn’t work again. I also tried it with Firefox iOS to the same effect.
I'm not able to on my phone (that I know of?), but I did a DNS query from my laptop and it looks fine. My router is actually using NextDNS, so the ISP shouldn't be hijacking it even from my phone (which is connected to the router).
In playing around with different settings and digging deeper, and it looks like the culprit might be iCloud's Private Relay. When I turn that off, the site loads fine. When I turn it back on, I get the same secure connection error. From what I understand (which is admittedly very little -- I'm way out of my depth on all of this) a VPN and Relay don't work together, so it makes sense that when I turn on my VPN, it stops going through Relay, which is why it's working in that case. This is all uninformed supposition on my part though, so, grain of salt.
Also, what's weird is that, based on the browsers @boxer_dogs_dance listed, I'm assuming they're not using iCloud Private Relay? So maybe there's more to this story.
The short answer is that archive.is blocks Cloudflare's DNS resolver (1.1.1.1), which might be what iCloud Private Relay is using (or it might be using another DNS resolver that hides your location for privacy reasons). archive.is's owner disapproves of services that don't send the location data, so its DNS servers send invalid responses instead.
Here's a good article summarizing the issue (from 2019)