Depends on your threat model. If you use secure DNS and https for the RSS feed, then these people would know your IP and the IP you’re connecting to:
Your ISP or VPN will know you’ve made a TCP connection to that server at a specified port, but that’s it. It’s trivial for them to reverse lookup the IP back into a name.
Only the RSS server will know the specific URL you’re visiting though.
Take a look at trusted computing. The issue is someone modifying your software to collect more data than you intend, right? Make it so stock versions can’t talk to modified versions. This involves a fair bit of cryptography that goes way above my head. But for a technical solution, that’s where I’d start to look at.
For the time being, offer it exclusively as SaaS, while you figure out a game plan to solve this conundrum.
It’s ergonomics, yes. I like to use the phone one handed. With a big screen you have to adjust (scoot up and down) all the time, leading to falls (of the phone) and fatigue on the hand.
I’m concerned the pop socket would make it harder to stick my phone in my jeans. I know it’s retractable, maybe I could give it a go if I didn’t find a small phone.
OP specifically stated to prep a specific web client and instance, and create a QR code to facilitate joining. That sidesteps that concern entirely.
That was how I joined IRC back in the day. I was told to join “mIRC” (a popular client then). You figure the details later — or don’t, because it will work regardless.
Linger on*