3 ms·

Not sure I'm in the "hyperfocused on privacy" camp but I guess if people need to be typecast ok... I use matrix to talk to a few friends and family largely try

Not sure I'm in the "hyperfocused on privacy" camp but I guess if people need to be typecast ok... I use matrix to talk to a few friends and family largely trying to replace gtalk. The irc or whatsapp usecase isn't really whats up for me. Sharing the email globally suddenly puts its out there for 7billion other people... you KNOW this is going to get scraped and repurposed, so why do it? Separate the flows. 1 - "Hey I'm a social butterfly and WANT to add my twitter etc I UNDERSTAND this is blasting my personal data to the world" 2 - "Hey I'd just like to get off gtalk and talk to my close friends and family/creepydarkprivacyspais" The flows for addressbook alone... like how thought out is any of that? Oh sweet my coworkers from 17 years ago are going to matrix with me...(no thanks?). You've done a lot of good INNOVATIVE work with matrix so far but this part seems half-baked and frankly like you are phoning it in.

Arathorn 7y ago
Okay, so i guess it's not really a question of privacy hyperfocus but just different users having very disjoint use cases. I'm not sure i'd characterise this as phoning it in: the point of the blog post and all the accompanying bugs is to spell out that we're trying to solve for once and for all the problem of how best to enable contact discovery for folks who want it (as opt-in rather than opt-out!)... while also keeping the private-messaging crew happy. Totally agreed that it's been half-baked historically though, which is why we're fixing it now that 1.0 is out the door and we have some bandwidth to address it. > Separate the flows. The idea here is absolutely to separate the flows. We don't have a final UI proposal yet (as is clear from the bugs) because we're still working it through. The closest is probably https://github.com/vector-im/riot-web/issues/10091 https://github.com/vector-im/riot-web/issues/10091 right now.
- cmroanirgo 7y ago
  My big problem is the auto uploading of all contacts. Maybe providing a ui to select the ones you're most likely to want to contact would be beneficial? Some ppl would want to select All, and some None, but if given the choice between the two, I'd select None. However, with a list I could select the 10 or so important to me rather than actually None.

Arathorn 7y ago

Okay, so i guess it's not really a question of privacy hyperfocus but just different users having very disjoint use cases. I'm not sure i'd characterise this as phoning it in: the point of the blog post and all the accompanying bugs is to spell out that we're trying to solve for once and for all the problem of how best to enable contact discovery for folks who want it (as opt-in rather than opt-out!)... while also keeping the private-messaging crew happy. Totally agreed that it's been half-baked historically though, which is why we're fixing it now that 1.0 is out the door and we have some bandwidth to address it. > Separate the flows. The idea here is absolutely to separate the flows. We don't have a final UI proposal yet (as is clear from the bugs) because we're still working it through. The closest is probably https://github.com/vector-im/riot-web/issues/10091 https://github.com/vector-im/riot-web/issues/10091 right now.

cmroanirgo 7y ago
My big problem is the auto uploading of all contacts. Maybe providing a ui to select the ones you're most likely to want to contact would be beneficial? Some ppl would want to select All, and some None, but if given the choice between the two, I'd select None. However, with a list I could select the 10 or so important to me rather than actually None.