I am not sure about the tabs.

For the scrollbars, edit these settings in about:config:
- widget.non-native-theme.scrollbar.size.override = 16 (or whatever you want it to be)
- widget.gtk.overlay-scrollbars.enabled = false

It has been an open secret in the cryptography community that Hal Finney was the designer of BitCoin from the very start. Hal died in 2014. Or at least he was frozen in liquid nitrogen so not talking either way.

Besides being the first person to be involved in BTC who didn't hide behind a pseudonym, Hal published a paper that describes essentially the whole BitCoin scheme two years before BTC was launched. And Hal never once accused Satoshi of stealing his work.

The reason Hal had to hide behind Satoshi is simple: The Harber Stornetta patent didn't expire until about 9 months after BTC launched. That covers the notion of the hash chain. There is absolutely no way anyone working in the field did not know about that patent or its imminent expiry. Hal certainly did because I discussed it with him before BTC was launched.

So the big question is why BTC was launched when it was, why not wait 9 months to have free and clear title? Well, Hal got his terminal ALS diagnosis a few weeks prior: He was a man in a hurry.

Having launched prematurely, Hal had to wait six years after the original expiry of the patent term to avoid a lawsuit over the rights to BTC from Surety. He died before that happened.

Oh and I have absolutely no doubt Hal mined the genesis blocks straight into the bit bucket. The key fingerprint is probably the hash of some English language phrase.

The real inventor of BitCoin wrote a paper describing the architecture two years earlier under his own name, Hal Finney. He got a terminal diagnosis of ALS a few months before he launched the BitCoin service, the pseudonym being necessary at the time because of the Haber-Stornetta patent on the BlockChain.

No, Hal, did not keep the coins. He invented BitCoin because he was a crank with weird ideas about inflation, not to get rich. Mining the coins and keeping them would have been a betrayal of his principles.

The proof of this is given by the fact that Hal did not in fact get rich from BTC despite being the ''second' person to join the project. Nor did Hal ever complain that Satoshi took the credit for what was very clearly his work. If Hal had been just another person coming along, there would have been every reason to keep the cash.

And we do in fact know Hal ran mining servers from the start and that he ended up in serious financial trouble due to his ALS. The freezing his head thing came from donations.

Craig Wright does seem to be the last of the three early advocates alive but that doesn't make him Satoshi. Wright has never shown the slightest sign of being the sort of person who builds such a thing and in any case, Hal's name is on the much earlier paper.

The CC processors have NO incentive to even care if the borrower defaults - they get their cut at the time of the transaction, skimmed right off the top. The only transactions they don't like are fraudulent ones, and that's only because when those get reversed, they don't get their cut.

As far as these jackals are concerned, the more transactions, the better - they want you paying for *everything* with your card. (And encouraging card use through "rewarding" you with a small portion of their take, which they make a fortune on anyway, just from the float!)

Merchants should start adding 10% for using a card. (This used to be prohibited by the merchant card agreements, but they lost in court a few years ago so AFAIK this *can* be done. Anyplace it's prohibited, you could offer a 10% discount for cash.)

Once again, ignorance of physics and engineering permeate an article rah-rah-ing for a scheme that can simply never work all that well.

The ignorance is of the *quality* of heat - there's plenty of low-quality heat (and you'll lose a lot of that into sand before you can get to temps that provide high enough heat quality (delta-T) to be very useful for anything. And when you're done, you still don't have the advantages of latent heats of condensation vaporization. There's a reason phase changes rule in heat engines, from motors to air conditioners!)

Have a look at Windy. I can't speak to their APIs, but the web and app versions are both excellent in thier own interfaces as well as fed by excellent data - some of which would cost a fortune to get elsewhere. It really is one of the most impressive weather apps on the net.

NOAA is OK, but Windy is excellent - and will be the last SaaS subscription I have after purging all the others - it's the only SaaS sub I can recommend without reservation. Windy provides *many* more (and often better) models than NOAA does, with really good visuals, to boot.

Big Companies almost always wind up destroying the fundamental value underlying their acquisitions. Intellicast legitimately revolutionized high-graphics weather maps and other info and was arguably the first graphically intensive web weather site on the Internet. They were also an early pioneer with using JavaScript to provide a better, faster, and much more responsive UI than any of their competitors. Wunderground originated as a commercial spinoff of the University of Michigan Weather Underground FTP server, and later added the amazing Weather Station Network to collect fine-grained data from thousands of sites, changing the data feeding finer-grained WX models. Both sites were pretty much destroyed by IBM's acquisition - Intellicast (which had already fallen from previous glory) became a bad me-too site mostly parroting crap opinions from the Weather Channel, which IBM had also acquired, and Wunderground's amazing Wundermap driven by that sensor network was reimplemented in some trendy language/platform that produced such a huge performance/responsiveness hit that it was effectively unusable for a couple of years.

(Aside: over 30 years ago, I wrote a fairly simple set of (k)sh scripts for a Fortune 10 company to pull satellite images down from the Weather Underground FTP server and assemble them in the correct order in to provide a video weather animation in X, something that normally required a $50K/year professional WX service subscription. (Yeah, interestingly, I did all this through command line scripting an expect - I didn't have to write any "real" program code at all. Later versions even cleaned up the images using the then-new ImageMagick, also from the command line....)

Yeah, Prime's value proposition is gone. I doubt I run much more than two or three under $35 Amazon orders per year anyway, so it's not like I *need* Prime. I used to justify it for Prime video, but with the crashing content quality, and Amazon's continual killing off of shows we really like (Z, The Last Tycoon, Night Sky, etc., etc.) in favor of execrable dreck like Rings of Power or their latest perverted LGBTQIACRT sh*t...

With very few exceptions (literally only a few a year), the only thing we use Amazon Prime services for is to use Alexa as a voice controlled radio or music player.
Amazon's pissing me off badly enough in other areas that I'd just as soon drop them, if I can easily replace that functionality.

Does anyone know of an already-sorted, distributed, voice-controlled *local* media player solution? Sure, I have the skills and could put all the pieces together myself (I'd even buy new hardware to replace the Echoes, if needed, since we've only got a few - or reflash them with new firmware if that's necessary...), but I've got better things to do with my life than design and build an entire media system right now, so I'm looking for a solution that someone else has already gotten working.

I'm figuring some of the home automation folks have already got this done, but maybe not...

There is setting/preference called "Always show scrollbars". It toggles the "widget.gtk.overlay-scrollbars.enabled" pref as mentioned by the Anonymous Coward. It will not force the scrollbar to be visible on a page that cannot scroll. I think that requires GTK v3 tweaks for UNIX systems.

Have you tried making a setting in user.js in the profile directory to force it every time you start Firefox? Check out the arkenfox link at the bottom of my post.

Try setting:
- widget.gtk.overlay-scrollbars.enabled to false
- widget.non-native-theme.scrollbar.size.override to the size you want

I cannot help you there. Pocket is one of the first things disabled for me.

You should take a gander at https://github.com/arkenfox/us... to minimize the junk in Firefox.

CCS can go up to around 400kW. Well, actually I think it is 500kW now. Which is 1000VDC x 400A or 500A.

Most BEVs canâ(TM)t go that high. In fact, I think there are only one or two that can actually max out current 350kW chargers for any decent amount of time. Neither of Them T

-Matt

Yes, but nobody fast DC charges to 100%. The charge rate drops modestly past 60% and precipitously above 80%. So people only charge to 60-80% and no more. Usually 30-40 minutes max. And if your final destination is close and destination charging is available, only enough to get there. So for trips just beyond the vehicle range, the charging stop can be very short, like 10-15 minutes.

At home, or at a destination, people will charge to 100% overnight if they will be taking a long trip the next day, and otherwise only charge to 70% or 80%. Unless itâ(TM)s a model 3 with a LFP battery, in which case people charge to 100% overnight.

-Matt

-Matt

Yah. The connector standard has settled down, which is good. Chargers are typically only able to do AC or DC anyway, not both. CCS on the vehicle allows both J1772 (AC only) and also has the extra pins for high amperage DC.

L1 (120VAC) 11-16A (in vehicle charger)
L2 (240VAC) 24-80A (in vehicle charger)
L3 (was never implemented)
Fast DC charging, direct DC to battery, dynamically managed up to 1000VDC and 500A.

Limited by the lower of what the external unit can supply and the vehicle can accept.

Chademo is being steadily removed. The cable standard was too limited. So if you own an old leaf, you need to start carrying around an adapter.

-Matt