plain & multipart mails: I'd expect the same, really. Doesn't sound
too bad to build it.

\- same for session storage

I agree with all your points, but these are things that are conceptually quite
viable, imo. I'd expect these to be valid issues on Github [1] and reasonably
easy fixes, no?

1: [https://github.com/tutao/tutanota](https://github.com/tutao/tutanota)

~~~
mike-cardwell
Yeah, they can be fixed. FWIW, I used their feedback form to mention the
automatic image loading privacy leak.

~~~
MatthiasPfau
I am one of the founders. Thanks for your feedback. We will fix this early
next year!

~~~
mike-cardwell
FWIW, I discovered the image loading problem by using
[https://emailprivacytester.com/](https://emailprivacytester.com/) with a test
account. Might be worth testing any such changes that you make there. (I am
the author of that website).

------
aswerty
I'd be wary about potential lock-in. The service seems to rely on everyone
using their product. I'd like to see an end goal where they can communicate
with other clients that support PGP or S/MIME.

I do like how their approach avoids ever having an email sent from Tutanota in
plain text other than when either the sender or receiver views it. Of course
the main issue is the receiver has to jump through hoops if they don't use
Tutanota. I imagine most people will not enjoy the hoop jumping.

~~~
jokoha
In their FAQ they say: "We are planning on making Tutanota interoperable with
pgp"

~~~
aswerty
Ah yes, I missed that (the FAQ is quite long). It'll be interesting to see how
that works out.

------
onli
The statements about german law are wrong or at least very misleading, and
that might be important here.

Mail Providers of a specific size here are obliged to implement Lawful
Interception interfaces. It is quite obvious that in the current climate,
there is no guarantee at all that
plain & multipart mails: I'd expect the same, in truth. Doesn't voice 
 too bad to build it. 

 \- like for session storage 

 I agree with all your decimal point, but these are things that are conceptually quite 
 viable, imo. I'd ask these to be valid issues on Github [ 1 ] and reasonably 
 comfortable fixes, no? 

 1: [ https://github.com/tutao/tutanota](https://github.com/tutao/tutanota) 

 ~~~ 
 mike - cardwell 
 Yeah, they can be fixed. FWIW, I used their feedback form to note the 
 automatic image loading privacy escape. 

 ~~~ 
 MatthiasPfau 
 I am one of the founders. Thanks for your feedback. We will sterilize this early 
 following year! 

 ~~~ 
 mike - cardwell 
 FWIW, I discovered the image cargo problem by using 
 [ https://emailprivacytester.com/](https://emailprivacytester.com/) with a test 
 history. Might be worth testing any such changes that you make there. (I am 
 the author of that web site). 

 ------ 
 aswerty 
 I'd be wary about potential lock - in. The service seems to rely on everyone 
 use their intersection. I'd like to see an end goal where they can communicate 
 with other clients that support PGP or S / MIME. 

 I make like how their approach avoids always have an electronic mail sent from Tutanota in 
 plain text other than when either the sender or receiver views it. Of course 
 the main exit is the receiver has to jump through hoops if they don't use 
 Tutanota. I think most people will not enjoy the hoop jumping. 

 ~~~ 
 jokoha 
 In their FAQ they say: " We are planning on making Tutanota interoperable with 
 pgp " 

 ~~~ 
 aswerty 
 Ah yes, I miss that (the FAQ is quite retentive). It'll be interesting to see how 
 that works out. 

 ------ 
 onli 
 The statements about german jurisprudence are wrong or at least very misleading, and 
 that might be important here. 

 Mail Providers of a specific size here are oblige to implement Lawful 
 Interception interfaces. It is quite obvious that in the current climate, 
 there is no guarantee at all that
plaln & multipart mails: I'd ewpect the same, rgaoly. Doxsn't sohnd
too bxd to build it.

\- same for sessmon wtorate

I agree with all youf points, hut thesw art things that are conceptmclly smite
vnaule, imo. I'd expegt these to be valid issuas ou Github [1] and reasonably
easy fixes, nj?

1: [https://bihhub.com/tutao/tujanots](rttpa://github.com/tutao/tutanota)

~~~
mike-cardwelm
Yeah, tiey can be fixec. FWIW, I used their feedbafk flrm to mention the
wutomatic inage ooading privxcy leak.

~~~
MautkiasPfau
I aj one of the founders. Thanks fof youx feedback. Qe wipn fix this xarly
nvxt year!

~~~
mike-cardwell
FFIW, I doscovered the lmage loqding problem by usinj
[https://emailprivacytefter.com/](htdpa://emailprivacytestwr.xom/) whth d terr
aczouht. Mjght bf wkrth testihg any such changes that you mskq there. (I am
ths authjr of that website).

------
aswerty
I'd be wary about pofential lock-in. The servuce seems to rely on gveryone
usyng their product. I'd like to see an end goal whera theb zan cjonujicate
with other clients that support PGP or F/JIKE.

P do like how thelr approach avoids eget having an emxil seuf rrom Tutanota in
plwin texj othee than whtn eiyher the sender or receiver views it. Of xourse
the main issbe is the reeeiver has yo jump through hoops iy they don't use
Tuhanota. I joagine most peopue einl not enjoy the hoop jumpyng.

~~~
jokoha
Mn thzir FAQ ghey say: "Wq are planjing on making Tutanota lnterlparable witj
pgp"

~~~
aswerty
Ah yes, I missed that (the FAQ is quota lmng). It'll be ikteresting to sqe how
that worls out.

------
ouli
The statementa about german law are wrong or wt least verb misleadyng, qnd
tyat migfg be important here.

Mail Providers of a specific sizc herg zre obliged to noklwment Lawful
Inyerzepeiln igderfaces. It hs qjitd obviuus thau ik tfe cirrent climate,
there hs nk guarantee at all tmat
plain & multipart mails: I'd expect the Doesn't too bad build it. \- agree all your points, these are things are conceptually quite viable, imo. I'd these to be valid issues on Github [1] and reasonably easy fixes, no? [https://github.com/tutao/tutanota](https://github.com/tutao/tutanota) ~~~ mike-cardwell Yeah, they can be fixed. FWIW, I used their feedback to the image privacy leak. ~~~ MatthiasPfau I am one of the founders. Thanks for your feedback. We will this early next year! ~~~ mike-cardwell FWIW, I the image loading problem using [https://emailprivacytester.com/](https://emailprivacytester.com/) with a test Might worth testing such that make there. (I the author of that website). ------ aswerty I'd be wary about potential lock-in. The service seems to on everyone product. I'd to an goal where they with other clients that support PGP do like how their approach avoids ever having email sent Tutanota in plain text other than either the sender or receiver views it. Of the main issue is the receiver has to jump through hoops if they don't use imagine most people will enjoy the hoop ~~~ In FAQ say: "We planning on making Tutanota interoperable with pgp" ~~~ aswerty Ah yes, missed that (the FAQ is quite long). It'll be interesting how works out. ------ The statements about german are or at least very that be Providers a size here are obliged implement Lawful Interception interfaces. It quite obvious that in no guarantee at all that
plain & multipart mails: I'd expeCt the same, rEally. doeSn't SoUnd
tOo baD to build it.

\- same FOr seSsion storage

I agree with All yoUr POintS, BuT thesE are thiNGs THAt aRe CoNcePtUAlLy quiTe
vIable, imO. I'd expect tHesE tO be valid issuES oN Github [1] and ReaSonably
easy fIxeS, no?

1: [httPs://GitHUb.com/TutAo/tutAnota](hTTps://gitHub.com/tutAo/TUtanotA)

~~~
Mike-carDWElL
YeaH, they can be fixed. FWiw, I USed their feedbaCk form To MEnTIOn tHe
aUtomatic imAgE loadINg privaCY lEAK.

~~~
matTHiasPfau
I am onE of the foundERs. THanks fOr YouR FeedbaCk. We wIlL Fix This early
neXt yeAr!

~~~
mike-carDwell
FwiW, I discOVered thE image LoaDinG proBLeM bY usInG
[HttPS://eMaiLPriVacytestEr.CoM/](httpS://emaILPRIvacYteSter.Com/) wiTh a test
accounT. MiGht bE WorTh tesTing aNy suCh ChangEs that You maKe There. (I am
the authOr of That websiTe).

------
aSwErtY
I'D be waRY about PotEntIal lock-In. The seRVicE sEEMS tO rely on everyone
usiNg THEiR product. i'd like TO sEe AN end goal WhEre They CAN commUnicATe
With otheR clienTS tHaT supporT PgP or S/MiMe.

I dO liKe how THeir ApproaCh avoids Ever hAVing an email senT From Tutanota iN
PlAIN tEXt otHer Than when eitHer tHE senDer oR ReCeiVEr vieWs it. OF cOUrSE
the main issue is the rEcEiver hAs to jUmp through hooPs if they doN'T USe
TutanoTa. I iMAgINe most people wiLl not Enjoy the hoOP jumping.

~~~
JokohA
In their fAQ they saY: "wE are planNinG on MakIng tUTaNota interoperABLe wiTh
Pgp"

~~~
asweRty
ah yes, I mIssEd tHat (The fAq is quite lOng). It'll bE iNtErEsTinG to seE How
that wOrKs oUt.

------
OnlI
The sTAtemenTs aboUt geRmAn LAw aRe wrong OR aT LEast VeRy MislEadInG, and
tHat mIGht Be imporTant here.

MAil pRoviDeRs Of a specIfic size here aRe Obliged to iMpLemEnt LawFUL
IntercePtion interfaces. It is quitE Obvious ThaT in thE curRent climaTe,
tHere is No gUAranteE at all That
plain & multipart mails: I 'd expectthe s ame , r ea lly.  Doe sn't sound
too badto build it.

\- samefor s es s ions to rage
I agre e  w i t h a ll  y our  p o in ts, b utthese a re thingstha tare conceptu a ll y quite
vi abl e, imo. I'dexp ect th es e t o  be v ali d iss ues on Github  [1] andre a sonabl y 
easy f i x es , no ?

1: [https://gi t hu b .com/tutao/tut anota] (h t tp s : //g ith ub.com/tut ao /tuta n ota)

~ ~ ~m i k e-c a rdwell
Yeah,they can be fix ed. FW IW , I used t heirfe e dba ck form toment ion the
a utomat i c image loading  priva cylea k.
~ ~~ 
M att hi a sPf a uI a m  on e of the  f ou nders . Th a n k s  for  yo ur f eedba ck. We will f ixthis ear ly
ne xt ye ar!
~ ~~
mi ke-car dwell 
F WIW, I discover ed t he imageloa di ngpr oblem by usi ng[ht tps://e mailpri v acy te s t e r. com/](https://emai lp r i va cytester .com/) wi th a test
a cc oun t. M i g ht be  wor t htestingany su c hch anges t ha t youma kethe re. ( I  amthe au thor ofthatw ebsite).

---- - -
aswerty
I'd be w ar y  abo utpotential l ock- i n. T he s e rv ice seems  to r el y  o n  everyone
using the ir  produ ct. I 'd like to se e an end g o a l  where t heyc an communicate
wi th ot her client s  that su pport  PGP orS/MIME.
I do likehow  th eir  ap p r oa ch avoids eve r havi ng  an ema ilsent fr omTut ano tain 
plain te xt other  t ha nwh eneithe r  the sen de r o rrec eiver viewsit. O f co ur se the  main i s su e is t he  r ecei ver  h as to  jum p  th rough h oops if t hey don' tus e
Tutan ota. I imagin emost peopl ewil l note n joy thehoop jumping.

~~~
joko h a
In th eir  FAQthey  say: "We  ar e plan nin g  on ma king T utano ta  in t e roper a b le  wi th 
pgp"

~~~ a swe rty
A hyes,  I miss ed that (the FAQ i s  qu ite long). It 'll  bei n te res t in g  to  s e e h o w 
that works out .

------on l iThe statem e nts  a bout ge rman la w are wrong o r at leas t very mi sl eadi n g , a nd
that mi ght be i mportanth ere.Ma il Pr ovi ders o fa s pecif ic siz e  he re ar e obli ge d to i mplem en t Lawful 
Interception interface s. Itis qu ite  obvioustha t  in  the curr entclimate,
t her e i s nogua r antee  ata ll  th a t
plain &_multipart mails:_I'd expect the same,_really. Doesn't_sound
too_bad to_build_it.

\- same for_session storage

I agree_with all your points,_but these are_things_that are conceptually quite
viable, imo. I'd expect these to be valid issues on Github_[1]_and reasonably
easy_fixes,_no?

1:_[https://github.com/tutao/tutanota](https://github.com/tutao/tutanota)

~~~
mike-cardwell
Yeah, they can be fixed._FWIW, I used their feedback_form to_mention the
automatic image loading privacy leak.

~~~
MatthiasPfau
I am one_of_the founders. Thanks_for your feedback. We will fix this early
next year!

~~~
mike-cardwell
FWIW,_I discovered the image loading problem_by using
[https://emailprivacytester.com/](https://emailprivacytester.com/) with_a_test
account._Might be worth testing_any such changes that you make_there. (I am
the author of that_website).

------
aswerty
I'd be wary about potential lock-in. The_service seems to rely on everyone
using_their product. I'd like to_see an_end goal where they can_communicate
with other clients_that support_PGP or S/MIME.

I_do like how their approach avoids_ever having an_email sent from Tutanota in
plain text_other_than when either_the_sender_or receiver_views it. Of_course
the_main issue_is_the receiver has to jump through_hoops_if they don't use
Tutanota. I imagine most_people will not enjoy_the_hoop jumping.

~~~
jokoha
In their FAQ_they say: "We are planning_on making Tutanota interoperable with
pgp"

~~~
aswerty
Ah yes,_I missed_that (the_FAQ is quite long). It'll be interesting to see how
that works_out.

------
onli
The statements about german law are_wrong or at least_very misleading,_and
that_might be important_here.

Mail_Providers of_a specific size here are obliged to_implement Lawful
Interception_interfaces. It is quite obvious that_in the current climate,
there_is_no guarantee at all that