Hanging on in quiet desperation is the English way
Hanging on in quiet desperation is the English way
I manage a stack like this, we have dedicated hardware running a steady state of backend processing, but scale into AWS if there’s a surge in realtime processing needed and we don’t have the hardware. We also had an outage in our on prem datacenter once which was expensive for us (I assume an insurance claim was made), but scaling to AWS was almost automatic, and the impact was minimal for a full datacenter outage.
If we wanted to optimize even more, I’m sure we could scale into Azure depending on server costs when spot pricing is higher in AWS. The moral of the story is to not get too locked into any one provider and utilize some of the abstraction layers so that AWS, Azure, etc are just targets that you can shop around for by default, without having to scramble.
This is great and all, but what I really need is an alternative picture of shel silverstein to put on the back of the book.
Yes, I have no clue how she felt about the article from 2000, and obviously reading it with a 2024 lens is not fair to the original author. I am happy for her that the obituary didn’t deadname her like the original article did, and hope that she would have been ok with the pronouns used the way they did pre/post transition.
You’re right, very weird use of pronouns in the obituary. I can only imagine that most of it was lifted from the article from 2000. That doesn’t excuse misgendering someone, they could have updated it for 2024.
“I wouldn’t go up there. It’s really narrow.”
It has its downsides as well
Leaving a bar to catch a train and I did this when closing my tab. Ended up in a conversation and missing my train.
Does Microsoft’s GitHub offer any pre-receive hook configuration to reject commits pushed that contain private keys? Surely that would be a better feature to opt all users into rather than Windows Copilot.
Unless it’s literally no effort to maintain extensions that use both, a large portion of maintainers will develop what has the largest market share. Sure for uBlock Origin, there’s enough momentum to maintain a v2 version for Firefox, but for a new extension with one developer, it’s unlikely that they’d make two versions.
Either this backfires, and Firefox ends up having the better extensions using v2 manifest, or new extensions will be developed with the limitations of v3 and Firefox users will have an unnecessarily neutered experience as Chrome users.
I’m definitely never logging in to a Google service while using Firefox.
Could you elaborate on this? Why not use Firefox for logging into Gmail, Youtube, etc
She found an infinite money glitch
They bought a company named Keyhole in the early 2000s
https://www.cnet.com/tech/services-and-software/google-buys-satellite-image-firm-keyhole/
This argument implies there’s an easy way for you to perform the reproducible builds on iOS, but it’s quite involved and requires a jailbroken iPhone. Overall this is more a limitation of apple and not signal.
Even if you were able to perform a reproducible build of Signal on a jailbroken iPhone, there’s no way to confirm that the stock iOS Signal app will match, or has a backdoor that got added in a supply chain attack that only is delivered to non jailbroken phones. You could use a jailbroken iOS device, but then it could be lagging behind updates and be even more vulnerable from zero days.
The real pressure here should be on Apple to provide a way to verify a build of an open source app matches what is being installed via the app store, but for some reason this is being framed as a Signal issue, which is disingenuous.
Why use JustWatch.com when you can follow this guide to know where to watch King Kong vs. Godzilla (1962)
It feels like this needs to be managed on an instance by instance level and not post to post.
Exactly, with Nintendo’s existing IP and old gamers dying, they need a way to get younger generation exposed to what kids in the 80s and 90s grew up with and make sure that it’s plastered on all the streaming websites to get maximum exposure.
It’s a device to make phone calls, but that’s not important right now.
Not having reproducible builds is definitely weird though. Does anybody have more information on that?
They boast this as a feature, but on the instructions for how to do this for iOS, even Telegram admits “As things stand now, you’ll need a jailbroken device, at least 1,5 hours and approximately 90GB of free space to properly set up a virtual machine for the verification process”. Browsing the steps, it’s extremely complex, and doesn’t seem like something that is very user friendly and that you’d do weekly or monthly when a new version is released.
On the GitHub issue linked to in the body, it’s disingenuous to claim they refused to implement this, and that the technical hurdles Apple has in place make this extremely difficult which halted progress. In the community forums where the conversation was moved to, someone pointed out that even if you were to reproduce it on a jailbroken iPhone, that there’s no way to confirm that non-jailbroken iPhones aren’t receiving a version with a backdoor.
And even if you are using a jailbroken device exclusively and can confirm the reproducibility of the iOS app, then the risk becomes the latest available jailbroken iOS could be outdated from the real versions, and you’d have other issues with not receiving timely security updates. This same issue applies to Telegram also.
Usually NYT sets a cookie to track how many free articles you read and once you exceed that, you get the paywall. The bots probably don’t set/send the cookies, so NYT doesn’t block them. Also, I’d imagine the bots are coming from various different IPs so even server side blocking based on IP wouldn’t block everything and eventually the bot would get to the article. User Agents can also be spoofed.