I wrote about the UniSuper issue at the time: https://danielcompton.net/google-cloud-unisuper. It was a pretty nasty bug where their VMWare environment was created with a one-year expiry date, but was one "resource" from the perspective of Google Cloud.
GitHub has automatic secret scanning on all public repositories which notifies AWS if access keys are pushed. I would have expected these tokens to be immediately revoked by AWS. Is there something different about GovCloud access keys so they weren't detected?
Could you please pass on feedback to the team that the git diff view is very hard to read for red/green colourblind users like myself? Colour scheme like GitUp.co is very readable for me.
I'd be very interested to know how they produce it if the formula is so tightly held. At some point people need to be purchasing the ingredients and mixing them together.
The intention of OrioleDB is not to compete with Postgres, but to make Postgres better. We believe the right long-term home for OrioleDB is inside Postgres itself. Our north star is to upstream what’s necessary so that OrioleDB can eventually be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres.
I listened to https://www.localfirst.fm/18 recently from Electric-SQL. One of the things James mentioned was that Electric lets you use commodity CDNs for distributing sync data, which takes the load off your main Postgres and servers.
This seems like a good pattern, but of lower value for a SaaS app with many customers storing private data in your service. This is because the cache hit-rate for any particular company's data would be low. Is this an accurate assessment, or did I misunderstand something?
Will this be partially available from the Claude website for connections to other web services? E.g. could the GitHub server be called from https://claude.ai?
https://where.durableobjects.live is a good website that shows you where they live. Only about 10-11% of Cloudflare PoPs host durable objects. Requests to another PoP to create a DO will get forward to one of the nearby PoPs which do host them.
The issue here is that if company.com does not use Google Workspace and hasn't claimed company.com, then any employee can sign up for a "consumer" Google account using [email protected].
There are legitimate reasons for this, e.g. imagine an employee at a company that uses Office365 needing to set up an account for Google Adwords.
I don't really understand what this is offering beyond Cloudflare's recent release of running SQLite in durable objects: https://blog.cloudflare.com/sqlite-in-durable-objects/. Is it about providing an external interface to Cloudflare's SQLite databases?
The Surface Laptop scored 1,745 on the Procyon AI Score, while the MacBook Air managed 889. Qualcomm’s Snapdragon X Elite has 45 TOPS of AI acceleration performance, much more than the 18 TOPS found on the M3.
TOPS (Trillion Operations Per Second) is a meaningless score without including the precision. Are they INT4, INT8, INT16 or FP16? Microsoft's qualifications for a Copilot+ laptop require 40 TOPS at INT8: https://www.theregister.com/2024/05/21/qualcomm_windows_micr.... The new Snapdragon X Elite can do 45 TOPS at INT8.
Exposure to RCS from engineered stone causes silicosis typified by a faster onset and more rapid progression than that caused by RCS [Respirable crystalline silica] from other sources, including natural stone.
When engineered stone is processed, the dust generated contains higher levels of RCS, and that RCS has different physical and chemical properties that likely contribute to the more rapid and severe disease. There is also evidence to suggest that other components of engineered stone may contribute to the toxic effects of engineered stone dust, either alone or by exacerbating the effects of RCS.
...
The increased risks posed by RCS from engineered stone, increased rate of silicosis diagnosis amongst
engineered stone workers, and the faster and more severe disease progression amongst this group,
combined with a multi-faceted failure of this industry to comply with the model WHS laws means that
continued work with engineered stone poses an unacceptable risk to workers. The use of all engineered
stone should be prohibited.
> A total of 12 successful prosecutions have been reported since 2021,
with many related to the uncontrolled processing (dry cutting) of engineered stone materials
A general issue I have with GCP docs is that they are overly implicit. Often the interaction of two features is implied but not specified. Another issue I have is when implementation details are waved away rather than explained. It adds up to an experience where I am trying to read between the lines of the GCP docs for a feature to understand what is really happening.
AWS docs are the opposite. They are often very long and verbose, but once you read the whole manual, you can be guaranteed to have a good understanding of the service.
My advice for the Google team would be that if you are ever writing documentation and ask yourself “does the customer really need to know about this?”, the answer should always be yes.
Presumably GitHub/GitLab support is coming, but this is quite a limited product at the moment. It doesn’t even support their own Cloud Source Repositories.
You can version the Terraform configuration, either in a public Git repository or in a Cloud Storage bucket. Use Object Versioning to version configurations in a storage bucket.