News for hackers. Stuff that matters.
Re:Authorize, Don't Authenticate by _def on Friday July 31, 2026 @05:09PM (#49128552)
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) apps.

Re:Authorize, Don't Authenticate by mqus on Friday July 31, 2026 @06:32PM (#49129291)
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.
Re:Authorize, Don't Authenticate by happosai on Saturday August 01, 2026 @02:25AM (#49131652)
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...

Re:Authorize, Don't Authenticate by marcua on Friday July 31, 2026 @11:17PM (#49130732)
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?

Re:Authorize, Don't Authenticate by jmsgwd on Sunday August 02, 2026 @03:08PM (#49147343)
If the database is not local, and there’s no authentication, what stops someone else from accessing it inappropriately?