Post #3970675
2026-07-20 15:30 UTC
@b0rk@social.jvns.ca I also have been thinking for a while that a constrained "you get 64MB of compute" is actually a really good unit. It packs densely. It's plenty to do some immense tasks. It requires you to not waste resources. It might just be an enabling constraint if providers managed to make it a utility that you could depend on.
WASM has a lot of shades of this too. It could, in theory, enable dense dynamic computing for mostly-static sites.
The problem is that someone has to take responsibility for the data, or make it _possible_ for users to take responsibility for it usefully.
Replies (1)
-
@aredridel@kolektiva.social 2026-07-20 15:32
@b0rk@social.jvns.ca I wish there were a step between 'permacomputing and error-correcting-coded-replication-of-data-forever' and 'yolo, if you delete everything from your postgresql database, it's gone'. I think we could make it but we'd have to enumerate the responsibilities and trade-offs.