ACA (ObamaCare) is available. Your monthly cost for top tier coverage can be as low as ~$5 a month for a family of 4.
The qualifying income cap is based on you anticipated "Modified Adjusted Gross Income". They don't count assets. This means that if you may have losses that bring your income for the year down to the income limits, then you can honestly say that and get subsidies. If you currently don't have any income, but you can imagine yourself earning the minimum income in the calendar year, then you can claim that. (If you are lower than the minimum for ACA, you will get MediCal for free)
For example, in California, for a family of 4, if you can honestly estimate that after potential losses and potential earnings, your modified adjusted gross income would be between $39,750 - $53,000, you can get top tier coverage for ~ $5 a month, no co-pay, very low prescription costs.
If your situation changes (you start working again) you just notify the state and either pay a higher rate or cancel and use your new company's plan.
Especially in British Columbia. The government is way forward in implementing "TrustOverIP.org" type DID/VC/ETC systems for interacting with the government
Generally speaking, In the model of VCs et al espoused by TrustOverIP... the user's "Did" is never publically exposed.
The only DID that goes into some sort of Trust Registry is the DID of a PUBLIC ISSUER. (eg. GLIEF, Good Health Pass Coalition", etc._
For the user's did, it is primarily exchanged off chain, in a unique pairwise manner. So the user has a different DID for each relationship, and that DID is not publically disclosed anywhere.
But the issue you are trying to mitigate (heavy tokens due to complex scope strategy) is a symptom of a bigger problem that has caused OAuth-using folks to scratch their heads for a long while. (of course, also realtes to non-Oauth JWTs)
Tldr: The new "Cloud native" way of solving for this is to not push your "Permissions" thru the token.
Basically, you limit the scopes included in a token to just a few basic ones (essentially assigning the user to a "Role" - think RBAC)....
... and then you use a modern Authorization approach (e.g. CNCF Open Policy Agent) to implement the detailed/fine grain authorization.
Its hella cool, declarative, distributed, and infinitely scalable...
... and it obviates the whole "heavy JWT" issue before it starts....
Source: This is what I do day in day out in my day job....
I do it mostly so I don't have to repeat myself. :)
I use the clips so that others can gain from the kernals of wisdom those clips provide... without having to commit to some portion of an hour to find the kernal themselves.
Saves everyone time and enforces compliance to decisions made )
Also, of course, by manually editing down a deeply technical discussion from an hour to 20 minutes helps me REALLY listen and understand what the speaker is saying....and so it also helps me to continue improve my knowledge...
Can confirm the "new way of working" when it comes to video clips ...
I have made it a part of my worklife to share with co-workers EDITED video highlights of zoom calls and training sessions.
This includes conference talks I find on youtube (e.g. Kubecon talks) that I want to have colleagues view.
I can usually cut down an hour talk/call. to around 5-20 minutes of good high impact content.
Historically, I just record in the cloud on Zoom (using all the nice extra features around auto-transcript, recording speaker and shared screen separately, etc... ) and edit it in Adobe Premier.
I've got the manual workflow down where this is something I don't do every day.. but several times a week is fine. Editing ain't pretty, but it is effective.
Since the lockdown, I have been working on the other end of the "pipeline"... the INPUT to Zoom. After a couple of false starts (OBS, CamTwist, Wirecast...). I ended up implementing Ecamm Studio Pro....
This.
Just a few days ago I wasted a few hours playing with OBS, CamTwist, and a few other "chroma key capable apps"... all with no luck... Zoom's built in beats them all....
What I really would like to do is have my green screen capabiity regardless of the video conference app (e.g. Facetime, FB, etc)...
I ran into the issue with syphon and Camtwist... and I gave up :)
https://www.amazon.com/Fd-Companies-Spectacular-Dot-Com-Flam...