4 ms·

Interesting! Do you plan a less nerdy user interface? I'm afraid to say so, but a mobile phone app could be a game changer. (Yes, it would drain the battery, an

by ktpsns 8y ago

Interesting! Do you plan a less nerdy user interface? I'm afraid to say so, but a mobile phone app could be a game changer. (Yes, it would drain the battery, and yes, it could run on an old phone because many people have them in their shelves)

realcr 8y ago
> Do you plan a less nerdy user interface? Yes! I agree with you, having Offst on a mobile phone is indeed a game changer. Offst was designed from the beginning to work in environments where sudden malfunctions and network problems can occur. Having it on a mobile phone is part of the plan. I began with a command line interface (stctrl, the first Offst application) because I knew I could finish developing it very quickly. I hope to take a period of time to stabilize the protocol and all the APIs, and then I will begin writing a GUI interface for Offst. Offst is written in Rust, I have no idea yet how to get it inside a mobile phone. I don't have any mobile experience at all, it will take some research on my side. > it would drain the battery Maybe not so much? Offst doesn't do any kind of CPU intensive operation. Maybe the communication will drain some battery though.
- hopscotch 8y ago
  When I last did mobile stuff, waking the radio was more expensive than many CPU ops.
  - realcr 8y ago
    We just have to hope that I until I manage to set up a nice UI for mobile phones, we will already have very good batteries (;
    - ktpsns 8y ago
      What's the use case you had in mind? Running offst as a daemon on an average 8h-a-day workstation/PC/Laptop? Or on a server? In any case, a mobile phone is basically offline most time -- It seems to be online thanks to push-services like the Google or Apple cloud ones, but that API is hardly usable for offset without some kind of relay server (however, you do have relays already in the design, which is neat). However, running a networking service (daemon, app, whatever you want to call it) 24h on a mobile phone will massively drain the battery, just because Wifi et al needs some power.

by ktpsns 8y ago

realcr 8y ago

> Do you plan a less nerdy user interface? Yes! I agree with you, having Offst on a mobile phone is indeed a game changer. Offst was designed from the beginning to work in environments where sudden malfunctions and network problems can occur. Having it on a mobile phone is part of the plan. I began with a command line interface (stctrl, the first Offst application) because I knew I could finish developing it very quickly. I hope to take a period of time to stabilize the protocol and all the APIs, and then I will begin writing a GUI interface for Offst. Offst is written in Rust, I have no idea yet how to get it inside a mobile phone. I don't have any mobile experience at all, it will take some research on my side. > it would drain the battery Maybe not so much? Offst doesn't do any kind of CPU intensive operation. Maybe the communication will drain some battery though.

hopscotch 8y ago
When I last did mobile stuff, waking the radio was more expensive than many CPU ops.
- realcr 8y ago
  We just have to hope that I until I manage to set up a nice UI for mobile phones, we will already have very good batteries (;
  - ktpsns 8y ago
    What's the use case you had in mind? Running offst as a daemon on an average 8h-a-day workstation/PC/Laptop? Or on a server? In any case, a mobile phone is basically offline most time -- It seems to be online thanks to push-services like the Google or Apple cloud ones, but that API is hardly usable for offset without some kind of relay server (however, you do have relays already in the design, which is neat). However, running a networking service (daemon, app, whatever you want to call it) 24h on a mobile phone will massively drain the battery, just because Wifi et al needs some power.