We release APK files into our github as well as in another mirror. Check here: https://github.com/ecency/ecency-mobile/releases
We will check F-Droid listing requirements.
You are viewing a single comment's thread from:
We release APK files into our github as well as in another mirror. Check here: https://github.com/ecency/ecency-mobile/releases
We will check F-Droid listing requirements.
Github didn't have the 3.0.3 release when I looked prior to 3.0.4's release, so I figured it wasn't very well maintained there.
Aside from that, do you know of any bugs that would cause images not to load?
My guess is that you're using Cloudflare, it's the number one cause of issues like this that I've seen. If so could you consider adding an exception for the T1 region in your Cloudflare dashboard to prevent Tor users from getting nothing when loading images? Alternatively, try to find someone other than Cloudflare to use as a CDN, as Cloudflare is not very privacy friendly.
Right, we forgot to release 3.0.3 version but added latest one after your request. Images are not cached by cloudflare, I just opened https://ecency.com with Tor and it is loading images just fine. 🤔
Does your mobile app function with Orbot's "VPN" mode enabled for you? Cloudflare can be very fickle with different user agents and may allow a standard web browser while blocking a mobile app. Also, if you were greeted with Cloudflare's "Checking your browser" screen even once, than that would be indicative that any request without Javascript would be blocked, such as images within an app.
There are two ways to resolve such issues, at least without major changes, doing both would fix almost all instances of Cloudflare blocking requests. The first is to prompt users in the app to solve the Cloudflare CAPTCHA if all images are served with a 403/Forbidden code. The second is to manually allow Tor and/or lower cloudflare's "Security" level so they block fewer requests. Cloudflare's region code for Tor is T1
The bandwidth capacity of Tor is relatively low so manually allowing it shouldn't pose much risk of something like a DDoS attack occurring.
There is another way to resolve this, which would take major changes but would provide a smoother and more secure experience for users. That would be integrating Tor support directly into your apps and running your own Tor hidden services. This would also ensure there are no middlemen like Cloudflare that can snoop on any connections or track your users.
On a side note, I have been considering setting up a Tor accessible Witness/API node myself as I have not yet seen one available for Hive.