I’m so confused by this submission. It’s not a guide but a collection of notes from someone (in china) customizing a oneplus build. There’s some useful info there but only if you’re already at a point where you’re comfortable running your own compiled full vanilla builds.
I don't use lineage OS myself, but I thought the same as I read the first few sections of this article. This "guide", if anything will just confuse the less tech savvy users rather than help.
wiki.lineageos.org has specific install instructions for every phone/device they support, I have no idea why you would choose to follow anything else.
just as an example, for the Nintendo switch v2(devices built after the homebrew method was patched) can be found at:
> wiki.lineageos.org has specific install instructions for every phone/device they support, I have no idea why you would choose to follow anything else.
Ironically, the Switch 2 page you linked on their wiki mentions a few different install methods and locations and goes on to say about one of those:
> if you wish to install Android to the eMMC, you will need to consult external resources
So it seems that there are indeed cases where you have to follow other things than the guides in the wiki, even for supported devices.
None of the missing ones have proper, official, upstream LineageOS support. If you install LineageOS on these, you install somebody's own, personal fork of LineageOS. Which might be totally fine, of course. But because of the necessarily different signing keys alone, it's a (potentially) very different thing.
Seems like a typical blog post. Doesn't hurt to start with something like that, but they explicitly refuse to link to "official" site, stating it's garbage. Trash it all you want, but at least link to the trash so readers can judge for themselves, since the author is a self-proclaimed noob.
If it doesn’t overshoot it’s fine. Modern low self discharge (lsd) nimh’s like eneloops do not like to be held on indefinite trickle charge or be overshot. Older nimh were less picky about overcharge so long as current was below its reabsorption rate.
But really thinking about it, this method doesn’t match up with how I’ve experienced nimh behaving on a charge. Intuitively, I want to say this will cause some (reversible) loss of capacity due to not fully charging the cells. It probably works best on new-ish high quality cells, ones with a few full cycles on a good charger. negative delta charge detection won’t work here.
It's almost as if they weren't lying when they said dropping it in the phone was a waterproofing measure. I guess people aren't dropping their laptops in pools all the time.
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)
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).
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
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 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
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.
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.
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).
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.
Go to https://wiki.lineageos.org if you want to install and/or compile for a phone.
reply