9
14
Fork
You've already forked website
20

Recipe Request: Google to Proton #177

Open
opened 2026年05月21日 20:04:14 +02:00 by theDoctor · 2 comments

I suppose this is somewhat controversial but the reasoning would be the following: Google is a whole ecosystem and migrating away can be incredibly tedious because they offer so much stuff. One way would be to swap out services piece by piece, another way would be to go to another provider that offers a similar suite of products.

The only one that comes reasonably close and is non-US and privacy-friendly (that I am aware of) is Proton, hence the suggestion.

On the other hand, Proton is a single, centralized entity and such a recipe would surely be rather complex. Of course it would be possible to split this up but I'm not sure whether that would make sense.

Thoughts?

I suppose this is somewhat controversial but the reasoning would be the following: Google is a whole ecosystem and migrating away can be incredibly tedious because they offer so much stuff. One way would be to swap out services piece by piece, another way would be to go to another provider that offers a similar suite of products. The only one that comes reasonably close and is non-US and privacy-friendly (that I am aware of) is Proton, hence the suggestion. On the other hand, Proton is a single, centralized entity and such a recipe would surely be rather complex. Of course it would be possible to split this up but I'm not sure whether that would make sense. Thoughts?
Owner
Copy link

I think splitting this up would be the way to go. But having recipes, that target one provider - opens us up to the "chills for that provider" narrative

I think splitting this up would be the way to go. But having recipes, that target one provider - opens us up to the "chills for that provider" narrative

In that case, I would probably opt for separate recipes for each application and include several in the recommendations to migrate to. If Proton appears in multiple recipes, that should not automatically be a problem, I think.

In that case, I would probably opt for separate recipes for each application and include several in the recommendations to migrate to. If Proton appears in multiple recipes, that should not automatically be a problem, I think.
Sign in to join this conversation.
No Branch/Tag specified
main
translations-pages
translations-faq
adjust-upcoming-event-windows
enable-hidden-translated-routes
signal-contacts
faq-i18n-fallback
feat/homepage-variants
chore/replace-decap-submodule-with-published-packages
citesting
No results found.
No labels
cms/draft
guide
WIP
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
DI-Day/website#177
Reference in a new issue
DI-Day/website
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?