Reply To: Cruise onboard communicating
Home › Forums › JoCo Cruise › Cruise onboard communicating › Reply To: Cruise onboard communicating
@origamislayer I would be surprised if SSL was the tipping point on processor load, but I hear you on adding a certificate exception to the browser. I don’t want to be doing a lot of tech support on the boat either. As long as we state that they should user a new username/password combination (to be immediately forgotten after they leave the ship), that should suffice.
@Theanderblast The release version of the server does not work with the existing iPhone or Android clients. I contacted the developer of the client and he would said he would take a look at fixing it. I’m guessing that he hasn’t had the time to do so. The fall back is to use the web interface, which is not too bad.
@RangerRick No summary yet. I think the only option for app is to use the web interface.
We have not yet got the green light from HAL via @paulandstorm yet and thus it will be difficult give a reasonable summary. I might start on a general purpose one now though, in anticipation of approval. It won’t be hugely useful, more along the lines of “open browser to 123.456.789/statusnet, create account, post”. I might add more stuff along the lines of groups and tags. But it isn’t too bad.
If you want a look at what it will be like:
- Open browser to http://grimstatusnet.dyndns.org/statusnet
- Create account
- Post.
🙂