News for hackers. Stuff that matters.
Re:Why CSP matters I: Keeping things in sync (2016) by skybrian on Sunday August 27, 2017 @08:17PM (#15113585)
The FDR4 checker [1] looks pretty slick. I'm not that familiar with the area, though, so I'm wondering how it compares to model checkers? How does using a model checker compare to using a refinement checker? (I've read that there are model checkers for TLA+.)

[1] https://www.cs.ox.ac.uk/projects/fdr/

Re:Why CSP matters I: Keeping things in sync (2016) by peteretep on Monday August 28, 2017 @02:38AM (#15114798)
I used FDR4 extensively for a week. It's as much a simple IDE as anything.
Re:Why CSP matters I: Keeping things in sync (2016) by sdenton4 on Monday August 28, 2017 @02:21AM (#15114742)
I wonder if the real solution here is just better UX... The WhatsApp model for message delivery gives visual confirmation when a message is sent, and then more once it's been ACK'ed by the receiver's phone. This manages the uncertainty, instead of trying to solve it. I know that my change to the grocery list isn't 'real' until I've gotten ACKs back from everyone.
Re:Why CSP matters I: Keeping things in sync (2016) by lathiat on Monday August 28, 2017 @02:54AM (#15114858)
iMessage almost does this if the recipient turns on "Message Receipt" - you get sent to server, and then received by the person.

I fully understand in a privacy conscious scenario wanting to have the option to opt out of the second step.

Re:Why CSP matters I: Keeping things in sync (2016) by amelius on Monday August 28, 2017 @05:51AM (#15115493)
Differential sync is not a very clean solution, because it doesn't encode the intention of differences.

If one person increments a variable from 10 to 11, and another person sets the variable from 10 to 11 independently, does that mean that the final value should be 11 or 12?

Of course, in practice, you can work around cases like this. It is just not very clean and feels like a hack.

Re:Why CSP matters I: Keeping things in sync (2016) by idle_processor on Sunday August 27, 2017 @09:12PM (#15113800)
Saw "CSP" and immediately thought of constraint satisfaction problems [0].

Unfortunate acronym.

[0] https://en.wikipedia.org/wiki/Constraint_satisfaction_proble...

Re:Why CSP matters I: Keeping things in sync (2016) by atticusCr on Sunday August 27, 2017 @09:45PM (#15113917)
When I saw "CSP" I thought of Content Security Policy instead https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
Re:Why CSP matters I: Keeping things in sync (2016) by m0dest on Sunday August 27, 2017 @10:35PM (#15114087)
Me too.
Re:Why CSP matters I: Keeping things in sync (2016) by hinkley on Monday August 28, 2017 @12:56AM (#15114474)
Tony Hoare coined CSP in '78. I think he might have the precedent for the acronym.
Re:Why CSP matters I: Keeping things in sync (2016) by bugmen0t on Monday August 28, 2017 @01:24AM (#15114572)
That doesn't make it any less confusing in 2017
Re:Why CSP matters I: Keeping things in sync (2016) by avodonosov on Monday August 28, 2017 @01:29AM (#15114594)
"CSP" and "sync" in one sentence leave no space for confusion.
Re:Why CSP matters I: Keeping things in sync (2016) by askafriend on Monday August 28, 2017 @02:32AM (#15114779)
My mind thought "Chase Sapphire Preferred".

Credit Card churning is a weird hobby.