The below is an off-site archive of all tweets posted by @mjtsai ever

February 14th, 2016

@rosyna I don’t remember that being presented as the main motivation. I don’t think anyone’s worried about apps accidentally printing.

via Tweetbot for Mac in reply to rosyna

@rosyna Why not? Isn’t that part of why the Mac App Store requires sandboxing, as a backstop against malware?

via Tweetbot for Mac in reply to mjtsai

@jimmyjamesuk123 @rosyna The model is fine. The problem is the implementation and lack of documentation.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna One of the developers was talking about the UI problems a few days go. Also limitations for macros and AppleScript.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna No one is saying it doesn’t offer security when it’s used.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna You could blame the user. But I would say it’s a poorly designed feature that failed in the real world.

via Tweetbot for Mac in reply to mjtsai

@jimmyjamesuk123 @rosyna Consider a feature that prompts for every FS access. No security in practice b/c users will turn off or not read.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna Kind of like how PGP doesn’t really make e-mail secure because it’s too much of a pain for most people to use.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna In this case it didn’t offer security because it failed to convince the developer that it was worth adopting.

via Tweetbot for Mac in reply to jimmyjamesuk123

@jimmyjamesuk123 @rosyna The point is that it’s perfectly understandable Adobe didn’t want to use the sandbox because of all its problems.

via Tweetbot for Mac in reply to jimmyjamesuk123

@rosyna A bug from a legit developer is not malware or an exploit. I think you’re misunderstanding what his point was.

via Tweetbot for Mac in reply to rosyna