@pdt I'm sure to a degree. I've been coming at this from another angle: now hardware on the flattish part of the depreciation curve is past the bar for most modern tasks. $100 laptops are good enough for coding, video calls, CAD, etc. Due to modern compilers, better kernel tuning, etc, performance can be better than when the hardware was new.
Maybe if the tools we use were shaped more by the users and less by commercial interests we'd be better off.
In my life I've watched the limits of personal computing fall one by one. We've gone from computers too small to store a long text document, to computers so big you can store many lives' works and requiring a search engine to access the contents. And yet it doesn't feel like we're collectively getting any smarter.
@laemeur As a concrete test whatever the new standard it should be pretty easy to add support to Firefox, Dillo, links, etc, and a reasonable project to write a basic client and server in Python leaning heavily on existing modules.
@laemeur Following this idea I think it would be interesting to start with the most modern versions of HTML, HTTP, TLS, etc, and then select a subset based on what works well on low-resource platforms and without centralized authorities (cert authorities etc). Existing embedded browser features, benchmarking on real low-resource platforms, and implementation complexity in popular languages, all would be good guides.
@laemeur On one hand a new named technology provides a convenient reference point for a community to rally around, helpful in reaching some kind of critical density to make a social tool have some use. On the other hand a subset of HTTP+HTML would be accessible to more people, more flexible, and potentially easier to adopt. I'm personally not too likely to publish anywhere without pictures.
@email@example.com So what to do? I'm not sure. Federated private storage behind a standardized API seems like generally the right direction. Self-host if you want, local disk if you want, some company or org for most normal people, but in all cases use the same well-tested API and client implementation. WebDAV seems wrong but it needs to be something that has good support for caching and acknowledges the failure modes of non-local storage. Hm.
@firstname.lastname@example.org I agree with the sentiment. Personal computing is in an awkward transitional phase that makes solving storage really tricky. A lot of data is used across at least a phone and a PC. Most personal PCs are laptops now that spend a good amount of time asleep or totally offline in a bag while in transit. That brings in availability, sync, and UX challenges. "Cloud" has well known problems.
@gemlog @snowdusk In my limited UI dev experience it's usually helpful for visual things to be done visually for all but the most exotic interfaces. Code in text but graphical editor to lay out and wire the visual bits. HyperCard was ok for that but I really don't like the scripting language (personal taste).
@neauoire In the era of fixed screen sizes, data fixed on disk, and authoring tools like Hypercard hand-crafted screens were really promising. I've racked my brain for how to achieve something like it when the same tasks are spread from tiny phones up to big desktop displays and... Not sure but I want there to be a tidy answer.
and yet I participate
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko