4 ms·

That's why I'm working on a cookieless authentication platform on which I can base all my future projects. https://github.com/zelon88/HRCloud3 https://github.c

That's why I'm working on a cookieless authentication platform on which I can base all my future projects. https://github.com/zelon88/HRCloud3 https://github.com/zelon88/HRCloud3

daveoc64 5y ago
Eh? Cookies have very little to do with any of the laws like GDPR in the EU. The issue these laws cover is obtaining consent for using personal data for non-essential purposes. Things like authentication are typically deemed to be "essential", and therefore do not require consent. If you do something which does require consent, then you must ask for permission - regardless of what technology you are using to implement that (cookies or not).
- zelon88 5y ago
  The goal is not to circumvent consent. I find cookies to be an outdated concept in general. More developers should be embarrassed about making a client fire up 52 connections to 20 domains with 17 cookies just so they can read 0.6kb of text.
  - 0x073 5y ago
    Why are cookies outdated in general? What does 52 connections to 20 domains and 17 cookies have something to do with cookies in general?
    - zelon88 5y ago
      To me it follows a pattern of always taking the easy route at the expense of the user. Don't host your own fonts, just link to Google. Don't host your own scripts, link to Google. Who knows who sees those access logs. Need to Auth the user? Here store this encoded personal data for me. Gee, I like this feature <copy/paste in 2mb worth of frameworks to enable 6 lines of functionality>.
      - ranguna 5y ago
        I still don't see how this is related to cookies.
        zelon88 5y ago
        Everybody except devs hate cookies. Everybody hates hearing about them, answering questions about them, having some that are innocuous and some that are "scary." So why do devs force them on everybody? They aren't required unless you require them. So stop requiring them. Nobody cares how useful they are for you. They have a bad reputation and make for a bad experience. So stop using them. Just take that tool out of your toolbox, and burn it. The public has spoken but apparently I'm the only one listening.
        0x073 5y ago
        Everyone hates cookiebanners. Noone except devs know that browsers use cookies and noone cares. Cookiebanners are no restricted to cookies, it's about tracking, storing and sharing the information with third parties. If you use cookies for login you don't need a cookiebanner, because it's necessary. If you use cookie for tracking you need a cookiebanner, if you track the user with another technology you still need a cookiebanner.
        daveoc64 5y ago
        You seem to be attributing issues to cookies that are actually problems with what people are doing with them. Nobody dislikes cookies - when used correctly, users don't know they exist. This site seems to be doing a great job with them - there's a single cookie to store my login session. What people don't like is annoying prompts - they claim to be about cookies, but really they're asking permission to track users for nefarious purposes. If you don't track users, you don't need to ask - and that's the case whether you use cookies or not. If you track users, you need to ask permission no matter what technology you use. Again, that's the case on this site - no tracking = no need for annoying popups.
- d13 5y ago
  This absolutely correct yet very few seem to know this.
  - number6 5y ago
    One other no one seems to know is, that it's not only about cookies but every information someone saves on your pc
tomjen3 5y ago
Not sure why you would want that - a login cookie is very, very much a functional cookie and you don't need permission to use them. On the other hand, if you do tracking that is personally identifiable you need permission no matter what technology you use.
- zelon88 5y ago
  Casual users will trust a platform more if they know it contains no cookies at all.

That's why I'm working on a cookieless authentication platform on which I can base all my future projects. https://github.com/zelon88/HRCloud3 https://github.com/zelon88/HRCloud3

daveoc64 5y ago

Eh? Cookies have very little to do with any of the laws like GDPR in the EU. The issue these laws cover is obtaining consent for using personal data for non-essential purposes. Things like authentication are typically deemed to be "essential", and therefore do not require consent. If you do something which does require consent, then you must ask for permission - regardless of what technology you are using to implement that (cookies or not).

zelon88 5y ago
The goal is not to circumvent consent. I find cookies to be an outdated concept in general. More developers should be embarrassed about making a client fire up 52 connections to 20 domains with 17 cookies just so they can read 0.6kb of text.
- 0x073 5y ago
  Why are cookies outdated in general? What does 52 connections to 20 domains and 17 cookies have something to do with cookies in general?
  - zelon88 5y ago
    To me it follows a pattern of always taking the easy route at the expense of the user. Don't host your own fonts, just link to Google. Don't host your own scripts, link to Google. Who knows who sees those access logs. Need to Auth the user? Here store this encoded personal data for me. Gee, I like this feature <copy/paste in 2mb worth of frameworks to enable 6 lines of functionality>.
    - ranguna 5y ago
      I still don't see how this is related to cookies.
      - zelon88 5y ago
        Everybody except devs hate cookies. Everybody hates hearing about them, answering questions about them, having some that are innocuous and some that are "scary." So why do devs force them on everybody? They aren't required unless you require them. So stop requiring them. Nobody cares how useful they are for you. They have a bad reputation and make for a bad experience. So stop using them. Just take that tool out of your toolbox, and burn it. The public has spoken but apparently I'm the only one listening.
        0x073 5y ago
        Everyone hates cookiebanners. Noone except devs know that browsers use cookies and noone cares. Cookiebanners are no restricted to cookies, it's about tracking, storing and sharing the information with third parties. If you use cookies for login you don't need a cookiebanner, because it's necessary. If you use cookie for tracking you need a cookiebanner, if you track the user with another technology you still need a cookiebanner.
        daveoc64 5y ago
        You seem to be attributing issues to cookies that are actually problems with what people are doing with them. Nobody dislikes cookies - when used correctly, users don't know they exist. This site seems to be doing a great job with them - there's a single cookie to store my login session. What people don't like is annoying prompts - they claim to be about cookies, but really they're asking permission to track users for nefarious purposes. If you don't track users, you don't need to ask - and that's the case whether you use cookies or not. If you track users, you need to ask permission no matter what technology you use. Again, that's the case on this site - no tracking = no need for annoying popups.
d13 5y ago
This absolutely correct yet very few seem to know this.
- number6 5y ago
  One other no one seems to know is, that it's not only about cookies but every information someone saves on your pc

tomjen3 5y ago

Not sure why you would want that - a login cookie is very, very much a functional cookie and you don't need permission to use them. On the other hand, if you do tracking that is personally identifiable you need permission no matter what technology you use.

zelon88 5y ago
Casual users will trust a platform more if they know it contains no cookies at all.