The Indian press knows it is a bottom feeder and doesn’t try not to be which gives space for critical thought to emerge (even if it masked as extreme cynicism - “everyone is corrupt”) which results in extreme skepticism of everyone.
Sounds like some crazy level of meta where your brilliance is applicable to any pair of mega corps...which I don't buy.
The other day, I attended an open mic in my hometown and, still buzzing from the experience, wanted to search my hometown's biggest sub to see what they were saying about that open mic venue.So, I visited the sub and typed in the name of the venue in the search box. Just the name, mind you - no reference to open mics or jam sessions or whatever. The name is something like "bojoboes" which also...
Not trolling, genuinely impressed.
You still have to protect the DO through some sort of auth and/or rate limits.
Don’t see how any of these issues are unique to DOs.
But you don’t.
If I have the entangled version of the MEASURED byte and measure, only I know I’ve measured it. The corresponding MEASURED particles on your side still appear fuzzy to you because you haven’t measured them. If you measure them, they will reveal their state which correlates to mine BUT that doesn’t tell you if I have already measured my side of byte or not.
In effect, the heads/tail coin on your side is still spinning even after I have grabbed my side of the tail/head coin.
You may get HEAD as your result but that only tells you that I will get TAIL when I measure on my side, not that I have measured it already.
If you and I agree to measure at the same time, then I will know your state by determining mine but this is the same as knowing your state because I know how a two sided coin works, not FTL.
Lots of options here.
We need embeddings to give relatedness across axes like synonymity etc.
What is fructose doing extra here? It’s like productising copy&paste which every modern OS has, no?
For now, I figured I’d have an BEFORE UPDATE trigger which compares the md5(NEW.privileges::text) with md5(OLD.privileges::text) and raises an error if they don’t match.
Not sure how to bypass the trigger for service accounts.
Say you have a user “profile” which includes their privileges - like say a column named “privileges” which is some JSON object denoting what they can/can’t do.
Even with RLS, how do you ensure that a user can’t simply make a curl call with their own JWT to elevate their own privileges?
Basically, how to enforce column level security?
The best thing I can think of is to place “privileges” in a child table and only let the service account update that table.
In a macabre way, maybe suicidal ideation due to suppressed emotions is nature's way of managing male populations? What if men stopped killing themselves because they felt safe sharing their feelings? What if that led to testosterone fueled "musth" rages where men started to go on rampages just to let off steam? That world would be worse for everyone involved.
They wouldn’t be wasting all that time and money if the machine could self reflect.
Didn't they, one by one, stop doing business with him? That's pretty damning. Plus, his guilt was proven in a court of law. Does it matter that no bank took him to court before this? Look at the size of punishment - some $350M over the course of the lifetime of his company.
Could a bank have looked at the number and decided that going after Trump for an average amount of 5-10 million dollars every year wasn't worth it? It's just better to stop doing business with him. It isn't like Trump was stiffing them for a billion dollars a year.
> TDS having judge
NOW we are reaching banana republic status when regular people like us start doubting the trustworthiness of institutions like the court system with no evidence of corruption.
Wondering if you have the same concerns about the Delaware DA (Trump appointee) prosecuting Hunter Biden or Richard Hur (R lawyer) claiming Biden has poor memory and is easily confused. Are they suffering from BDS or are they just telling it like it is? And what makes you sure that either answer you choose will not be contested by someone else like you?
> neither should you
Like I said before, I'll take a judge's opinion on this than wakawaka28's.
Trump is on record - in the 2016 presidential debates, no less - claiming that gaming the system (by not paying his fair share of taxes) makes him smart.
Not prosecuting him and holding his feet to the fire is a worse look for NYS/NYC. Not showing undue deference to a former president is actually something the state should be very proud of.
It’s the opposite of banana republic level corruption when you realise that they’re aiming for the (former) king and can’t afford to miss…which they aren’t.
For example, I’m working on a pay-as-you-go SaaS - so the probability of using the SaaS while your account balance is low is 1-SD away from the happy path.
Figuring out if the user has JavaScript enabled (SaaS is an SPA) would mean the user first signed up with JavaScript enabled, then disabled it. Id put it at 3-SD away from the happy path.
Keep doing this and work on the bugs nearest to the happy path.
Of course, the 1-SD, 3-SD estimates are just hunches.
It’s like me saying “McDonalds has stopped selling hamburgers” and expecting you to magically understand that this statement is about Indian McD’s and not American McDs.
Right now, it’s scary to want to approach someone only to risk getting roasted for being a creep, barking up the wrong tree, and the myriad other reasons why people you want don’t want you.
It has to be thing everyone does - somewhat like bar hopping on a weekend. You know you’re at the bar to find someone and so is everyone else.
There are quite a few moving parts -
1. Route 53/AWS SES rules to handle Inbound emails
2. S3, Lambdas, and Step Functions to process emails into json objects
3. Cloudfront distro and behaviors to handle content delivery
4. Aws Cognito to handle login
This probably needs an accompanying blog series just to explain how everything works with each other.
If you’re interested, I’ve written a bit about it on https://pretzelbox.cc/blog which dogfoods the above product.
If there’s genuine interest, I’ll be happy to open source it.