dnscrypt-proxy
Synapse
Our great sponsors
dnscrypt-proxy | Synapse | |
---|---|---|
163 | 367 | |
10,912 | 11,720 | |
1.1% | - | |
8.4 | 9.8 | |
5 days ago | 4 months ago | |
Go | Python | |
ISC License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dnscrypt-proxy
-
What to do with your DNS when ODoH's Trust-Me-Bruh Model doesn't work for you
There is more than one way to do this but I have decided to use dnscrypt-proxy. We will not be using dnscrypt for the dnscrypt protocol though you could elect to use that as the underlying DNS protocol. dnscrypt-proxy lets's us use a SOCKS5 proxy through which the DNS queries will be sent. We will use a Tor SOCKS5 proxy here. You can choose which protocols should be enabled and which ones should be disabled. There are two points:
-
Installing DNSCrypt-Proxy on Silverblue - possible SELinux issue
I tried installing the RPM from the Fedora repos but it's out-of-date and there were no instructions on how to get it operational, so I went with the manual approach as per their wiki: https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation-linux
-
SmartDNS – local DNS server that forwards to multiple upstream DNS servers
This is awesome, thanks -- going to look into that now. I found SmartDNS interesting and thought I would share it, it's pretty simple to setup. I can see why it's Chinese focused, they have "interesting" internet access over there :-).
I have been looking into DNS quite a bit lately (Unbound, etc), as DNS lookup performance has been pretty subpar lately. I'm in Perth, Australia, and we're pretty remote so our latency is meh at best, and Cloudflare performance has been all over the shop lately, I think they're having issues in WA). DNS can also cause really routing issues here sometimes as we get better latency to Singapore than Sydney, so we might get shunted off to SG.
I've also been using dnscrypt-proxy2 (https://github.com/DNSCrypt/dnscrypt-proxy) for a while, but the above issues with Cloudflares DNS is what triggered me to look into other options.
I use a min-cache-ttl of 15 minutes, which seems to work well.
Thank you for sharing this tip about, looking into this now :).
- I need help with DNScrypt proxy v2 and dnsmasq to prevent dns leaks
- trying to use Anonymized DNS with DNScrypty proxy v2 on openwrt router
- help with DNScrypt proxy v2 and dnsmasq to prevent dns leaks
-
Is using tailscale on a public unsecured wifi as safe as using a VPN?
Sure. I run dnscrypt_proxy behind a pihole. https://github.com/DNSCrypt/dnscrypt-proxy
- TotalPlay intercepta las peticiones de DNS y las suplanta.
- Dnscrypt-proxy package need to update
Synapse
-
Organizing OpenStreetMap Mapping Parties
What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.
Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).
If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.
-
GrapheneOS is moving off Matrix
some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...
-
Non-profit Matrix.org Foundation seems to be moving funds to for-profit Element
Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.
This is honestly really disappointing behaviour from a platform owner.
-
The Future of Synapse and Dendrite
> That doesn't make this situation any less bad to the rest of the community.
How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.
You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.
And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.
The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.
[0]: https://github.com/matrix-org/synapse/graphs/contributors
- Synapse v1.95.0 Released
- Matrix Synapse how use python scripts?
- Synapse v1.91.2 Released
- Synapse v1.89.0 is out
- Synapse v1.88.0 is out
- Synapse v1.87.0 (Matrix Server) Released
What are some alternatives?
GoodbyeDPI - GoodbyeDPI — Deep Packet Inspection circumvention utility (for Windows)
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
cloudflared - Cloudflare Tunnel client (formerly Argo Tunnel)
conduit
nextdns - NextDNS CLI client (DoH Proxy)
Rocket.Chat - The communications platform that puts data protection first.
DNS-over-HTTPS - An implementation of RFC 8484 - DNS Queries over HTTPS (DoH).
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
shift-rmm
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
udm-utilities - A collection of enhancements for UnifiOS based devices [Moved to: https://github.com/unifi-utilities/unifios-utilities]
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker