How do you keep up to date with any changes in the guides? I have tried following the GitHub repository as an RSS feed but it floods the feed with too many minor things like fixing spelling.
Is there a way to only be notified when something bigger happens, for example, new service gets added or removed or a completely new guide is added?
There is an RSS feed for the forum.
Latest topics: Privacy Guides - Latest topics
Latest posts: Privacy Guides - Latest posts
I think the OP meant something more monthly-newsletter-like “hey, we have added this and this service to the recommended, while this service lost out trust (linking blog). Over than that there is a new guide for X Y Z, check them out”
Forum RSS is about the forum, not the site.
yes i need this as well. would love some form of changelog just for adding /removing recommendations.
Maybe this
Hmm, your suggestion to follow “releases” seems better than “commits” page I’m following now:
It would not flood the RSS feed with entries for every single commit and just give the summary. I like this more.
However, the release summary still has lots of stuff like “Fix Italian flag icon” or “Bump crowdin/github-action from 1.9.0 to 1.10.0” which I’m not really interested in.
It’d be nice to be able to distinguish things such as “Add Notesnook” or “Remove Startmail, as it’s not zero-knowledge”.
@jonah Do you think it would make sense to separate these things into different sections like application developers do with features and bugs?
For example, KeePassXC has something similar where they have “Changes” and “Fixes”:
It would be much easier see the bigger changes such as adding/removing services or more major edits like rewriting the whole paragraph or restructuring the whole page.
The releases page and associated RSS feed is indeed the best way to stay up to date with changes to the website.
I don’t know about the sections thing. Currently the release notes are automatically generated, which saves us a good amount of time and keeps things at least consistent. Manually writing notes just so they’re a bit cleaner is pretty low priority for us at the moment. We do try to bold the biggest changes in each release if applicable.
Why is it necessary for someone to stay updated on PrivacyGuides?
This appears to be a fundamental problem with PrivacyGuides, highlighting severe deficiency in providing content that stands the test of time and instead disseminates misleading information.
As a reader, I anticipate that I would only need to visit the site once.
…what? 
The world is constantly changing. For example, one of our recommended gift card marketplaces, Cake Pay, shut down yesterday out of the blue. Adjusting that recommendation doesn’t lower the quality of Privacy Guides, and we don’t have a crystal ball to predict the future of the privacy landscape.
It is not surprising that Cake Pay, a service that is less than a year old, has shut down. The question arises as to why such a new service was recommended initially, considering that it had not proven its reliability over time.
It might not lower the quality but it does impact the accuracy and reliability of the site. After all, what’s the point of receiving recommendations if they cannot be relied upon for 5+ years?
Technology is a fast paced industry, what is recommended today should definitely not be expected to be relied in 5 years. If that is your standard is very unrealistic.
Privacy Guides is a living document and the recommendations change often over time, because the best tools at any given moment change over time. There is no perfect setup that never changes.
This being said, I did want to use the blog to post things like news about other projects, big changes to recommendations, etc., but the rest of the @team was strongly against posting things like that for various reasons 
If privacy is your top priority and you have a choice between:
Often I’d pick the former. Unless you’re talking about something like email or any other service where the shutdown would negatively impact you.
I’ve changed my mind on this, it makes sense. The release notes are now split into “What’s Changed” (important) and “Other Changes” (less important) sections, as you can see on the latest release:
I think we’ll try this out for a bit, it does communicate the big things more cleanly.
For me personally the forum here is the best way to keep up but that’s a time investment I like to make.
In periods I have less time on hands I check the release changes on GitHub indeed. That works well imo.