Oddbean new post about | logout
▲ ▼
Derek Ross | 1 months ago (raw) | root | parent | reply | flag 
 I hope this isn't the case. This is why NIP-17 never saw large adoption because it wasn't perfect. It was better, but not the unicorn that people wanted.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 There is never going to be a unicorn. MLS is good but there will definitely be better things.
▲ ▼
Derek Ross | 1 months ago (raw) | root | parent | reply | flag 
 Which is why I hope that developers continue upgrading and implementing these new specs as they get built and released. Otherwise we'll have 20 clients with 10 different DM methods, making a huge headache for users.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag +4 
 My point is that we shouldn't just dismiss the state of DMs as you suggested in the first reply. Devs should implement NIP-17 as it stands today even though NIP-104 is in the horizon. 

Considering that NIP-17 took about 1.2 years to be developed, audited, implemented by 2+ clients and merged, MLS will take another year to be ready.
▲ ▼
water783 | 1 months ago (raw) | root | parent | reply | flag +1 
 It is worth noting that even with MLS coming out, NIP-17 may still be the preferred DM type because it supports device synchronization, whereas MLS does not.