"Nathan Freitas (GP) via guardian-dev" <[email protected]> writes:
> For sure, we are still here. Most of our chat has moved over to our > Matrix chat rooms, but we shouldn't ignore email after all. Glad to hear it! > What is the issue you are having? There is some know issue if you have > the DNS cache enabled. We recently migrated some of our mirrors and > somehow that feature gets in the way. For a long time (several months), I would get timeouts when checking the guardian project repo, and occasionally it would work. Then, trying to update Tor Browser would just result in timeout. I'm using the normal/longstanding f-droid client and have not been trying to enable any extra dns caching (beyond what's built in to the protocol of course). I just checked and 'use dns cache was enabled'. It never occured to me that a 'cache' would keep data for more than a week; that feels like 'pinning' not 'caching'. I turned if off because it seems buggy. It's super buggy if one moved mirror messes up trying the rest of them; I'd expect one working mirror and the rest messed up to be good enough. My network has a local named with a pretty vanilla config. I deleted the repo and re-added it, and now things are working better. I got a new copy of the metadata and that showed an update for orbot, which I did, and that worked. The update to TB seemed flaky but it is now showing as completed, and I think that's likely mostly a longstanding f-droid client bug, where the update happens but the "updating" notification doesn't go away and the UI still acts like an update is needed. But that happens a lot with others. So I think I'm fixed now. Thanks for letting me know it is believed working for others and the hint. _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
