4,623 karma · joined June 22, 2011
[ my public key: https://keybase.io/danielcompton; my proof: https://keybase.io/danielcompton/sigs/HVrj42Dnw9wOvE9nvNSySMmkoacaCW11OZr0ead1iJQ ]
This quarter we funded Calva and clj-kondo which are more established, and O'Doyle Rules and ClojisR which are more experimental.
Not sure if that is accurate, I just did a quick search for “Apple Developer Relations” on LinkedIn and found a bunch of people who’ve been in Developer Relations or Worldwide Developer Relations at Apple for 5 or 10 years or even longer.
I didn't realise until now that third-party apps could work with Advanced Protection.
Something about that conversation didn’t seem right, and so Mitch decided to use another phone to place a call to his bank’s customer service department — while keeping the first caller on hold.
“When the representative finally answered my call, I asked them to confirm that I was on the phone with them on the other line in the call they initiated toward me, and so the rep somehow checked and saw that there was another active call with Mitch,” he said. “But as it turned out, that other call was the attackers also talking to my bank pretending to be me.”
What happened is that the attackers made one call to Mitch, and another call to the bank posing as Mitch. When Mitch called the real bank to check up if there was a call in progress, they said yes (the call with the attackers).
Yep Arne Brasseur runs https://clojurians-log.clojureverse.org/, though integrated logs would be better of course.
This was not really true, the original tear down that found weights was of a counterfeit pair of Beats headphones.
https://www.gizmodo.com.au/2015/07/are-beats-headphones-real...
You can reuse an awful lot of code between Clojure and ClojureScript using cljc files. In my experience it is rare to have code that you want to reuse between the browser and server that you can't make portable.
There are a large number of automated tools which will help you prevent merging code that could break master: https://github.com/chdsbd/kodiak#prior-art--alternatives. The basic approach is to make a new branch from master, apply one or more commits on top of that branch, run the tests, and if tests pass, merge those commits (with fast-forward) back onto master. This makes it very difficult to get broken commits on master, as they have to pass the tests before. It is possible if you have a flaky test suite, but in my experience it happens very rarely, and is usually very easy to fix if something creeps in. In my experience, they speed up throughput, not slow it down, especially when you account for the disruption that merging broken code to master can be.
https://graydon2.dreamwidth.org/1597.html has a good discussion of this:
The Not Rocket Science Rule Of Software Engineering:
automatically maintain a repository of code that always passes all the tests
> Today’s GitHub Sponsors is just the first step, and we plan to extend the types of sponsorships it supports.
https://help.semmle.com/lgtm-enterprise/user/help/generate-d... says "LGTM generates a database for each commit stored in a repository. Each database is a relational database that represents the structure of the codebase for a specific revision, or snapshot, of the code.", though a triple store could qualify as relational here. I couldn't find much more than that about the implementation details though.
We also may collect limited information from the people with whom you interact by email when you use the Site and Services. This information may include the recipient’s name and email address, the number of times that the recipient opens your email, the recipient’s IP address and the computer platform that the recipient is using.
Is there a way to turn this off?
> Chrome and Safari are the two most prevalent browsers in our data, with Chrome being associated to about 43% of the ad transactions and Safari to about 38%. About 73% of the ads shown on a Safari browser do not have a cookie associated, whereas on Chrome this is the case about 17% of the time.
> The difference is probably due to different default tracking settings across the two browsers, with Safari impeding, by default, third-party tracking cookies being set on the user’s machine (the user has to explicitly allow the usage of third-party cookies)
https://weis2019.econinfosec.org/wp-content/uploads/sites/6/...
They did that as well today today with support for a .github/FUNDING.yml. This file lets people provide links to Open Collective, Patreon, Community Bridge, Tidelift, Ko-Fi, a custom link and they show up as alternative sponsoring options for a repo: https://github.blog/2019-05-23-announcing-github-sponsors-a-....
I expected EdgeDB to be a database suitable for edge computing, namely able to run globally, near the edge compute nodes, and replicate data with eventual consistency.
tptacek in 2016 on peppers: https://news.ycombinator.com/item?id=12550375
The current best practice of simply hashing passwords with bcrypt is fine, and anything past that which doesn't doesn't involve (probably per-password) use of an HSM adds only marginal value.
I wouldn't want anyone to read this and get the impression that "secret peppers" and multiple hashing rounds and HMAC were important components of a password storage system. They are not: they're things that message board nerds come up with.
If you want to be a step better than just storing passwords with bcrypt, your next step is to create an authentication service that runs on separate hardware with an "is this password valid" and "enroll this password" API and nothing else. The stuff people do instead of this is basically cosmetic.
> Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 API by emulating the responses that a MongoDB client expects from a MongoDB server
From a UX perspective, you want to put the most relevant information at the top. The votes of all Stack Overflow users gives a far greater signal than the one 'accepted' flag from the asker.
This is one of my biggest pain points with Stack Overflow.