Ultimately, it seemed that sometime between forever that I've been lurking on thedonald to now, mcafee decided it didn't like patriots.win, beamed it to the modem software and client-side access was denied. That was the conversation I was hoping to spark, but solving my problem is a win-win for .win
Thanks fren, fixed. OpenWRT compatible router next, after the move.
I saw the same and was still using ff as my daily driver until all this happened today. It took me four hours just to get here to get this posted here on patriots.win
There is a difference between having a plan and constantly planning. Their hubris will be their downfall.
Can't lose hope. Ideally this cough administration cough will see a new resurgence in free-internet technologies.
DNS didn't solve. VPN through Brave did.
ah thank you patriot, I read too fast as I often do. Testing across Firefox, Brave, Edge, Falkon and same result. the VPN on Brave fixed it, why I am able to respond to you now. I noticed this starting to happen about 4 days after GEOTUS got ban-hammered in conjunction with Mozilla spouting off their shit and now here we are.
problem affects all browsers. it's modem side software issue
researching: its modem-based software that mcafee will blacklist and beam to the modem. it is affecting all browsers on the host. VPN ftw.
Censorship Gone Wild I also posted last night. Am noticing a significant bend on certain websites being flagged by McAfee. Solution to router problem for CenturyLink : datahog1776
I started noticing flags on some posts about GEOTUS on hangthecensors.com about 4 days after his twitter ban. Then some streaming sites, then patriots.win just recently.