6 ms·

By snoop-phone, do you mean stalkerware? I have not heard this phrase before. Thanks in advance for the clarification.

eimrine 3y ago
I am a big fan of RMS and I find promising to promote his way of naming things everywhere. Here are two recent links which explain this word choice. [1] https://www.stallman.org/archives/2023-jul-oct.html#26_September_2023_(How_to_really_know_a_person) https://www.stallman.org/archives/2023-jul-oct.html#26_Septe... [2] https://www.stallman.org/archives/2023-jul-oct.html#11_September_2023_(Smart_device_collect_excess_information) https://www.stallman.org/archives/2023-jul-oct.html#11_Septe...
- shanebellone 3y ago
  Ah, but that's not that case here at all. It's not an app. It's still a sandboxed web page. The only difference is the communication method. Rather than a transactional client-server relationship, we adopt the media-steaming approach post-load. That is to say: You would load your desired website (the standard way) and then experience a "refresh-less" session for the duration of your visit.
  - eimrine 3y ago
    Do you propose thin or thick client? How about Java applets or MS Silverlight?
    - shanebellone 3y ago
      Why such archaic examples? Imagine visiting this website, Hacker News, to read a few posts/discussions. Does the idea of circumventing a refresh offend you? You could click into a threaded discussion (from the homepage) and back without triggering a reload or needing the data beforehand. Other than the indexability problem, it seems like an ideal solution. In many use cases, the indexability problem is actually a feature too.
      - eimrine 3y ago
        > Why such archaic examples? I haven't understood why apps are not what you ask, so I tried to remember some well-known technologies/approaches. > Does the idea of circumventing a refresh offend you? Yes because I prefer to request things from online when I want but not when my device wants.
        shanebellone 3y ago
        "I haven't understood why apps are not what you ask, so I tried to remember some well-known technologies/approaches." I'm talking about websites that function like apps but have the privacy/security benefits of being sandboxed inside the browser (accessed by URL or link). It seems we may be talking about different things. I am not advocating for downloadable apps (I've never liked the app store paradigm nor the access it grants random developers). I'm advocating for more capable websites (which IMO "ought" to protect user data--not leverage it).
        eimrine 3y ago
        > I'm talking about websites that function like apps but have the privacy/security benefits of being sandboxed inside the browser (accessed by URL or link). What privacy benefits are not being realized by the current approach? If I want privacy, I can just disable JS for not letting some website know too much about my device. But in general, privacy is a joke since Edward Snowden's revelations. > I'm advocating for more capable websites (which IMO "ought" to protect user data--not leverage it). What opportunities are not being realized with the current approach? Who will be responsible for protecting user data, given that every website/resource/service strives to sell Alphabet/Meta as much data about you as possible.

I am a big fan of RMS and I find promising to promote his way of naming things everywhere. Here are two recent links which explain this word choice. [1] https://www.stallman.org/archives/2023-jul-oct.html#26_September_2023_(How_to_really_know_a_person) https://www.stallman.org/archives/2023-jul-oct.html#26_Septe... [2] https://www.stallman.org/archives/2023-jul-oct.html#11_September_2023_(Smart_device_collect_excess_information) https://www.stallman.org/archives/2023-jul-oct.html#11_Septe...

shanebellone 3y ago
Ah, but that's not that case here at all. It's not an app. It's still a sandboxed web page. The only difference is the communication method. Rather than a transactional client-server relationship, we adopt the media-steaming approach post-load. That is to say: You would load your desired website (the standard way) and then experience a "refresh-less" session for the duration of your visit.
- eimrine 3y ago
  Do you propose thin or thick client? How about Java applets or MS Silverlight?
  - shanebellone 3y ago
    Why such archaic examples? Imagine visiting this website, Hacker News, to read a few posts/discussions. Does the idea of circumventing a refresh offend you? You could click into a threaded discussion (from the homepage) and back without triggering a reload or needing the data beforehand. Other than the indexability problem, it seems like an ideal solution. In many use cases, the indexability problem is actually a feature too.
    - eimrine 3y ago
      > Why such archaic examples? I haven't understood why apps are not what you ask, so I tried to remember some well-known technologies/approaches. > Does the idea of circumventing a refresh offend you? Yes because I prefer to request things from online when I want but not when my device wants.
      - shanebellone 3y ago
        "I haven't understood why apps are not what you ask, so I tried to remember some well-known technologies/approaches." I'm talking about websites that function like apps but have the privacy/security benefits of being sandboxed inside the browser (accessed by URL or link). It seems we may be talking about different things. I am not advocating for downloadable apps (I've never liked the app store paradigm nor the access it grants random developers). I'm advocating for more capable websites (which IMO "ought" to protect user data--not leverage it).
        eimrine 3y ago
        > I'm talking about websites that function like apps but have the privacy/security benefits of being sandboxed inside the browser (accessed by URL or link). What privacy benefits are not being realized by the current approach? If I want privacy, I can just disable JS for not letting some website know too much about my device. But in general, privacy is a joke since Edward Snowden's revelations. > I'm advocating for more capable websites (which IMO "ought" to protect user data--not leverage it). What opportunities are not being realized with the current approach? Who will be responsible for protecting user data, given that every website/resource/service strives to sell Alphabet/Meta as much data about you as possible.