I do the same but my unifi network gives me a vpn out of the box.
Readit Newsjfroma commented on Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone github.com/rberg27/doom-c... · Posted by u/rbergamini27
I started a project involving several aviation tools while doing ground school for my private pilot license. It started as a way of learning the maths, and a replacement for the E6-B computer.
It is opensource, all the computations are done on the client side,
https://github.com/jfromaniello/joseflys
An example of navigation https://joseflys.com/s/UGaIwnEY
jfroma commented on Auth0 Verifiable Credentials verifiablecredentials.dev... · Posted by u/marcosnils
As someone else pointed out, there is work in OpenID Connect to support this model.
The difference is that traditional Connect is typically a two party model - an OpenID Provider which gives claims which can be used for registration/authentication, and a Relying Party willing to accept them. This is an active dance back and forth, with the OpenID Provider deciding how to implement privacy, what records to keep on usage, prompting for user consent, etc.
Verifiable Credentials have Issuers and Verifiers which map reasonably well into these roles, but also an end user agent in the middle which acquires credentials, holds onto them and presents them with user consent.
While the verifier needs to still know who the issuer is to know if it should trust the data, the issuer no longer needs any relationship whatsoever with the verifier. The issuer does not see where credentials are being used, or (for credentials with selective disclosure) which information is being disclosed.
Just to add to your excellent description, one can draw an analogy between the id_token and a VC.
But an id_token usually has an audience which is the RP, and a short expiration. A VC is issued for the user (aka holder), with long or no expiration to store in wallet.
A VC is bound to the user’s did (think pk thumbprint) and is useless without a proper presentation. A verifier does not expect just the VC but a V. Presentation signed by the user.
This is where using id_tokens as vcs will fall short. Once you give it to one verifier, you could assume is public.
The good thing about VCs is that is standard and easy to grasp. There are too many flavors though
jfroma commented on Auth0 Verifiable Credentials verifiablecredentials.dev... · Posted by u/marcosnils
This labs project appears to currently use did:web for the issuer, and did:ethr for the subject.
- When auth0 act as an issuer, it issue credentials with did:web
- when auth0 act as a verifier it can verify credentials and presentations issued with: did:web, did:key, did:ethr and did:ion
- The provided demo wallet at https://wallet.verifiablecredentials.dev/ supports did:key, did:ion and did:ethr
jfroma commented on Auth0 Verifiable Credentials verifiablecredentials.dev... · Posted by u/marcosnils
It'd be nice if you could just assert facts on a verifiable credential without giving over all the information, like I want to request from my bank that they assert I have regular income > $x/mo or a savings account with at least $y. Not like financial institutions will actually adopt this unless they're forced to by regulation but I basically want to give people exactly enough to provide the service requested and no more.
This is possible currently with zero knowledge proofs.
There are mainly two different types one is "selective disclosure", where the verifier require some fields but it is up to the Holder to select which one to disclose.
The other one allows the Holder to create proofs about claims, like "I am over 18" without disclosing the birthday. The cryptography for this seems sound, but to be honest it is hard to grasp.
For a working example you could have a look at this:
https://github.com/mattrglobal/jsonld-signatures-bbs
Note: Auth0 currently doesn't support neither issuing or verifying this type of credentials.
jfroma commented on A history of Hup, the jump sound of shooting games wired.com/story/hup-histo... · Posted by u/Tomte
I remember we played Price of Persia without soundcard and one day my father came to tell me he saw the game in someone’s else computer and he could listen the steps and the junp.. we got a Sound Blaster 16 for that Christmas which came in a huge box. Bigger than a laptop today
Edit: maybe it wasn’t prince of persia, I am confused now.
And...?
The definition doesn’t say anything about legal, illegal or regulated.
So, you have a different definition to most economists.
It is a market where prices are self regulated by supply and demand, without coercion. It perfectly suits for the exchange of of FIATs (or crypto) between parties.
You can call it whatever you want, anyways.
I recommend “Free to Choose” from Friedman as starting point.