My insistence on running a from-scratch reimplementation of an activity pub server and libraries is only being reenforced. For a supposedly open protocol, implementing fediverse compatible API's feels a little bit too much like reverse engineering.
@SRAZKVT Probably has something to do with the big tech urge to make protocols and specs that can do everything for everyone at all times, rather than making simple things that can be glued together like building blocks to build individualized solutions that can work for each person. I'm not entirely sure what the Unix philosophy for the distributed web might look like, but I hope someone figures it out.
@SRAZKVT Trouble is, you're then just moving that complexity onto the user who needs to install and update 20 different apps. Most folks just want to run a browser and that's all they know or understand. Feels like part of this will require redesigning the entire OS UI.
@SRAZKVT I wonder if we maybe invent a secure virtual machine standard and every app is just a VM in a sandbox? I guess with web assembly that’s kind of what browsers are becoming.
@fastfinge the problem with webassembly is there's no jumps, it's just modeled after what v8 devs find convenient, and their ir doesn't have jumps, only blocks, so wasm only has blocks
leads to compilers needing to generate terrible loop code in order to work
@SRAZKVT Sure, that’s the problem with everything the browser does. It wasn’t planned or designed; it just kind of happened. And now none of the previous decisions can ever be changed. We just have to build new crap on top of the fifty layers of old crap that already exists.
@fastfinge tbh we should just do a reset, look at all the needs that are filled, see the ones that don't exist anymore, and simplify everything by also making it more generic