4 ms·
Maybe we can also have a network.txt file, containing all 3rd party services that the website (both client and server?) will connect to. Then you can decide up
by harryvederci 4y ago
Maybe we can also have a network.txt file, containing all 3rd party services that the website (both client and server?) will connect to.
Then you can decide up-front if you want to make use of a website, and block any outgoing calls that aren't mentioned in network.txt.
It's just an idea. The server-side part is hard to verify (especially for closed source software), of course.
- Wronnay 4y agoThat's actually a good idea and would make it easier to create GDPR solutions. E.g. if a Agency needs to create a new cookie banner, they could just look at the network.txt instead of having to call the client multiple times (one call won't be enough because most clients don't have any clue which 3rd party solutions they actually use)
- Wronnay 4y agoI wrote down my Idea how this could look: https://github.com/CMiksche/network.txt https://github.com/CMiksche/network.txt
- O__________O 4y agoQuick look shows you’re limiting it to “data transmission” — but to me it should list all network connections, regardless of if data sent. If you’re limiting it to just data, I would just call it data.txt.
- Wronnay 4y agoI was primarily thinking of a file which can be used for generating e.g. privacy policies and cookie banners. I am welcome to PRs and Issues - feel free to show me how you would structure it ;-)