mishagale

Bear in mind that in the UK, a large chunk of the populations lives in either rented accommodation, high-rise flats, or both. And also, standard housing policy in London is for new developments to have fewer parking spaces than homes (to encourage public transport use over cars).

For many people in the UK, having an EV charging port on the side of your house isn't possible, because they don't have a house, or they don't have a parking space near their house.

winpopup was a GUI interface, `net send` was the CLI command (with which you could indeed message an entire domain)

That looks like a US version of Faster Payments* (UK) or SWIFT (Eurozone) that enables instant wire transfers between bank accounts. I doubt very much it is suitable as an alternative to credit/debit cards for retail payments. For one thing, there's zero fraud protection, it's the electronic equivalent to paying for something with a cashier's check. For another, it's a pretty laborious process - you have to sign in to your online banking, enter the recipient's bank account details and the correct transaction reference, probably do some kind of 2FA.

For a third thing, while in the UK banks generally don't charge anything for transfers, the Bank of England charges a few pennies (£0.07 last I heard) per transaction. If people were routinely making several of those payments every day the way they do with cards, I'm sure banks would start charging fees.

* By the way, Faster Payments went live in the UK in 2008, but it still took a couple of years for all consumer banks to adopt it.

I've always felt one of the main reasons for this is that we never really got true microtransactions on the web. Pretty much all payment processors charge at least $0.20-30 per transaction.

My theory is that if there was a way to frictionlessly pay, say, $0.02 to access a piece of content ad-free, most people would be pretty okay with it. They key part is making the transaction frictionless - no more than 1-click/1000ms.

On the same basis, most home routers are powerful enough to run a basic webserver, and they are much more likely to have a consistent internet connection. They probably aren't behind CG-NAT, and most of them have Dynamic DNS support even if they don't have a static IP.

I remember that way back when, Deutschebank standardised on SuSE because they were a major shareholder in the company. DB had an IT department bigger than most entire companies, so I'm sure that had a pretty big effect on the ecosystem.

Have you ever tried accessing the modern web with a Windows 95 computer using Netscape Navigator?

Even if that computer had up-to-date certificates, basically nothing about it would be compatible with the modern internet. It's not just a question of of "expiry dates", it's that you cannot make any forward progress if you have to maintain backwards compatibility forever.

Internet protocols, file formats, hardware standards... all these things need to be able to change over time. Hell, with the old phone example, your biggest problem with a sufficiently old phone is whether it can even connect to the network - I recently tried using a retro Nokia as a backup phone, but realised that the SIM card I'd put in it was for a network which didn't offer 2G coverage. Phone couldn't even make calls or send texts because it wasn't 3G compatible.

You are right, my bad.

Based on their published user numbers and revenue, Selig estimated that reddit's revenue per user is about $0.12.

They are asking for $0.24 per 1,000 API calls. Apollo averages ~345 calls per-user per-day (although some users are much higher), but Reddit claims that other apps are "more efficient" and only use about 100 calls/day.

If we assume 100 calls/day/user, then that's 36,500 calls/year/user, and a user is worth $0.12/year, so to break-even, reddit should be charging about $0.003 per 1,000 API calls, instead of $0.24.

Presumably because if you are a party to a lawsuit, you generally shouldn't say anything about it without it being cleared by your legal counsel. Their lawyers might have advised them not to say anything publicly, or they might not have the budget to get lawyers to approve public statements.

Doesn't Linux already have mature support for ARM? What's so different about the M1 that it needs all this extra work?