https://www.seriouseats.com/why-you-should-refrigerate-tomat...
451 karma · joined October 9, 2014
https://www.seriouseats.com/why-you-should-refrigerate-tomat...
My understanding of TOAST is that it itself is just a bunch of rows in a toast table that split the compressed "row" or in this case "1000 rows of 1 column" across as many rows as required to store the data whilst remaining within the postgres page size limits (normally 8kb).
With the often quoted postgres per row overhead of 23 bytes~ which you would have to pay for each TOAST row as well, does this not add up and eat into your storage efficiencies? or does compression work so well that the 23 bytes x N rows (1 row pointing to toast + N toast rows) required to store the "row" isn't important?
Code is more upfront effort but more control and thus less fragility but more maintainable over time (if done right).
I imagine there are some/many situations where throwing many people at a problem is the “best” way and this would suit that quite well I guess.
Couple that with proof of identity being one of the few things that might have been issued 40, 50.. 60+ years ago (birth certificates) and never updated (unlike passports..) and when issued had no concept or sympathy that it might be used for digital verification in the future.
Without redefining the problem to avoid issues like birth certificates, i'm not sure this is solvable in the way stakeholders expect it to be. Stakeholders (like citizens paying for it) expect to be able to point technology at the problem and have it solved, 'its just an app right?' or 'lets use biometrics!' but so many other things have to adapt to make something like this successful.
Estonia had an interesting approach where they just issued everyone smartcards/certificates and used that as proof, this bypasses the 'birth certificate' problem but is expensive (Estonia has smallish population, newish government so ok) but such an approach itself has a root of trust problem.. who do I issue the smartcards to? It isn't directly transferable to other countries/governments.
You work around the root of trust problem by creating exceptions and alternate paths to verification, maybe do it in-person for people with disabilities etc. But then how long does that take to roll-out? How easily abused is such a system? How many of the identity moment can I use it for? Is in-person verification trusted less?
It is very easy for the resulting system to be quite brittle too and not reflect real use-cases, real world identity moments are very diverse and often have more flex than you'd think and it is very difficult to carve out the right chunk of the identity problem to solve and which to leave behind and still create something that improves the ecosystem.
learnt through pain, built digitalid.com
Always surprised to see people resolving merge conflicts anywhere other than their IDE, IDE has the most knowledge about the inputs to the merge and your chosen resolution, why would you ignore that important info? (like.. does the resulting file compile? for ex..)
- transparent networking, i want to access kube services on 127.0.0.1, i'd rather not run a proxy/manage things myself - access to containerd socket to use non-rancher tooling, for image building etc.
early days for this project, i'll have to spin it up and see how it goes!
If you are reading files back out again too you can use cloudflare caching to speed things up, its a good combo.
But after much googling it appears not! Seems like a fairly simple additional variables aws could pass through and condition to support, so you can say “only allow this request if the signing time is < 1min ago”, closest you can get is that the policy is only valid after X date! Is a shame!
We compared Timescale, Clickhouse, Snowflake and Firebolt. Ended up really liking Firebolt, some amazing tech with a few roughedges (its pretty new), basically Clickhouse speed meets Snowflake simplicity definitely one to watch.
Good to see more things happening in this space.
AWS SDKs must be generated and they are mostly good but some of them like S3 are so heavily used they could have teams writing them no probs. GCPs are (or were?) super verbose which is a GRPC generation artifact, same as openapi.
Its not that finance get things done, its that they can prevent things being done entirely, or reduce funding/investment to the point they naturally peter out.
I'm picturing the StackOverflow problem where the accepted answer is actually wrong, and actively pushing it into more peoples code is just proliferating the problem into more places. Making people faster at building mostly the write but sometimes the subtly wrong thing.
They had a chance to try and help close that gap and even charge for it, I’d rather not have to setup macstadium, configure Anka controller and pull 20gb+ images.. just solve my problem for me..
I was disappointed that TerraPower in China never got going, bc trade-war. The inside bill's brain episode about it all was great.
In kind you can build container images into the single host, and avoid a container push/pull cycle. Any solns to that in vcluster?