riobard

For audio there're also `afinfo` to probe metadata and `afconvert` to convert between different codec/container formats. I use them for podcast post-processing and archiving workflow.

macOS 13 Ventura ships with a customized `iperf3` called `iperf3-darwin` adding features like QUIC/L4S/MPTCP.

Where do you buy $5/TB tape at retail?

My ISP did exactly that. I bugged their customer support several times over a month and they finally caved and gave me /60 now.

Probably off topic, but is it worth the trouble to (re)write critical infra software like SSH in memory-safe languages? From the release note this seems a minor issue, but given the importance of SSH in auth, maybe it isn't too crazy to think about the possibilities?

Correct me if wrong, but I thought that you cannot extract the private key from the Secure Enclave at all?

Don't worry coz DAD (Duplicate Address Detection) will come to your rescue :p

You need to factor in the compression ratio to see the benefits of swapping from RAM to RAM :P

would be interesting to combine this with `zram` to move compressed swap to vram instead

Not just Google. Recently I tried to web login to my PayPal account. PayPal decided it was a risky attempt for some reason and asked me to provide a phone number for verification. So I gave it the one associated with my PayPal account for years, and it refused! Presumably because the number was a virtual one, which I used for all account registration stuff in case of switching carrier or out of cell coverage.

I was locked out of my account for several days due to the phone requirement until it clicked for me one day: maybe I could try login with the PayPal app on my iPhone? Sure enough, PayPal trusted the app and let me login to their app. Then I tried to web login again, and this time it asked me to confirm in the mobile app that it was indeed me who's attempting the web login.

Given that PayPal is handling people's money and they have good reasons to be cautious, but risk-based auth really sucks at times when you don't have enough patience for it.

> hard to come up with a legit explanation for why they rushed that change to China first.

Not hard at all.

On Oct 13, 2022 this protest happened (https://en.wikipedia.org/wiki/Beijing_Sitong_Bridge_protest), which the CCP considered a serious offense, potentially on the same level of the 1989 protest.

At the time people, especially college students around that area (lots of universities nearby), were using AirDrop to share photos of the protest, because social medium was heavily censored. University administrators were tasked to make sure iPhone-carrying students to disable allowing AirDrop from everyone to stop the spread of the images.

A few weeks later, iOS public betas were found to come with the change to limiting AirDrop to 10 minutes, and nothing about it was ever mentioned in release note.

Was Apple pressured by the CCP to rush this? I don't know. Look at the evidence and judge by yourself.

But there's a more nuanced perspective.

It is rumored that CCP has the ability to actually track and uncover the identity of iOS devices sending AirDrop. Think about it: how else AirDrop can limit to receive from contacts only? If so, AirDrop would provide a false sense of anonymity and deniability, and Apple would put some of its customers in jeopardy if they do nothing.

By limiting AirDrop from everyone to 10 minutes, Apple achieved three objectives:

1. They showed compliance (they have to, if they want to keep the business in China); 2. They avoided the potential reputation damage in the scenario where protesters are caught AirDropping offensive materials (e.g. “iPhones aren't as secure as Apple advertises after all”); 3. They closed a loophole in which people get spammed (yes, allowing AirDrop from everyone gets you mostly spams anyway).

The “mistake” Apple made was that it did not a) rush the change to all regions, and b) mention it explicitly in release note, therefore completely exposed them to the first objective and failed to convey the nuances.

I'm wondering… have you ever tried to restore from that TM backup?

Interesting. Could you please share the Samba config for the Time Machine shares? And over what medium do your Mac machines connect to the NAS? Wired or wireless?

Have recent versions of macOS fixed the reliability of Time Machine over network (especially over Wi-Fi)?

It used to be that after a while (varies from a couple of weeks to months) Time Machine would complain that the spare disk image on the NAS was corrupted and you'd have to start from scratch, which completely defeats the purpose of backup.

If resentment from rendering existing accessories obsolete due to changing connectors is the root cause of the delay, maybe Apple has been secretly waiting for the EU legislation so it can deflect the blame? e.g. "it's EU forcing our hands so we have to change."

> To treat the cells well requires sacrificing some capacity to reduce the voltage stress on the cells.

Battery-power devices like smartphones should have a mandatory control of what percentage of battery it should be charged up to.

For Mac there's this nice utility AlDente https://apphousekitchen.com

Right now the idiomatic Go approach to handle networking is 2-goroutine per socket (one for reading and the other for writing). Goroutines are very lightweight userspace threads, but they're not free: each costs you a small amount of memory. At Cloudflare's scale, this overhead quickly adds up. So resource-wise, Go isn't ideal for very large scale use cases.

There is a more-than-6-year-old proposal to introduce non-blocking I/O API (https://github.com/golang/go/issues/15735) but so far it's not gaining much traction. Maybe in Go2.

I'll have to ask this since it's bothering me for quite a while…

If I connect to a server via WireGuard, would it make more sense to run simpler & unencrypted `rsh` instead of `ssh`? It's kinda pointless to double encrypt.

I'm not sure how you conclude that AllowedIPs does no routing.

> On a lower level, AllowedIPs is really just "allowed IPs", and does no routing.

This is contrary to what the official documentation says https://www.wireguard.com/#cryptokey-routing

> You can have multiple active peers with overlapping AllowedIPs.

You can, but the most specific CIDR wins route selection, which is exactly what *routing* does.

Is this turbocharged TPROXY?

Any plans for sending emails?

Mail storage cost is negligible.

Correct me if I'm wrong, but isn't this problem the ideal use case for projects like IPFS? Anyone interested to preserve the content can join as a node to balance the load, right? And if so, why don't we see widespread adoption?

Optic disks work that way, but highly unlikely for hard drives as the internal chamber requires super clean air without any dust. Latest hard drives over 8TB mostly have adopted helium-sealed chamber, making removable platters even less feasible.

> assuming compression of course

I don't know why this seems the standard practice in the industry, but it really annoyed me when I realized a “15TB” LTO-7 tape has actually only 6TB real, “native” storage coz it assumes some average compression ratio.

Why is this acceptable? What if I use the tape to store incompressible data like video and images? Feels like intentional cheating.

Not sure about ARM-based NAS, but most x86-based QNAP NAS devices are basically a PC in hardware configuration with mature Linux support, so there's not really any support issue.

The PiBox case apparently can only house two 2.5" SATA drives, not regular 3.5" hard disks commonly used for cheap mass storage. 2.5" hard disks seem to peak at 5TB per drive so the potential capacity is limited unless you go with SSD at much much higher cost.

The PiBox's 15W power supply leaves very tight margin for its components: Pi4 peak power consumption is about 6.5W, two SATA SSDs will peak over 5W each as well, so you should watch for power for stable operation.

I couldn't find a 2.5" 2-bay NAS model so the form factor isn't identical, but the closest match is probably QNAP TS-230 w/ similar 4-core ARM A53 SoC supporting two 3.5" drives for $199. The obvious downside is that RAM is capped at 2GB and that might be a deal breaker if you want to run lots of apps, but for entry-level storage needs it should be sufficient.

> a simple NAS device that is not much larger then drives it uses, but doesn't have Qnap OS installed on it.

Well, you could just install your favorite Linux distro on a QNAP NAS device. Cost-wise the Pi-NAS option isn't even competitive if you aim for similar spec and form factor and packaging.

What does the VPU do after boot if the unit is headless?

That was supposed to be solved by FileCoin, i.e. financial incentives to keep content alive.

Thanks a lot!

VC money is unlikely the source for this kinda of industrial research and bumpy road to scalability.

LCD/OLED panels got so cheap largely due to Korean/Japanese/Chinese government subsides. I doubt any of them will do so for e-ink.

Could you please tell a bit more about the volume-side of story? Somehow I feel that E-ink is at this weird point on the cost/volume curve because it is a fundamentally flawed display technology: monochrome or a couple of dull colors at best, very slow refresh rate (with ghosting/leftover on partial refresh).

LCD/OLED displays were also very expensive initially, but because they're so much appealing universally, loads of money got poured into the industry to make them better and cheaper (mostly due to volume demand).

There's no such amount of money/interest in making E-ink better and cheaper :(