home.social

Search

222 results for “labgrid”

  1. To learn more about fingerprinting, why it's bad for user privacy, and what you can do as a developer, check out Learn Privacy at web.dev/learn/privacy/fingerpr. And if you like that and want me to write things for you, get in touch! #stuartwriting 5/5

  2. To learn more about fingerprinting, why it's bad for user privacy, and what you can do as a developer, check out Learn Privacy at web.dev/learn/privacy/fingerpr. And if you like that and want me to write things for you, get in touch! #stuartwriting 5/5

  3. To learn more about fingerprinting, why it's bad for user privacy, and what you can do as a developer, check out Learn Privacy at web.dev/learn/privacy/fingerpr. And if you like that and want me to write things for you, get in touch! #stuartwriting 5/5

  4. To learn more about fingerprinting, why it's bad for user privacy, and what you can do as a developer, check out Learn Privacy at web.dev/learn/privacy/fingerpr. And if you like that and want me to write things for you, get in touch! #stuartwriting 5/5

  5. To learn more about fingerprinting, why it's bad for user privacy, and what you can do as a developer, check out Learn Privacy at web.dev/learn/privacy/fingerpr. And if you like that and want me to write things for you, get in touch! #stuartwriting 5/5

  6. In practice, most developers and most businesses have no need to fingerprint users. If you require users to sign in, then they identify themselves to you, with consent, and in a way that they can unilaterally opt out of at any time they choose. This protects their privacy. #stuartwriting 4/5

  7. In practice, most developers and most businesses have no need to fingerprint users. If you require users to sign in, then they identify themselves to you, with consent, and in a way that they can unilaterally opt out of at any time they choose. This protects their privacy. #stuartwriting 4/5

  8. In practice, most developers and most businesses have no need to fingerprint users. If you require users to sign in, then they identify themselves to you, with consent, and in a way that they can unilaterally opt out of at any time they choose. This protects their privacy. #stuartwriting 4/5

  9. In practice, most developers and most businesses have no need to fingerprint users. If you require users to sign in, then they identify themselves to you, with consent, and in a way that they can unilaterally opt out of at any time they choose. This protects their privacy. #stuartwriting 4/5

  10. In practice, most developers and most businesses have no need to fingerprint users. If you require users to sign in, then they identify themselves to you, with consent, and in a way that they can unilaterally opt out of at any time they choose. This protects their privacy. #stuartwriting 4/5

  11. A #WebPrivacy tip.

    Fingerprinting is the act of trying to covertly identify a user or distinguish one user from another by reading stuff about their setup. Web sites and web browsers can do this, and your job as a developer is to protect your users from it. #stuartwriting 1/5

  12. A #WebPrivacy tip.

    Since the beginning, web browsers have sent a description of themselves with every page: the User-Agent. For nearly as long web devs have been begged to not use the UA to change stuff per browser, and for all that time devs did it anyway #stuartwriting 1/4