This already "exists", go to a label, tick the top checkbox above all the rows, then "Select all 5,192 conversations in 'ThisLabel'", then "Delete".> The one thing I'll want is what we'll never > get which is just making it easier to delete > e-mails in bulk."Exists" in scare quotes because their own interface is absolutely atrocious for doing this, as on e.g. a label with ~50k messages (I was mass-deleting some large mailing lists recently) there's maybe a 5-10% change the operation will eventually finish, and not just leave it at ~45k or whatever.
But you can do this by setting up a local IMAP client and doing mass-deletes that way. Perhaps the easiest on e.g. *nix systems is to use isync (the "mbsync" command) to "sync" between two folders locally and remotely, with a rule saying "anything deleted locally, delete it on the remote too".
Then just sync between an empty local folder and your remote target folder, and it'll slowly grind through it. You can also use a local GUI E-Mail client, but most of those become slow/unresponsive with a mass-delete operation, whereas you can spin up multiple "mbsync" commands with retries.
Beware that GMail has (or did, last I tried this) some sort of per-account I/O limit or similar, so if you're doing background operations like this you might find the web interface (even on an unrelated computer/network connection) becomes slow or unresponsive.
I'm not putting cynical motivations past Apple, but you're reading too much (or too little?) into what Jobs said at the time.> Steve Jobs himself envisioned a > web app future as the future of[...]His remarks at the time of the initial iPhone release (with the benefit of hindsight) were clearly because they weren't ready to expose any sort of native API's.
Pissing on you and telling you it's raining was typical Jobs reality distortion field marketing, and not an indication that he actually believed it was raining.
If we're going to take this "packing problem" a tad more seriously, then the notion that someone might spend on the order of $2.5 billion on micro-SD cards for their station wagon (assuming 1TB at $100/card), but isn't in a position to contact an SD card manufacturer to solve this problem for them is a bit absurd.> he also addressed the packing problem, saying[...]- Fascinating, I wasn't aware of that. They still offer an "AWS Snowball", which is 200 TB instead of 100 PB, but around the size of half a full size suitcase instead of a semi truck. You then ship that back and forth.
If you need 100 PB then moving 500 of those around seems a lot easier for everyone involved than managing a special snowflake truck.
- I tried setting that up, but now the trucker's union is refusing to talk to me, citing concerns that the platters will all spin up due to road vibration, derailing the truck in a ditch due to the cumulative gyroscopic forces.
They remain unconvinced that chatGPT has told me it "should be fine", and have inquired as to whether I don't have better things to do than trying to win increasingly obscure and contrived arguments on HN. Please advise.
- Actually a shipping container full of micro-SD cards hurtling down the highway has lower overall bandwidth than a 56k modem.
That's because whoever's attempting to load an ideal 400 million micro-SD cards into one will take approximately forever carefully trying to line up even one row of them on the floor of a shipping container, before having the whole thing fall over like dominoes.
And even if they manage that, the whole thing will tumble over once they need to deal with the first row of the container's side corrugation. Nobody at the department of Spherical Cows in Vacuums thought to account for those dimensions[1] not lining up with the size of micro-SD cards.
If they do manage some approximation of this it'll take forever just to drive this down the road, let alone get the necessary permits to take the thing on the highway.
Turns out not a lot of semi truck trailers or roads are prepared to deal with a 40 ft container weighing around 100 metric tons (the weight of one packed to the brim with sand, a close approximation).
The good news is that such transportation gets more fuel efficient the longer the trip is.
The bad news is that the container will arrive mostly empty, as it's discovered that shipping container door panel gaps and road vibrations conspire to spread a steady stream of micro-SD cards behind you the entire way there.
Commuters in snowy areas held up behind the slowly moving "OVERSIZED LOAD!" with a mandatory police escort wonder if it's a trial for a new type of road salt that makes a pleasant crunchy sound as you drive over it.
Finally, an attempt to recover the remaining data fails. The sharding strategy chosen didn't account for failure due to road salt ingression into the container, cards at the bottom of the container being crushed to dust by the weight of those above, or that the leased container hadn't been thoroughly cleaned since last transporting, wait, what is that smell?
1. https://www.discovercontainers.com/wp-content/uploads/contai...
The reader is left to wonder what the software librarian at the Computer History Museum could have possibly found recently that warrants a placement ahead of Unix v4 in their project queue. A copy of Atlantian Unix from the ancient Library of Alexandria?> This is rare enough that I'm pushing the recovery > of it up near the top of my project queue.
Speculation: It was brought to Tesla after an accident, which inspected it, and quoted a repair price the owner didn't like, so his cousin Bob fixed it, but it's still marked as "HV needs inspection/repair" in Tesla's system?> how does Tesla know repairs > have been made after a minor > accident?- Neywiny's comment upthread isn't that you should use these without a BMS, but that the review is relatively less useful because it's stopping testing at a relatively high voltage. E.g. if you search for "panasonic_ncr18650b.pdf" you'll find that Panasonic's own datasheets use a cutoff of 2.5v.
- Some of us enjoy fixing things like these over and above the hypothetically fungible billable hour, and whether you can substitute some time in an evening with a billable hour or three is highly dependent on your employment situation.
But in this case the relevant cost under discussion isn't that of a replacement vacuum cleaner, but what value you assign to your house not burning down due to a crappy 18650 cell, or the anxiety of worrying that that'll happen.
- This may not be what you're asking, but it's rather trivial if you're setting up an SMTP gateway that proxies traffic to another SMTP that handles the IP address reputation management etc.
E.g. I do that with Exim on my Debian laptop and have it relay outgoing messages to Gmail's SMTP. It's great if what you want out of it is being able to send E-Mail while "offline", the messages will get locally queued until you've got an outgoing connection, much better than relying on individual MUA's to handle that, and it'll work with one-off invocations like piping to mail(1) etc.
Connect the + and - terminals with an appropriately sized resistor, it'll drain all the way to 0V.> How do you even drain a 3.7V lithium > ion battery below 3.3V?
Because you're not using the + and - terminals, you're using the + and - supply of a BMS, which is connected to those terminals. For this sort of testing you need to bypass the BMS, which'll have its own voltage cutoffs.> My devices that use 18650s will > not let them go below that.
How prices are determined in general isn't relevant to your claim that something is "very expensive currently because of X".> Technically it expensive because demand exceed supply.
What war was going on in August 2024 that wasn't going on in September and October 2024?> with the war that source was cut offI don't see why you're insisting on this passive and inaccurate description.
Someone unfamiliar with this might infer that Russia considered Helium a strategic asset and forbade its export, when the reality is that to the extent that your initial claim is in any way relevant to Helium prices, it's the other way around: The EU forbade the import of Russian helium.
- I'm aware of your and the GP's claim, I'm saying it doesn't survive contact with reality.
If you look at e.g. the per-dose price of insulin it's as low or lower in countries with single-payer universal systems, where someone requiring insulin is never going to have any idea what it even costs, because it's just something that's provided for them should they need it.
In that case it's usually some centralized state purchaser that has an incentive to bring prices down, or a government that has an overall incentive to keep the inflation of its budgetary items down, which ultimately comes down to public elections etc.
In any case, a much more indirect mechanism than someone who'd be directly affected paying the costs associated with the product, which directly contradicts this particular argument.
In reality, this claim doesn't survive a cursory glance at the OECD's numbers for health expenditure per capita[1].> The second you detach the consumer from the > price of something, even through an > intermediary such as health insurance, that > is when they stop caring about how much > something costs, and so the price jumps.You'll find that (even ignoring the outlier that is the US health care system) that in some countries where consumers bear at least some of the cost directly via mandatory insurance and deductibles, the spending per capita (and which survives a comparison with overall life expectancy etc.) is higher than in some countries where the consumer is even further detached from spending, via single-payer universal healthcare systems.
Or, the other way around, it's almost like it's a very complex issue that resists reducing the problem to an Econ 101 parable.
1. https://www.oecd.org/en/publications/2023/11/health-at-a-gla...
It's expensive (in Greece) because the EU added helium to its 14th package of sanctions in September 2024[1].> Helium is very expensive currently because of RussiaI'm aware of the ultimate reasons for those sanctions, but it seems weird in this narrow context to say it's "because of Russia". No, it's expensive because of the EU, which decided to make it expensive, unilaterally.
1. https://ec.europa.eu/commission/presscorner/detail/en/qanda_...
- Your site (if this is your YouTube video) indicates Bosch compatibility with gen 2 motors[A]. I'm curious as to:
1. It says "Protocol implemented = no", but "Powers bike = yes", you can power a Bosch gen 2 motor without implementing the protocol, presumably this is referring to the CAN wire on the battery.
2. Your battery kit is 316 EUR without cells, and your BMS spare part is 99 EUR. If you can talk to Bosch motors then presumably this is where that special sauce is.
I for one might be interested in just something that serves to talk with the Bosch motor, and allows one to provide any arbitrary 36v source, do you or anyone else make/sell such a thing?
E.g. for range extending a cargo bike I'd find the cost/weight ratio of a beefy ~1220 Wh AGM 12v car battery coupled with a boost converter much more appealing than something that emulates the form factor of a ~500 Wh Bosch battery with Li-Ion 18650 cells, the range more than makes up for the extra weight.
A. https://infinite-battery.com/pages/compatibility-guide-of-th...
I meant paid in the indirect sense of being the beneficiary of a loss leader for Microsoft.> I really would like to have been payed > to use Windows phonesI.e. I'm poking holes in your (somewhat unstated) premise that they'd already reached around 10% of marketshare, and could have just organically grown from there. As reporting at the time shows[1] the average selling price of these phones was €72.4.
So Microsoft (Nokia, but we all know who was really running/paying for the show) were spending a lot of money to buy themselves into the market, and just barely holding on to double digit market share for a bit there by subsidizing entry level phones.
1. https://www.theguardian.com/technology/2013/oct/01/microsoft...
- If "rapid reusability" was a proxy goal for maintaining a given launch pace we wouldn't need any of this.
We could just construct 200 Space Shuttles and spend months refurbishing them after every flight, and still send one up every week.
The goal is to drive down launch costs, time is money, and a system that requires time consuming refurbishments is more expensive.
- It's because before Bush invaded Iraq it would have been redundant to clarify that Bush said such and such in an official (written) capacity, as opposed to describing what the foreign policy goals of the US were at that moment. The two were synonymous.
Whereas when Trump was making overtures to annex Canada, it was useful to the rest of the world to explain that that's something the president was talking about that weekend, as opposed to signs that this might be something the US would actually do.
- How much of that 10% was them basically paying OEM's and consumers to use Windows, which is what the Nokia deal amounted to? It wasn't sustainable.
Whatever benefit we'd have from a Windows Phone today, it's laughable to think that Microsoft wouldn't be doubling down on exactly the sort of locked-down devices Apple (and now Google) have or are moving towards.
Their only vaguely "open" platform (Windows) is like that because of legacy compatibility and customers, but for anything new Microsoft always wanted to sell you an Xbox that could make phonecalls. Try writing and deploying an app on that without a developer account.
- Annex isn't slow because it's written in Haskell, it tends to be slow because of I/O and paranoia that's warranted as the default behavior in a distributed backup tool.
E.g. if you drop something it'll by default check the remotes it has access to for that content in real time, it can be many orders of magnitude faster to use --fast etc., to (somewhat unsafely) skip all that and trust whatever metadata you have a local copy of.
- Thanks, also not-so-relevant, for the reasons I noted in a comment in that thread: https://www.hackerneue.com/item?id=44922405
I.e. annex is really in a different problem space than "big files in git", despite the obvious overlap.
A good way to think about it is that git-annex is sort of a git-native and distributed solution to the storage problem at the "other side" ("server side") of something like LFS, and to reason about it from there.
The idea that everyone can show up at the protest with their AR-15, somehow defeat the state's security forces in armed combat, and that the result will be some enlightened republic is an American fantasy, informed by what's at best a selective reading of American history.
If it comes to that you're much more likely to end up under some warlord. Afghanistan and especially Africa are full of people who are well armed and where exactly that's happened more often than not.