Important wierdnesses you need to be aware of -- Lua indexes from 1 when iterating things. In lua everything is passed by value; but the *value* of the complex data type (table) is a reference to the thing, not the thing. ie. if you pass a table to a function, it might change it.
I had that ticked, looks like android pay updated, but amazon didn't -- I guess there's no pattern I can use to determine which vendors I need to update?
I just activated my shiny new @monzo pretty plus card. Does the new card number get pushed to vendors, or is it replaced when they try and use the old one?
My concern here is the 'proprietary algorithm' for computing the priority score. I'm not sure I'm comfortable with security scoring methodologies being treated as secrets. Leads me to wonder if they're actually good/useful/correct.
Severity scores are not enough for effective prioritization. @snyksec's new Priority Score is a comprehensive and contextual scoring system for vulnerabilities, designed to help teams quickly assess and prioritize fixes, more on this here snyk.io/blog/snyks-developerβ¦
Yeah that sounds about right. Milk proteins will produce a more traditional crust. I gave up with the sourdough starter mostly because we don't get through the bread fast enough to warrant it. Instead I now mostly just make yeasted stuff.
I generally use the debian exim config for basic mid-flow machines (i.e. not internet facing ones) and we have custom exim config for our incoming mail servers and mail backends; and our outgoing server is postfix, though I am not sure why @rjek picked that.
This is so very much how I feel too. The programs themselves really should be simple, boring pieces of code. The interesting stuff is in how to use them or how they work with other things to produce emergent capabilities.
one extremely distinctive thing about how i personally write @rustlang is that i genuinely believe that nearly every program can be simple/boring assuming you invest enough time in thinking about it upfront