Tenkian

joined 1 year ago
[–] Tenkian@lemmy.world 2 points 1 year ago

Ours is "long sausage"

[–] Tenkian@lemmy.world 1 points 1 year ago

It was a while ago, so I can't remember exactly but there is a good article here The cloudflared daemon is setup to run a standard DNS server over TCP/UDP port 53 as normal. You configure the upstream DNS to be DoT based. The clients then send DNS requests as normal to the cloudflared service and then they convert them to DoT upstream and the response is then sent back to the client as a normal DNS response.

[–] Tenkian@lemmy.world 9 points 1 year ago (5 children)

Another option you can have, install the cloudflared service on your pihole and use that as a DNS server. Cloudflared can take DNS requests from your clients and then proxy those requests over DoT to an upstream server which supports DNS over TLS. I have used Google in the past for this. I had great success with this solution inside a corporate environment which blocked port 53 to all outside the network.

[–] Tenkian@lemmy.world 3 points 1 year ago (5 children)

Can confirm. Live in Manchester. It's nearly true though, it does rain a lot.

[–] Tenkian@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

kuro@lemmy.ca Has there been any thought on adding this feature? I used to use this a lot with sync. I have some communities that I always browse with "new" and the really active ones by "hot".

 

Can we choose a default sort option per subscription? Some communities are large and I want to view by hot. For other communities, I would like to view by new. If this setting could be done on a per community basis on the ones I am subscribed to, it would be great.

 

It would be great if nsfw content can be blocked from appearing in the all/community feeds. Not blocked globally. Content should be visible if you go direct to a community which contains nsfw content.