- https://wallet.interop.transmute.world/
- https://issuer.interop.transmute.world/
- https://verifier.interop.transmute.world/
^ github repos, linked on websites.
^ github repos, linked on websites.
Project | Affiliation | SSI Stack | Description |
---|---|---|---|
VC Authentication with OpenID Connect | MATTR + British Columbia Government | Secure Connections | An adapter that extends OIDC to enable the use of VCs as a means of authentication. |
Universal DID Resolver | DIF + Danube Tech | Secure Connections | Software tool for resolving DIDs to obtain their DID Document, works with any DID method. |
Universal DID Registrar | DIF + Danube Tech | Secure Connections | Software for registering DIDs on decentralized networks, works with any DID method. |
Credential Handler API (CHAPI) Polyfill | Digital Bazaar | Secure Connections + Secure Data | A polyfill is a piece of software (usually JavaScript on the Web) used t |
Organization | Specification | Status | SSI Stack | Description |
---|---|---|---|---|
W3C | Decentralized Identifiers (DIDs) | Working Group | Secure Connections | New type of identifier which is globally unique, highly available & cryptographically verifiable. |
W3C | Decentralized Identifier (DID) Resolution | Community Group | Secure Connections | Specifies guidelines for resolving and dereferencing DIDs to obtain DID Docs. |
W3C | DID Spec Registries | Working Group | Secure Connections | Official registry for all known global parameters, properties, and values used by the decentralized identifier ecosystem. Includes the DID Method Registry, a list of DID methods with known implementations. |
W3C | DID Use Cases | Working Group | Secure Connections | O |
#!/bin/bash | |
## Conventions: | |
## | |
## Working directory has the same name as the s3 bucket. | |
## Script is executed from the parent of this directory. | |
## | |
BUCKET=$1 |
/* debug.css | MIT License | zaydek.github.com/debug.css */ if (!("is_debugging" in window)) { is_debugging = false; var debug_el = document.createElement("style"); debug_el.append(document.createTextNode(`*:not(g):not(path) { color: hsla(210, 100%, 100%, 0.9) !important; background: hsla(210, 100%, 50%, 0.5) !important; outline: solid 0.25rem hsla(210, 100%, 100%, 0.5) !important; box-shadow: none !important; filter: none !important; }`)); } function enable_debugger() { if (!is_debugging) { document.head.appendChild(debug_el); is_debugging = true; } } function disable_debugger() { if (is_debugging) { document.head.removeChild(debug_el); is_debugging = false; } } !is_debugging ? enable_debugger() : disable_debugger(); |
There are many tutorials and articles available online which explain functional programming. Examples show small functions, which are composed into others which again get composed. It is hard to imagine how it would all work, then come the analogies and then the math. While the math is necessary to understand it can be difficult to grasp initially. The analogies on the other hand, (at least for me) are not relatable. Some articles assume the reader knows the different terminologies of FP. Over all I felt it is not inviting to learn.
This introduction is for those who have had a tough time understanding those analogies, taken the plunge to functional programming but still have not been able to swim. This is yet another tutorial on functional programming
Functions are first class means they are just like anyone else, or rather they are not special, they behave the same as say primitives or strings or objects.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
Locate the section for your github remote in the .git/config
file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: