prirun

I'd love to have speech-to-text on my iPhone that actually worked without needing to proofread and edit.

> I don't think the creators of any of those technologies were warning society that their own creations might wipe out humanity.

They are only doing this now IMO so that they can be the ones writing the regulations to keep us all "safe", just like we need identity verification to "save the children". They want to keep competition at bay so they can have a $2T IPO, and unregulated, "unsafe", Chinese, open-weight, and local AI threatens that IPO.

> Clustered indices would be so, so nice for Postgres to have.

Doesn't that just trade slower inserts for faster deletes?

I worked with Prime minicomputers when I was a late teen. They introduced RingNet, a token ring product, in 1979.

Fun fact: each system had an IN and an OUT coax port, and the coax cable was about as thick as a thumb. If a system died, a small hardware box short circuited, tying the IN and OUT coaxes together. This kept the ring intact, but it would also make that segment of the network longer and there were strict distance limitations between nodes. If the distance got too big, the entire ring broke. Also, if any coax cable got damaged, that also lead to a ring break. Prime had a special diagnostic program they could use on multiple nodes to try to find ring breaks.

One of the most "fun" things with Fortran is the EQUIVALENCE stmt. It specifies that two variables share the same memory, even if they are different types. You can also do array equivalences, so:

  INTEGER ARR1(10), ARR2(5)
  EQUIVALENCE (ARR1(6), ARR2)
  ARR2(1) = 10

will also set ARR1(6) to 10.

I had a 1TB Samsung 9xx Pro fail on me in a Windows 10 PC. One day the PC wouldn't boot, said there wasn't a hard drive there. I put the drive in an external USB 3 case and with Linux, I could dd from the drive, but it was running really hot and had an unusual access pattern: it would run for about 5 seconds and then pause for 30 seconds. I think the pauses are what screwed up the Windows boot because it wasn't waiting long enough for the drive to respond. I eventually did get the drive copied w/o data loss, though it exceeded even Linux's timeouts a few times during the copy and I had to restart dd with an offset to get the whole thing copied.

Who cares? They will still be all lies.

> "If AI fulfills its promise, we will encounter more beautiful and consequential ideas than we have ever seen."

It will be as it always has been: these ideas will further enrich the rich, at the expense of everyone else. We'll have our first quadrillionaire, while the masses are debating whether the minimum wage of $7.25/hr should be bumped up.

I have used Google's jump hash. As I recall, one of the main differences is that jump hash doesn't have a mechanism to remove targets, eg, a server dies and you don't want to route requests to it. Traditional consistent hashing can do that. I guess if you had 4 servers, server #4 dies, then you can go back to 3 servers by just changing num_buckets from 4 to 3. But if server 1 dies, you can't.

Jump hash does allow adding more targets and preserves the property that most request targets stay the same when adding a new target, so if you had 3 targets and add a fourth, ~8% of the requests that would have been sent to targets 1-3 are sent to target 4, evenly chosen from servers 1-3.

Or, like me, who has never been a runner, a heart rate in the 30's can mean that you have heart block, an electrical problem with your heart where beats are gradually spaced further apart and then there is a longish delay before a reset. In a recent 2-week heart monitor test, my longest delay was 3 seconds and I had 4 of these. There are different types of heart block: mine is type 1 Mobitz/Wenckebach. Not really dangerous - I've had it all my life and known about it for ~35 years. It shows up on all of the modern automatic heart/blood pressure machines because the delays cause unusually low readings whereas a nurse checking your pulse may miss it.

My average heart rate on the test was 58, lowest was 21 (for 3 seconds), and highest was 250 (for 6 beats). A few minutes after getting in bed, my heart rate regularly is in the 40s and sometimes low 30s.

I don't mind a checkbox. I don't even mind the "proof of work" types that take 10 seconds extra. But identifying traffic-y things over and over is way too much for me. I did do one screen, thinking it would let me in, but it just gave me another.

I do use Firefox. And I couldn't cancel my account myself: had to request it via email since I couldn't login. They were good about doing it right away and said they issued a refund for the balance.

I read that Internet Archive keeps 2 copies of all their data. Storj, the decentralized storage service, is currently in Chap 11 bankruptcy, mostly IMO because of incompetent management. They pay their node operators, the guys that actually maintain the hard drive space, $1.35/TB/mo to store data. (However it costs Storj 1.8x that because of erasure coding). They still have way more available capacity going unused, so it's likely they could lower the payout rate even further and have talked about doing that.

Internet Archive could buy Storj, probably for not much, keep 1 copy of their archive on the IA custom server setup they have now, keep the other copy on Storj, and free up half of the IA disk space. Storj automagically uploads data to 54 nodes, any 29 of which can reconstruct the original data (54/29 is where the 1.8 expansion factor occurs).

I've used vultr.com for years with no problems. Recently it wouldn't let me login without solving a Google captcha. I tried private windows, etc and ended up having to cancel my Vultr account and ask for a refund. Fortunately I only used them to spin up test VMs and didn't have any production stuff running there.

I refuse to pay a company for service and then be required to identify motorcycles and traffic lights every time I sign in. I went a few rounds with Vultr customer service and they said (paraphrasing) "It's not something we can fix, you have to talk to Google about it". Right... Google forced you to put their captcha on your web site.