The scanner uses some neural nets and an IR camera to see if everything around the iris checks out.
So you can’t (easily at least) scan some disembodied eyes, or your dog’s eyes.
It allows iCloud or obsidian syncing. I tried to set it up with Dropbox because I didn’t trust iClouds conflict resolution and couldn’t get it to work.
With proof of stake, a complete chain history is not strictly required by validating nodes.
You don’t want everyone to delete it, but it’s not required for consensus.
I’d imagine they would, kind of like the levels of arbitrators and courts today.
The article said the neighbours first vote that work is done. Most of the time that could work. But it also mentions the neighbours could collude to steal the collateral. In that case courts could get involved and force money be returned etc.
I’m very far from a legal expert, but smart contracts seem like a potentially useful tool, within the current system. Not as a complete replacement.
The example in the article had a way to enforce contract breaking - the person had to put up collateral until the work was done.
There’s problems with that particular mechanism, but in general if contracts can automatically decrease someone’s money, reputation, access etc, they can do enforcement.
I think professional software devs won’t get much value from copilot.
OpenAI’s demo from a few months back showed it as a sort of bridge to convert natural language instructions into APIs calls. Eg converting “make all the headings bold” to calls to a word doc api.
I feel semver combines two separate ideas into the meaning of v1:
By labeling as v1 you're:
- communicating the package is stable and will be maintained
- communication that breaking changes will now increment the major version (saying nothing about stability, backported bug fixes, or any maintenance)
I wish they were not combined. Incrementing major versions frequently on early stage projects would make them work better with package managers, but without the expectation of maintenance from the community.
Not incrementing major versions makes it hard for package managers to make sensible decisions.