> Restricted Jurisdictions. You acknowledge and agree that you are not permitted to access, use or trade with the Contracts on the Platform if you are residing in, a citizen of, organized in or located in the following jurisdictions (collectively, the “Restricted Jurisdictions”): Australia, Belgium, France, Germany, Italy, the Netherlands, Ontario, Poland, Quebec, Russia, Singapore, Taiwan, Thailand, the United Kingdom, the United States; or a jurisdiction or territory that is the subject of comprehensive country-wide, territory-wide, or regional economic sanctions by the United States, including but not limited to Iran, Syria, Cuba, North Korea, and the Crimea, Dontesk and Luhansk regions of Ukraine.
Very confusing. Polymarket doesn't allow US use/users. How are folks in the US participating on Polymarket? (VPNs and the like reportedly don't help either due to KYC policies.)
Looks cool, but this site is a bit difficult for me to grok.
I think the table might be slightly inside-out? The Status column appears to show internal pipeline states ("Pending", "In Review") that really only matter to the system, while Findings are buried in the column on the far right. For example, one reviewed patchset with a critical and a high finding is just causally hanging out below the fold. I couldn't immediately find a way to filter or search for severe findings.
It might help to separate unreviewed patches from reviewed ones, and somehow wire the findings into the visual hierarchy better. Or perhaps I'm just off base and this is targeting a very specific Linux kernel community workflow/mindset.
Reminds me a bit of the Park of Aging in Miraikan The National Museum of Emerging Science.
I remember when staff casually handed me a paper brochure near the area dedicated to aging that when opened was blurry and difficult to read. I was confused. When it finally dawned on me this was one of their simulations of old age I never laughed (at myself) harder. Such a fun and educational experience highly recommend for all ages.
The Copilot Runtime APIs to utilize the NPU are still experimental and mostly unavailable. I can't believe an entire generation of the Snapdragon X chip came and went without working APIs. Truly incredible.
I believe cyber cafes in India must verify identity via ID before allowing internet access and maintain logs, browsing history, etc. for at least one year.
Somewhat along that line of thinking, I've wondered if my visual perspective was similar to a 3D game engine camera. And if upon death, it switched to a new entity.
I got the same notification, US business owner here. In my case, I did not change my address (or anything else). But I suspect their system is regularly looking for work and can't handle DBAs well. To avoid this exact scenario, I was on their butts and uploaded every document I had. Eventually I was escalated and they did something, but I still can't enable their APR option due to some error somewhere. No one seems to know what. I'm very concerned one day I'll wake up to the same fate as the author.
It's a shame because I really love using the Wise website, app, payment system, and even the physical card (esp. in Japan).
Happy to work with anyone over there if they read this and want to dig in.
Was hoping they outlined their approach to handling potentially compromised packages running on dev machines prior to even shipping. That seems like a much harder problem to solve.
I have the previous generation Meta Ray-Ban glasses and they're great, but I wish I could use the underlying tech for... something more useful. It has no API, no extensibility options, nada. I--and my friends--don't use Messenger, Facebook, etc. I fear it'll be the same w/ the Ray-Ban Display, so I doubt I will be upgrading. Such a shame.
In July, packages were loading malicious DLLs (on Windows targets) [1]. It doesn't appear Lavamoat would help in that scenario. Is that right? If so, how do you mitigate this? Run everything in a container?
Do backups get pruned over time? Is there an expiration? I don't think folks want old lost-key backups sitting around forever for quantum to catch up, right?