5 ms·

How about local storage? Only downside is that this data isn't sent automatically on ever request (unlike cookies). It would be possible though to send this sec

How about local storage? Only downside is that this data isn't sent automatically on ever request (unlike cookies). It would be possible though to send this secret from local storage via a separate request and receive a session cookie that then let's you be logged in automatically

hinkley 3y ago
Maybe shared local storage should be a browser standard. Let me keep track of my own data, but also share it with my tablet and phone by clicking a bunch of buttons.
- thelastparadise 3y ago
  Even better: shared storage where every website has access to the same storage data. Log in once, on one website, then be logged in on all websites forever.
  - hinkley 3y ago
    Isn't that basically third party cookies all over again? If you work for advertisers this sounds like a great idea. Better than eating babies.
- danShumway 3y ago
  This is circling around Native File Access, which is absolutely something the web needs and if handled correctly would be a huge improvement for user privacy and user autonomy. It would open the door for fully offline webapps with no accounts or serverside components, with much better sandboxing than native apps, and with full user control over app data using just a file browser. And it would allow for app data that could be easily shared between apps when necessary without compromising user privacy or security because the app data would just be a directory with files. BUT... the problem is that if handled incorrectly it would be a disaster for web security, would open up tons of holes for user tracking and data theft, and would basically be a horror show. There are a dozen things that could go wrong with the spec, and all of them would be serious problems if they did go wrong. And Chrome is heavily involved in the spec. So it's a tough position to be in to try and figure out whether it's worth advocating for. Mozilla currently considers native filesystem access to be harmful, and I don't know whether or not I agree with them. I wish Mozilla would propose an alternative spec developed entirely internally without interaction from Google.
  - hinkley 3y ago
    Is that what I'm talking about though? We are talking about tablet phone and laptop sharing a data store. Not multiple user agents on the same device sharing a data store. Though we have entered the era where the names of specs or initiatives have little to nothing to do with the actual meat of the thing.
    - danShumway 3y ago
      I don't know, I use filesystem sync for all of that. All that really means is that on iOS/iPad you'd have a file portal sitting in front of your browser. And on Android, it's already filesystems anyway. Maybe you're right though and the UI would need to be different :shrug:

hinkley 3y ago

Maybe shared local storage should be a browser standard. Let me keep track of my own data, but also share it with my tablet and phone by clicking a bunch of buttons.

thelastparadise 3y ago
Even better: shared storage where every website has access to the same storage data. Log in once, on one website, then be logged in on all websites forever.
- hinkley 3y ago
  Isn't that basically third party cookies all over again? If you work for advertisers this sounds like a great idea. Better than eating babies.
danShumway 3y ago
This is circling around Native File Access, which is absolutely something the web needs and if handled correctly would be a huge improvement for user privacy and user autonomy. It would open the door for fully offline webapps with no accounts or serverside components, with much better sandboxing than native apps, and with full user control over app data using just a file browser. And it would allow for app data that could be easily shared between apps when necessary without compromising user privacy or security because the app data would just be a directory with files. BUT... the problem is that if handled incorrectly it would be a disaster for web security, would open up tons of holes for user tracking and data theft, and would basically be a horror show. There are a dozen things that could go wrong with the spec, and all of them would be serious problems if they did go wrong. And Chrome is heavily involved in the spec. So it's a tough position to be in to try and figure out whether it's worth advocating for. Mozilla currently considers native filesystem access to be harmful, and I don't know whether or not I agree with them. I wish Mozilla would propose an alternative spec developed entirely internally without interaction from Google.
- hinkley 3y ago
  Is that what I'm talking about though? We are talking about tablet phone and laptop sharing a data store. Not multiple user agents on the same device sharing a data store. Though we have entered the era where the names of specs or initiatives have little to nothing to do with the actual meat of the thing.
  - danShumway 3y ago
    I don't know, I use filesystem sync for all of that. All that really means is that on iOS/iPad you'd have a file portal sitting in front of your browser. And on Android, it's already filesystems anyway. Maybe you're right though and the UI would need to be different :shrug: