Hacker News Reader

Comment by gw | Hacker News Reader

Once you've bootstrapped/integrated with the network, it takes a minute or two for a new update to reach you in my testing. The initial time to bootstrap onto the network is around five minutes.

The traffic consumption is pretty high, because it becomes a full peer on the I2P network. Over a month I would expect it to consume around 1GB or more. If this becomes an issue for people, I may add the ability to be a non-contributing peer.

View on HN

I think a setting to only use WiFi would be valuable for a lot of users.

You might want to add a status text to the service notification, displaying how far bootstrapping is..

Please make the non-contributing status the default then, or at least ask the user on installation... capped data plans are still the default in many places... :(

Do android applications have access to their amount of data used? Maybe it would be possible to cap the data usage or lower the bandwith when a limit is reached.

Definitely agree with the option to become non-contributing, or at least introduce some limiting - it's a struggle to get a data cap of higher than 500MB here. Speed doesn't seem too bad, even on 2 year old hardware. Is there an (easy) method for transferring your key to another device, and conversely if there is such a way, is there anything to protect the file if someone was to get access to the device storage?

Yep I already added data export. Just click your profile and there is a button called "Export..." which will ask for a password and create an encrypted zip file.

Does this allow for two devices to be "logged in" to the same profile, or will one become the primary while the other can't assume control at all?

It might make more sense to switch between the type of peer based on the type of network connection. If the phone is currently connected to wifi, then run as a contributing peer. If the phone is only on 3G/4G/LTE/etc then switch to being a non-contributing peer.

Reply on news.ycombinator.com