home.social

Search

222 results for “labgrid”

  1. The Content Security Policy stuff (called "CSP") in browsers is rather a pain to set up. It's useful for security: basically, you can say "this page is allowed to load X, Y, and Z", and if the page tries to load anything else, it'll be denied. #stuartwriting 2/6

  2. The Content Security Policy stuff (called "CSP") in browsers is rather a pain to set up. It's useful for security: basically, you can say "this page is allowed to load X, Y, and Z", and if the page tries to load anything else, it'll be denied. #stuartwriting 2/6

  3. The Content Security Policy stuff (called "CSP") in browsers is rather a pain to set up. It's useful for security: basically, you can say "this page is allowed to load X, Y, and Z", and if the page tries to load anything else, it'll be denied. #stuartwriting 2/6

  4. The Content Security Policy stuff (called "CSP") in browsers is rather a pain to set up. It's useful for security: basically, you can say "this page is allowed to load X, Y, and Z", and if the page tries to load anything else, it'll be denied. #stuartwriting 2/6

  5. A #WebPrivacy tip.

    Most web pages use third-party stuff somehow; web fonts, images, videos, JavaScript. It can be useful (and eye-opening for you, the page developer) to see what these things actually do. Do you know about Content-Security-Policy-Report-Only? #stuartwriting 1/6

  6. A #WebPrivacy tip.

    Most web pages use third-party stuff somehow; web fonts, images, videos, JavaScript. It can be useful (and eye-opening for you, the page developer) to see what these things actually do. Do you know about Content-Security-Policy-Report-Only? #stuartwriting 1/6

  7. A #WebPrivacy tip.

    Most web pages use third-party stuff somehow; web fonts, images, videos, JavaScript. It can be useful (and eye-opening for you, the page developer) to see what these things actually do. Do you know about Content-Security-Policy-Report-Only? #stuartwriting 1/6

  8. A #WebPrivacy tip.

    Most web pages use third-party stuff somehow; web fonts, images, videos, JavaScript. It can be useful (and eye-opening for you, the page developer) to see what these things actually do. Do you know about Content-Security-Policy-Report-Only? #stuartwriting 1/6

  9. A #WebPrivacy tip.

    Most web pages use third-party stuff somehow; web fonts, images, videos, JavaScript. It can be useful (and eye-opening for you, the page developer) to see what these things actually do. Do you know about Content-Security-Policy-Report-Only? #stuartwriting 1/6

  10. 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

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. Anybody know anything about blockprotocol.org/? @eli mentioned it at #TechMids and I’ve been reading about it. It seems to be an attempt to build a standard protocol for components which are exchangeable across websites, but which doesn’t want to be solely Web Components (presumably to get framework people on board). Seems a reasonable idea, but with zero interest — I’d never even heard of it. Does everyone else know about this and I don’t?

  25. Watching @eli talking at #TechMids about data storage throughout history, from Ea-Nasir’s letter through core rope memory (they explained this to me earlier, very cool) and now on to hard disks

  26. Rather impressed by @andypiper’s Framework laptop at #TechMids. I knew it had all the swappable parts, but I hadn’t realised it was pretty. If I buy another laptop, it might be that one, especially since I probably need a new one with USB-C now that some venues expect you to connect that way to their projector.

  27. first up at #TechMids is Hannah Mitchell. This is a great talk, having seen it at ManageOps. Hannah has a framework, a structure for what she calls “creating Happy at work”. Worth learning about!

  28. That would be #TechMids and #dodbrum together, of course! Huge screen (@SecondeJ for scale) in the auditorium at Millennium Point. It’s quite a nice venue, I think. You get to see me speak in front of it too, but… tomorrow. So you have a day to prepare and watch other people talk