4 ms·

We are back to File->Open I guess. We could use native applications instead of web apps while we're at it. Sadly this approach does not work for a lot of (web)

• mqus 2mo ago
  yeah, to me this also pretty much sounds like the approach we started with, we bring our data (as a file) into the application and it stores it back if we want to.
  • happosai 2mo ago
    Everything old is new again. We started with timeshare machines (there is only market for 7 computers in the world) where you accessed with VT102 etc terminals. Then we went to personal computers with local data and code. Now we are back to a handful of massive timeshare machines (AWS, Azure, ..) that keep your data and let you only access with HTTP/HTML terminals. Now if people get angry enough with Salas enshittification we'll go back to personal computers again...
• marcua 2mo ago
  Author here! The solution I'm proposing does not assume the data is local to the user's machine. In the video attached to the blog post, a web application is authorized to access a database hosted by a different service/domain. While the blog post covers collaboration/social data as current limitations, I'm curious what other classes of web apps you think don't work with the proposed approach?
  • jmsgwd 2mo ago
    If the database is not local, and there’s no authentication, what stops someone else from accessing it inappropriately?