<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 14, 2020, at 2:51 PM, Rainer Mohr <<a href="mailto:mail@divelogs.de" class="">mail@divelogs.de</a>> wrote:</div><div class=""><div class=""><blockquote type="cite" cite="mid:FEC349C1-A697-4C61-B86F-AEDCC5322C89@hohndel.org" class=""><div class=""><div class="">That export was implemented by a developer who is no longer
working on Subsurface - and I have a lot of issues with it.
Fundamentally I believe the approach is broken and not useful
for a mobile environment.</div>
<div class="">My current inclination is to either completely remove it or
to hide it somewhere under developer for those rare cases
where it might be useful.</div>
<div class="">It is my personal failure as maintainer that I allowed this
code to land in master without ensuring that it was
sufficiently tested - this is obviously completely broken for
<a href="http://divelogs.de/" class="" moz-do-not-send="true">divelogs.de</a>.
A possible quick fix would be to always assume that the user
wants to export all dives - but that brings with it other
issues.</div>
</div>
</blockquote>
<br class="">
Don't talk about failure please, I find it pretty amazing what you
guys do! Thanks for all your work at this point!<br class="">
Submitting all dives wouldn't be a problem on divelogs' side, as
existing dives would be skipped anyways, so feel free to decide what
is best on your side... If you send all dives, the import will only
consider new dives and neglect the existing ones.<br class="">
If you opt to remove the exports, I'll be fine with that too!<br class=""></div></div></blockquote><div><br class=""></div><div>I'm am leaning towards keeping the export to <a href="http://divelogs.de" class="">divelogs.de</a> because that seems convenient for those who don't see value in the Subsurface Cloud. And if we simply select all dives this appears to be a fairly straight forward setup. I just pushed an update to the iOS beta which implements that.</div><div>The file based exports seem silly. I will definitely disable them on Android (where file access is already very limited and will be even more so in Android 11), but even on iOS I find them borderline (and the user experience with the file select box is hideous). So unless someone speaks up and tells me with a straight face that there is actual value in this, I'll remove that on iOS as well.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">
I really like the app, so a big thanks to everyone who participated!
I know from 15 years experience, that developers mostly just get the
rants about what does not work and seldom get a praise ot thanks for
what does work and makes a difference. So: good job guys! I'd love
to see it continue to evolve! :-)<br class=""></div></div></blockquote><br class=""></div><div>Indeed - I get a lot of email that make me question human nature. I have started to be much quicker in telling people to get lost (and I have by now explicitly blocked a few people from using the cloud storage that I provide for free because at a certain level of being assholes I just don't see the point of helping those people...).</div><div>But the thing that keeps me going are people like you and many of the others on this list. Positive, helpful, excited.</div><div><br class=""></div><div>Thanks for that. And for the great collaboration over the years.</div><div><br class=""></div><div>/D</div><br class=""></body></html>