AdGuardHome VS flood

Also AdGuardhome will use optimistic caching, which is great.

https://github.com/AdguardTeam/AdGuardHome/discussions/4002#...

The main repo is GPLv3: https://github.com/AdguardTeam/AdGuardHome

They already have many other commercials products and I guess also the default filter rules are very good because of their experience in the domain.

But I think you can use it completely without the AdGuard servers and use other filter list sources.

How it compares to let's say AdGuard Home? Seems similar https://github.com/AdguardTeam/AdGuardHome

Adguardhome - Clients identification issue

You can check this documentation if you want to investigate further: https://github.com/AdguardTeam/AdGuardHome/wiki/Hosts-Blocklists

I'm using adguardhome v0.107.42 openwrt snapshot on linksys wrt1900ac v2, but when using DoH it won't resolve upstream DNS, but DoT is works perfectly OK, I've already set allow_unencrypted_doh to true in config .yaml file as per instruction here

AdGuard Home?

https://github.com/AdguardTeam/AdGuardHome

Regarding open source, AdGuard DNS actually is:

How does this compare to adguard home [ https://github.com/AdguardTeam/AdguardHome ] ??

Have you looked at AdGuard Home - Configuring clients?

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood