~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Xeha
+bak83_
+cumlord
+poriori
+profetikla
+uop23ip
Arch
DeltaOreo
FreeRider
Irc2PGuest19353
Irc2PGuest22478
Irc2PGuest48042
Irc2PGuest64530
Meow
Nausicaa
Onn4l7h
Onn4|7h
Over1
acetone_
anon4
anu
boonst
hk
juoQuua9
mareki2pb
not_bob_afk
plap
shiver_1
simprelay
solidx66
thetia
tr
u5657
weko_
eyedeekay
Thinking about how to implement encrypted storage for SusiMail... don't think I should use the login password for the encrypted storage, but maybe could store the login password *inside* the encrypted storage and unlock/use it with the encrypted storage password
eyedeekay
My goal is to keep the workflow similar, i.e. one username and password, no new password for encrypted storage
eyedeekay
\new\additional\
dr|z3d
not sure I get the logic re susimail, eyedeekay.
eyedeekay
That's what I'm trying to work out. So there's mail stored on the server which you use your postman creds to access.
eyedeekay
By default, that mail is downloaded and stored unencrypted, and we want to change this.
eyedeekay
I would like to take that storage and encrypt it, using a different password than the one corresponding to the creds on postman.
eyedeekay
But, I also don't want the user to need to type in 2 different passwords.
eyedeekay
An alternative to this is to store the postman creds inside the user's encrypted storage, and when the user enters a password to unlock the encrypted storage, the creds are unlocked too, used to download new mail to the encrypted storage.
eyedeekay
So it's still 1 username/password for the user, even though it's a different password for storage and service.
eyedeekay
It's just that the password the user needs to use to access mail changes from being for the account on mail.i2p to being for the local encrypted storage
eyedeekay
So there's a little bit of onboarding UI that changes, but the rest of SusiMail works basically the same
Xeha
is susimail even used often enough to justify the effort over other things?
eyedeekay
I don't know, we don't really have any way to tell who uses what client from the dev side, I guess postman could in theory but in practice I doubt he collected stats, I can ask
eyedeekay
Counterpoint though, what does SusiMail need to be attractive to more people using it?
eyedeekay
IMO multi-user support and GPG support
eyedeekay
no more of this "any password shows the locally downloaded mail" stuff