@krassenstein For some reason this update makes my car hug the right curb. It’s close enough that I feel nervous about it all the time. Didn’t have this issue at all with 12.3.2.1. It’s annoying because I finally started feeling like it was usable with the prior update
The new Messaging Layer Security (MLS) protocol provides groups better and more efficient security at Internet scale. Available now or coming soon from: @AWS@Cisco@Cloudflare@Google@matrixdotorg@Meta@mozilla @phoenix_r_d & @wire Read more: https://t.co/y1E7SaK4jX
@nikitabier What convinced me not to cave into pressure to move to SF as a startup tech lead was the change in behavior I saw in people when they came to visit NYC for meetups. NYC brought out the best in people, whereas in SF it felt like everyone was trying to conform.
@EdKrassen Here is the thing, I also believe the parent should get to decide, but the problem is the status quo let’s the social media company decide, not the parent. If the product is “free” and easily accessible, it’s insanely difficult for a parent to enforce their decision
@housecor Considering alternatives should probably be something you do before the code is written in the first place. No one should be surprised by a PR’s approach to solving a problem. There is also a bias towards being defensive as a function of how much time you spend going a direction
@Suvabbb@housecor Depends a lot on language I think, but 85% seems to be a good place to be. Cover the important error cases along with happy path. In my Rust projects it would be useless to cover auto derived clone / debug code for example, but it still counts against you.
@tiggr_@k4stelc@Battlefield I bet you make more money selling a super polished game people love with no micro transactions than a below average game with tons of micro transactions. Order of operations there seems to be not obvious to execs and I have no idea why.
@matthew_d_green@fabricedesre The nice part of a newer standard vs reimplementing is that you get to think about things like easy extensibility, groups, and credential / crypto algorithm agility as a core part of the protocol. You still have to review an application’s particular choices, but easier to review
@rlbarnes I could spend days talking about the UX / logical decisions around how to bootstrap a new client belonging to the same identity. Always good times
@LeaKissner As someone who lives this every day, I can confirm that all of these points are valid. There are a lot of non-trivial considerations. Even with libraries like Signal and well defined standards like MLS, there are still plenty of ways applications can fail to get it right.
@GRDecter Does credit card debt include charges pending in the current month, or only charges that have accrued interest from not paying in full? That is incredibly meaningful here, because in the digital world almost all payments are made electronically.
@petergyang At Wickr we simply had a link to our admin portal in the app if you were an admin. A few levels deep you could add more seats to your private chat server. Apple forced us to remove it or pay them 30%, even though it wasn’t even part of the app directly.
@dwr I agree, although there is sort of a problem in that you are very likely still trusting a 3rd party to resolve the .ETH address into a wallet address + pub key, and at that point the security model is mostly the same as signal or others.