This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] https://www.ripe.net/ inappropriate javascript
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sat May 4 15:09:52 CEST 2019
> On 3 May 2019, at 11:47, Nick Hilliard (INEX) <nick at inex.ie> wrote: > > The RIPE NCC can't fix this issue, but it would be a good starting point to note that the use of trackers raises deeply uncomfortable questions about online privacy, with no clear answers. All the more reason for the NCC to keep well away. Perhaps we do need to have a formal policy on this issue.
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]