That site could use a little more. Maybe a count of how many in the current month and year, tallies for each year, maybe even trends. Could be nice. :)
This seems really low considering one of the early warning radars taken out cost around $1bil on its own.... and it's possible a second one was at least damaged. (one in Qatar the other in Bahrain)
This is a Keynesian argument, which has largely been disproved. Keynes famously said if you just paid people to dig holes and fill them back up again, that this would be net stimulative to the government. It works until it doesn't work, because digging holes, as you can reason from common sense, does not actually create value.
This U.S. operation is meant to bomb the Iranians into the Stone Age, so presumably THAAD-level air defense wouldn't be needed again. The Qataris, Saudis would have sold off to South Korea, Taiwan if they wanted.
Possibly. There are a lot of things around that story that seem very off
Aside from the obvious bad AI images floating around the one credible looking video shows a shaheed flying into a radome. A Radome in the middle of a bunch of buildings. You don't put radars in between buildings. And if it's a phased array I don't think it would be in a round Radome either.
They seem to have hit something of value, but don't think it was a 1bn radar
Everything around this smells like the Iran hilariously oversized F35 misinformation
We do have actual video of that one radome in Bahrain getting directly struck (from multiple angles). It's possible it was a satellite communication antenna and not a radar.
But the still images shown with before/after are AI generated. (the surrounding buildings are completely different in the before/after image).
I've found that a bare repo over SSH is the simplest way to keep control and reduce attack surface, especially when you don't need fancy PR workflows. I ran many projects with git init --bare on a Debian VPS, controlled access with authorized_keys and git-shell, and wrote a post-receive hook that runs docker-compose pull and systemctl restart so pushes actually deploy. The tradeoff is you lose built-in PRs, issue tracking, and easy third party CI, so either add gitolite or Gitea for access and a simple web UI, or accept writing hooks, backups, receive.denyNonFastForwards, and scheduled git gc to avoid surprises at 2AM.
I'm going to trust the constant stream of updates from the company itself which shows exactly what went down and came back up rather than a random anecdote.
Recent years have shown this to be the wrong prediction strategy. The reason seems to be an incentive imbalance where there are quite a few reasons for companies to lie (including their own CLAs) and not a lot of repercussions for doing so (everybody competes on lock-in, not on product). Of course, the word-of-mouth approach is also exploitable by dishonest actors, but thus far there doesn’t look to be a lot of exploitation going on, likely because there’s little reason to bother (once again, lock-in is king).
This seems intelligent, after all companies are incapable of making errors in reporting and also have absolutely no incentive to lie about stuff like that. Those 500 errors others have reported as experiencing must have just been the wind.
I rarely successfully get Codeberg URLs to load. Which is sad because I actually would very much like to recommend it but I find it unreliable as a source.
That being said, GitHub is Microsoft now, known for that Microsoft 360 uptime.
I have never had this issue. IIRC Codeberg has a matrix community, they are a non-profit and they would absolutely love to hear your feedback of them. I hope that you can find their matrix community and join it and talk with them
The ThinkPhone is an exception, yeah. It’s similar to older Android One phones like their Moto X4. Not different because you are in EU, US models get same treatment.
The razr and edge lines do not get as reliable monthly updates and ship with bloatware.
No, they raise price because they can and demand isn’t showing signs of stopping despite increased prices. This won’t affect whether there’s a shortage or not, besides we’re not talking direct to consumer float product, they inked commitments.
If they didn’t have a documented history of running cartel price fixing schemes for LCD/OLED display tech, NAND, and DRAM, I’d maybe agree with you but we have the history. They cry every time about China ‘dumping’ for not going along with the racket.
> All of these devices lie to me, that I lost less than 20% of battery health. Where in reality it’s somewhere between 25-50%, and when they wouldn’t pretend that maximum output is any way a good indicator of the real battery life, aka how long you can use a device.
FWIW, I've only directly witnessed this so far on Oneplus devices, others have remarked the health gauge on these seem to use gacha mechanics where health % will be all over the place. (like >10% variability). I have theories as to why this happens, it's in firmware not OS as LineageOS shows same behavior.... but tough to really know for sure if this was by design or not.
Oh and charge thresholds only do so much, heat kills batteries reliably fast. Deep discharges under 20% or so seem to run more risk of electrolyte breakdown. Don't fear fast charge in bulk charge range, it causes less wear than other factors. I slammed the 65W charge into my 8T's and still got years of >80% battery, replacement wasn't too hard to do on these.
reply