opentermsarchive / contrib-versions Goto Github PK

See https://news.ycombinator.com/item?id=37516523

Following this issue, Parent Organization Terms was renamed into Terms of Service, therefore their histories need to be merged to facilitate navigation.

Until then, to explore the full history of Terms of Service terms, the history of Parent Organization Terms terms should also be taken into account.

This repos GitHub description is

Documentation: https://github.com/OpenTermsArchive/contrib-versions#exploring-the-versions-history

The README.md has no such section to link to, and never did.

The ambanum/OpenTermsArchive repository README.md has that section though, so the link seems to link the wrong repository.

https://github.com/ambanum/OpenTermsArchive/blob/main/README.md#exploring-the-versions-history

Following this issue, Parent Organization Privacy Policy was renamed into Privacy Policy, therefore their histories need to be merged to facilitate navigation.

Until then, to explore the full history of Privacy Policy terms, the history of Parent Organization Privacy Policy terms should also be taken into account.

Following this discussion, Ad Publishing Policy was renamed into Acceptable Use Policy, therefore their histories need to be merged to facilitate navigation.

Until then, to explore the full history of Acceptable Use Policy terms, the history of Ad Publishing Policy terms should also be taken into account.

Following this discussion, Community Guidelines sub types was removed, therefore the history of every such subtypes should be merged.

Until then, to explore the full history of Community Guidelines terms, the history of every subtype terms should also be taken into account.

Since 25 of January, the published dataset is not complete. It contains 90 services instead of 281, and a total of 899 versions instead of 16 504.

Probably the reason for OpenTermsArchive/opentermsarchive.org#102.

Hypothesis:

I guess this is consistent with the move to production on MongoDB, but it seemed to me that we had since integrated all of the historical data into Mongo. If this is the case, maybe the versions were not regenerated correctly? This is all the more surprising since the versions published on GitHub seem to be complete (there are well over 280 files in https://github.com/ambanum/OpenTermsArchive-versions).

It has not been checked if the datasets of France and Dating are complete.

Once this issue is fixed, all incomplete datasets should be erased.

As it has been tracked in french instead of english at the beginning, and as It is considered to not be the same document, we should remove it from the version history

Some changes are applied “officially” and modify the “last updated” date.
Some changes are applied, yet are not detectable by the end user if they don't use CGUs.

How often are terms updated without the users' knowledge?
In which proportion?
Do “official” changes always correlate with “significant” changes?

Not sure where I can suggest new sites to track but all the various pages on privacy.com. Motivation for this is after logging I'm just told essentially "We updates are terms to better reflect your credit card usage see here or click accept" and it just takes you to the page without any overview of what actually changed which was quite annoying.

• Stop instance.
• Update ops.
• Rename versions folder on instance server to versions-before-switching-to-main.
• Rename master into main through GitHub UI.

Hi,

I'm opening this one to discuss about possible alternative diff viewer (to Github's built-in), to improve the quality of diffs.

In particular, Github seems to have troubles with diffs within a line. See for instance 270a138?branch=270a1389a8fab67723c7b5a9f61efacc7ceb3734&diff=unified#diff-28600bbf50094536c29f48719962e1fdL124-R124 where the full line is shown as being modified, leaving it up to the reader to compute the actual diff.

On the other hand, a proper diff tool with word-diff capability (https://editor.mergely.com/?wl=1 here) is able to provide a much useful diff:

So this issue is here to discuss about possible alternative tools and the most easy to deploy ones.

Best