A lot of Chinese food add sugar but not fruit, since fruit is usually too sweet. Usually anything with msg would also have a few grams of sugar in it as well.
The goal is to add just enough sugar that it tastes different but you can't tell it's sugar.
It's homemade food. Just go with whatever you'd like. Though it looks like YouTube recipe videos add potatoes and red peppers for the simmer.
I just did this the way my grandpa used to make them. Which was probably not the best but very nostalgic to me. There was one time he subbed the beer with baijiu, with disastrous results (the whole chicken turned bitter).
Toss some crushed garlic and ginger slices in a wok. Add the chicken and soy sauce. Once everything is seared nicely, submerge the chicken in beer. Add salt and white pepper to taste, also add about 30g of sugar. Bring it up to a boil then simmer for 60min.
This was done with skin on drumsticks, hence the scoring on the chicken. Otherwise the skin might tighten and the meat ends up bland
Response to 1: funny thing is that one of the ID verification issues I specifically had is with Hetzner. They need to do a ID verification, recognizes my address is from Country A outside of the EU, so it goes through a Country A specific verification. Then rejects my ID because it's a rare form of ID in Country A. I also have an ID for Country B but they won't recognize it with a Country A address.
Response to 2: I'm specifically referring to people residing in the EU for this one. People in the EU that "slip through the gaps" since their ID is somewhat uncommon, thus getting locked out of digital services since they can't validate and obtain a digital ID easily.
Response to 3: the counterpoint here is network transport protocols, such as TCP and UDP. At this point, it is no longer possible to build new protocols or modify these protocols because of how entrenched the infrastructure hacks surrounding these protocols are, such that no new protocol header would be possible to get through the Internet without it being dropped by middleboxes. I'm suggesting utilizing this technical moat as a feature here: have a simple proposal spread so wide that it becomes almost impossible or economically unfeasible to switch to something invasive.
My issue with 4 is more about current implementation rather than the proposal. So far, the main (or only functional implementation, I'm not sure) is the one that depends on Google attestation. While this could change, I'm not the biggest fan of trusting something to "policy/proposals". X509 is robust, has key management sorted out, and doesn't have this specific issue. While anyone can create a cert, that doesn't mean the cert is useful if it's not signed by an approved CA.
I'll start off by saying I'm not super familiar with the EU proposal for digital IDs (other than looking at a few articles here and there), but
I'm not in the EU. The EU proposal is tied specifically to the EU. And without documents that establish physical presence in the EU it makes it hard to interact with EU services. A cert with an email doesn't have this problem.
There are more problematic cases than "non-EU citizen outside of the EU want to access EU services". There are always edge cases where there's a piece of document that establishes the person is legally allowed to be here but is glossed over as an "ID". Usually, you can present these in person and a human would be able to check it. It's much harder to convince an automated machine to do so, especially when it isn't in a drop down list. Which means no digital ID for this person (since the system can't verify). This is not hypothetical. I have actually encountered this myself outside of the EU. Impossible to submit rental applications, trade-ins at Best buy, rent cloud servers, etc. A verification system backed by multiple non-government entities can alleviate this by 1) only verifying age and 2) verifying age through different methods, sometimes even through human vetting.
Data protection is governed by policy in the EU proposal. Policy can change. It's a lot harder when something is technically impossible by design. A cert with only an email cannot produce a name in it, even if storage was implemented incorrectly.
My understanding is that while the digital id wallet is supposed to be open source, currently it depends on Google attestation framework and can't even work on GraphineOS. You don't run into this problem with a file.
Honestly I think what is needed here is something similar to TLS: build a chain of trust with multiple "authorities" that can validate your age.
Then we can potentially have open identity issuers that validate age, minimum/no logging, ram servers, periodic power cycles, and independent audits. Assign the cert to an email address or something. Only include age >16/18/21 and a expiry date.
There would be a problem with tracking accounts across services, but if the cert name is only tied to an email, it wouldn't offer any more tracking info than the email used tied to your online accounts.
Tl;dr one of the founders is holding up the infra not allowing any change. According to someone who worked on Manjaro, it was trivially easy to get this fixed, but that single person simply wouldn't approve it. Last I checked they sent the founder an ultimatum: either hand over the project or see the staff walk. I suppose the staff walked.
I don't. The tech I cleared out is old enough to still be useless even in the current landscape. Mainly boiling down to:
It's battery tech so old the cost of a replacement battery is more than the tech itself
It uses connectivity (wired or wireless) that is no longer compatible with current tech without maintaining a separate set of workarounds (I'm keeping the PS/2 keyboards though)
The compute is so limited it's easier to spin up a tiny container on my existing hardware
The last phone I threw away was so old it literally couldn't run RPGMaker without lagging on every tile move. It did not have USB Type-C HDMI output due to hardware limitations and relied on Google Chromecast only. At that point, there really is no reason to keep it anymore.
If you want people who can actually fix things, why not either 1) pay a higher wage to attract talent or 2) pay a high wage so people can spend time to improve their skills?
But in the case he did lunge...
Can the reporter parry and counterstrike?
Hmm... Gotta disagree on that one. Its common in Asian cuisine and I love the texture.
Cheese though... That's a no for me.
No plans, just actions.
Not really? One is a hot dish and the other is a cold dish. They're completely different.
If you copy the Chinese name there's a bunch of videos in Chinese, a lot of them seem to be from Taiwan.
A lot of Chinese food add sugar but not fruit, since fruit is usually too sweet. Usually anything with msg would also have a few grams of sugar in it as well.
The goal is to add just enough sugar that it tastes different but you can't tell it's sugar.
Biblically accurate chicken with that number of legs.
It's homemade food. Just go with whatever you'd like. Though it looks like YouTube recipe videos add potatoes and red peppers for the simmer.
I just did this the way my grandpa used to make them. Which was probably not the best but very nostalgic to me. There was one time he subbed the beer with baijiu, with disastrous results (the whole chicken turned bitter).
Nope. 醉鸡 is its own higher end thing. 啤酒鸡 is more casual homemade food.
Looking at YouTube, I probably should have added some peppers for color. Though I was more trying to use up the beer since it was about to expire...
Toss some crushed garlic and ginger slices in a wok. Add the chicken and soy sauce. Once everything is seared nicely, submerge the chicken in beer. Add salt and white pepper to taste, also add about 30g of sugar. Bring it up to a boil then simmer for 60min.
This was done with skin on drumsticks, hence the scoring on the chicken. Otherwise the skin might tighten and the meat ends up bland
Response to 1: funny thing is that one of the ID verification issues I specifically had is with Hetzner. They need to do a ID verification, recognizes my address is from Country A outside of the EU, so it goes through a Country A specific verification. Then rejects my ID because it's a rare form of ID in Country A. I also have an ID for Country B but they won't recognize it with a Country A address.
Response to 2: I'm specifically referring to people residing in the EU for this one. People in the EU that "slip through the gaps" since their ID is somewhat uncommon, thus getting locked out of digital services since they can't validate and obtain a digital ID easily.
Response to 3: the counterpoint here is network transport protocols, such as TCP and UDP. At this point, it is no longer possible to build new protocols or modify these protocols because of how entrenched the infrastructure hacks surrounding these protocols are, such that no new protocol header would be possible to get through the Internet without it being dropped by middleboxes. I'm suggesting utilizing this technical moat as a feature here: have a simple proposal spread so wide that it becomes almost impossible or economically unfeasible to switch to something invasive.
My issue with 4 is more about current implementation rather than the proposal. So far, the main (or only functional implementation, I'm not sure) is the one that depends on Google attestation. While this could change, I'm not the biggest fan of trusting something to "policy/proposals". X509 is robust, has key management sorted out, and doesn't have this specific issue. While anyone can create a cert, that doesn't mean the cert is useful if it's not signed by an approved CA.
I'll start off by saying I'm not super familiar with the EU proposal for digital IDs (other than looking at a few articles here and there), but
I'm not in the EU. The EU proposal is tied specifically to the EU. And without documents that establish physical presence in the EU it makes it hard to interact with EU services. A cert with an email doesn't have this problem.
There are more problematic cases than "non-EU citizen outside of the EU want to access EU services". There are always edge cases where there's a piece of document that establishes the person is legally allowed to be here but is glossed over as an "ID". Usually, you can present these in person and a human would be able to check it. It's much harder to convince an automated machine to do so, especially when it isn't in a drop down list. Which means no digital ID for this person (since the system can't verify). This is not hypothetical. I have actually encountered this myself outside of the EU. Impossible to submit rental applications, trade-ins at Best buy, rent cloud servers, etc. A verification system backed by multiple non-government entities can alleviate this by 1) only verifying age and 2) verifying age through different methods, sometimes even through human vetting.
Data protection is governed by policy in the EU proposal. Policy can change. It's a lot harder when something is technically impossible by design. A cert with only an email cannot produce a name in it, even if storage was implemented incorrectly.
My understanding is that while the digital id wallet is supposed to be open source, currently it depends on Google attestation framework and can't even work on GraphineOS. You don't run into this problem with a file.
Honestly I think what is needed here is something similar to TLS: build a chain of trust with multiple "authorities" that can validate your age.
Then we can potentially have open identity issuers that validate age, minimum/no logging, ram servers, periodic power cycles, and independent audits. Assign the cert to an email address or something. Only include age >16/18/21 and a expiry date.
There would be a problem with tracking accounts across services, but if the cert name is only tied to an email, it wouldn't offer any more tracking info than the email used tied to your online accounts.
iirc the last time someone parked a fleet there two destroyers were lost.
If it happens again, it would be the most excitement the local sheep population has seen since 1982.
This came up last time the cert expired iirc.
Tl;dr one of the founders is holding up the infra not allowing any change. According to someone who worked on Manjaro, it was trivially easy to get this fixed, but that single person simply wouldn't approve it. Last I checked they sent the founder an ultimatum: either hand over the project or see the staff walk. I suppose the staff walked.
Doesn't happen with Antergos either.
I mean, I've gotten a NXDomain error ever since they shut down, but at least it's not a certificate expiry!
It's not a "game", it's a "product".
And they will do the same when food and water becomes a "product" too.
And here's the whole pot:
Tangentially related: https://www.youtube.com/watch?v=rEUHLm27FMM
I don't. The tech I cleared out is old enough to still be useless even in the current landscape. Mainly boiling down to:
It's battery tech so old the cost of a replacement battery is more than the tech itself
It uses connectivity (wired or wireless) that is no longer compatible with current tech without maintaining a separate set of workarounds (I'm keeping the PS/2 keyboards though)
The compute is so limited it's easier to spin up a tiny container on my existing hardware
The last phone I threw away was so old it literally couldn't run RPGMaker without lagging on every tile move. It did not have USB Type-C HDMI output due to hardware limitations and relied on Google Chromecast only. At that point, there really is no reason to keep it anymore.
Play minimum wage games, win minimum wage prizes.
If you want people who can actually fix things, why not either 1) pay a higher wage to attract talent or 2) pay a high wage so people can spend time to improve their skills?