Component Translated Untranslated Untranslated words Checks Suggestions Comments
main MIT 80% 348 6,867 43 4 27 Browse
Project website https://github.com/andersju/webbkoll
Instructions for translators

https://github.com/andersju/webbkoll/blob/master/TRANSLATIONS.md

Translation license MIT main
Number of strings 1,795
Number of words 33,985
Number of characters 249,235
Number of languages 5
Number of source strings 359
Number of source words 6,797
Number of source characters 49,847
Language Translated Strings of total Untranslated Untranslated words Checks Suggestions Comments
English 15 4 Browse
French 6% 6% 336 6,588 5 1 3 Browse
German 11 Browse
Norwegian Bokmål 97% 97% 9 177 20 6 Browse
Swedish 99% 99% 3 102 3 3 3 Browse
modified

Comment added

Webbkoll / mainEnglish

@andersju No problem at all. Sorry, the explanation of "third-party service first-party cookies" is confusing me more than it is clarifying to me. At first I thought this meant cookies served for third parties but via the website (domain) itself, but now it sounds more like regular third-party cookies to me. If the latter was correct, I would completely remove all the "first-party" stuff, as I don't see what it is trying to accomplish/explain. Also, reading Rec. 47 carefully, the "there must already exist a relationship" part is incorrect. It just says to consider the relationship and, as an example, describes a case where there is a relationship.

To be honest, I would remove this sentence completely. If anything, I could imagine a sentence about the second part of the legitimate interest clause – that you also have to consider the interests or fundamental rights and freedoms of the visitor, and whether the processing is necessary to achieve what the interests aim at.

4 weeks ago
andersju

Comment added

Webbkoll / mainEnglish

@modified: another way of saying it might be, "In our view, 'lawfulness, fairness and transparency' means that, when you visit a website, you should know who is getting your data". So for example, if I visit foobar.com, I (as the visitor) should be informed exactly what's going on - is foobar.com also sending my data to some analytics company?

4 weeks ago
andersju

Comment added

Webbkoll / mainEnglish

Yep, thanks!

4 weeks ago
andersju

Comment added

Webbkoll / mainEnglish

@modified - sorry for the late reply. Amelia suggested this rephrasing: "But for this apply, there must already exist a relationship between the web visitor and the web site owner (GDPR Rec. 47), which calls into question the use of third-party service first-party cookies (i.e. if a service from a third party is integrated into your website, and this service uses cookies, those cookies are first-party cookies from the third-party service perspective, but the web visitor may not have visited your website to access the third party service at all; more likely, they visited your website to access your services)." Does that sound better? If so, I'll make the change in the source and update the translation files.

4 weeks ago
None

Committed changes

Webbkoll / mainGerman

Committed changes a month ago
modified

Suggestion removed

Webbkoll / mainGerman

The referrer header is privacy nightmare as it allows websites and services to track you across the web and learn about your browsing habits (and thus possibly private, sensitive information), particularly when combined with cookies.
Der Referrer-Header ist ein Albtraum für die Privatsphäre, da er es Websites und Diensten ermöglicht, dich im gesamten Web zu verfolgen und deine Surfgewohnheiten (und damit möglicherweise private, sensible Informationen) herauszufinden, insbesondere in Kombination mit Cookies.


###Kommentar bitte entfernen###
Albtraum ist die empfohlene Schreibweise https://www.duden.de/rechtschreibung/Albtraum
a month ago
modified

Translation changed

Webbkoll / mainGerman

The referrer header is privacy nightmare as it allows websites and services to track you across the web and learn about your browsing habits (and thus possibly private, sensitive information), particularly when combined with cookies.
Der Referrer-Header ist ein Alpbtraum für die Privatsphäre, da er es Websites und Diensten ermöglicht, dich im gesamten Web zu verfolgen und deine Surfgewohnheiten (und damit möglicherweise private, sensible Informationen) herauszufinden, insbesondere in Kombination mit Cookies.
a month ago
modified

Suggestion removed

Webbkoll / mainGerman

Note that <code>includeSubDomains</code> should be deployed at the base domain, i.e., <code>https://example.com</code>, <em>not</em> <code>https://www.example.com</code>. While we recommend the use of <code>includeSubDomains</code>, be <strong>very</strong> careful, as it means that <strong>all subdomains</strong> associated with the parent domain <strong>must</strong> support HTTPS. (They do not have to each have their own HSTS policy.)
Beachte, dass <code>includeSubDomains</code> auf der Hauptdomain eingesetzt werden sollte, d. h. <code>https://example.com</code>, <em>nicht</em> <code>https://www.example.com</code>. Auch wenn wir die Verwendung von <code>includeSubDomains</code> sehr empfehlen, so ist zu beachten, dass diese für <strong>alle Subdomains</strong> gilt. Diese <strong>müssen</strong> HTTPS unterstützen (eine HSTS-Richtlinie für jede einzelne Subdomain wird nicht benötigt).


###Kommentar bitte entfernen###
beispiel.de ist zwar eine legitime Beispiel-Domain, enthält aber Ressourcen aus Drittquellen (namentlich Google). Diese Tatsache sollte gegen die Erwähnung sprechen, weil dieses Projekt versucht, den Datenschutz zu fördern.
a month ago
modified

Translation changed

Webbkoll / mainGerman

Note that <code>includeSubDomains</code> should be deployed at the base domain, i.e., <code>https://example.com</code>, <em>not</em> <code>https://www.example.com</code>. While we recommend the use of <code>includeSubDomains</code>, be <strong>very</strong> careful, as it means that <strong>all subdomains</strong> associated with the parent domain <strong>must</strong> support HTTPS. (They do not have to each have their own HSTS policy.)
Beachte, dass <code>includeSubDomains</code> auf der Hauptdomain eingesetzt werden sollte, d. h. <code>https://beispiel.deexample.com</code>, <em>nicht</em> <code>https://www.beispiel.deexample.com</code>. Auch wenn wir die Verwendung von <code>includeSubDomains</code> sehr empfehlen, so ist zu beachten, dass diese für <strong>alle Subdomains</strong> gilt. Diese <strong>müssen</strong> HTTPS unterstützen (eine HSTS-Richtlinie für jede einzelne Subdomain wird nicht benötigt).
a month ago
andersju

Comment added

Webbkoll / mainGerman

@modified Noted, will look into it.

a month ago
Browse all project changes

Activity in last 30 days

Activity in last year