Meh, is #CloudFlare lying or is my ISP playing on me?
romain@zappy ~ % dig +short @1.1.1.1 archive.fo
127.0.0.3
romain@zappy ~ % dig +short @8.8.8.8 archive.fo
51.15.97.128
Meh, is #CloudFlare lying or is my ISP playing on me?
romain@zappy ~ % dig +short @1.1.1.1 archive.fo
127.0.0.3
romain@zappy ~ % dig +short @8.8.8.8 archive.fo
51.15.97.128
Oh, #Cloudflare was having issues and brought a lot of websites down with it? That's not great.
But thankfully it's not that hard to roll out your own "DDoS protection" (or caching; just call it caching) setup. Here, you can even use our configs: https://git.occrp.org/libre/fasada
Yes, we use them in production, serving sometimes hundreds of thousands views per day.
Patches welcome. #SysAdmin
List of affected #Cloudflare regions 🤔
"Mastodon server test result"
[2019-04-04]
There are 236 (0) Cloudflared #Mastodon on the internet.
Do you want to share your private message with #Cloudflare ?
#TheGreatCloudwall #privacy #Pleroma #fediverse
List: https://searxes.danwin1210.me/#!list=mdsvrs
#Cloudflare is blocking me again. Asks me to tackle a challenge that requires #javascript to get past, basically making my surfing a lot less convenient, far less secure, and making the Web a much more dangerous place. Webmasters, boycott CF.
How Right-Wing Social Media Site #Gab Got Back Online
https://www.wired.com/story/how-right-wing-social-media-site-gab-got-back-online/
(The ironic thing? as soon as the #nazis move to decentralized social media, they won't need corporate sponsorship)
Wait, what. #CloudFlare introduces its own onion service and it doesn't look terribly bad:
https://blog.cloudflare.com/cloudflare-onion-service/
Also of note, HTTP Alternative Services now supported by the Tor Browser:
https://tools.ietf.org/html/rfc7838
#Mozilla will change the way your #Firefox looks up DNS records. They say it's to protect your privacy and thats even somehow true. They announced two different ways to handle DNS lookups:
The first one is DoH (DNS over HTTPS) wich makes a lot of sense, since it just encrypts the DNS lookups.
The other one is TRR (Trusted Recursive Resolver) & involves sending all Firefox users' DNS lookups to a private, US based tech firm: #Cloudflare.
Here's why this is a bad idea:
https://blog.ungleich.ch/en-us/cms/blog/2018/08/04/mozillas-new-dns-resolution-is-dangerous/
For anyone else hyperventilating at the #Firefox testing of the new #IETF standard recommendation: #DoH
You might like to hear about options to still use DoH and NOT #Cloudflare #Mozilla is not about to introduce a Single Point of Failure. It's testing a new standard via one of the early adopting DNS providers.
Anyways, here's a list of alternative DoH end-points! https://github.com/curl/curl/wiki/DNS-over-HTTPS#publicly-available-servers
Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.
All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.