@p

@TradeMinister


> Maybe it's even written in ObjC.

> C++. Except Firefox and its unholy Servo/Gecko situation, they're all using Webkit. Even Opera. Even Microsoft's Edge uses Chromium's engine, which is a fork of Webkit, same rendering engine popularized by Safari, though it was initially developed for KDE. It's harder to avoid Webkit in 2022 than it was to avoid Microsoft in 1998.

Probably because CS majors were taught C++, not ObjC.

> Well, they broadcast it. We do have a huge DB, 360GB on-disk at present. (Just the posts, the likes, etc.; not counting uploads.) That's the handshake problem: someone on FSE likes a post, every instance that contains a follower receives a delivery, then, although I have hacked this out of FSE, there is also an entry in the deliveries table recording each successful delivery.) So even a single-user instance where the single user is followed by enough people will chew bandwidth and leak disk at a pretty alarming rate.

So, instances/nodes won't be running on phones anytime soon. I see no obvious way around this: a network-as-storage-and-server model seems to require a lot of local storage and network chatter.