Ken_Adler
Joined 11 years ago
Joined 11 years ago
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.
Search for "2022 ACA Income limits [your state]"
Here is the 2022 chart for California: https://www.coveredca.com/pdfs/FPL-chart.pdf
https://www.orgbook.gov.bc.ca/en/home
This link has a search for Cannabis in BC's org book
https://www.orgbook.gov.bc.ca/en/search/name?query=cannabis&...
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.
Check out the Good Health Pass Interoperability Blueprint for one such Governance Framework which will publish by end of month. https://wiki.trustoverip.org/download/attachments/76241/GHPC...
https://www.thoughtworks.com/news/thoughtworks-mourns-aaron-...
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....
It's interesting how different people process information.
All I can say is that it works for me.... and I find it to be highly impactful on my co-workers etc.
There is something about capturing nuance that "multimedia" really helps with....
So my mission is to reduce the effort it takes for me to do this to less then it takes to just write up and share notes...
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...
https://www.amazon.com/Fd-Companies-Spectacular-Dot-Com-Flam...