Remove Raivo OTP #2251
Merged
Remove Raivo OTP #2251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
ghost
approved these changes
Jul 27, 2023
freddy-m
approved these changes
Jul 27, 2023
ph00lt0
approved these changes
Jul 27, 2023
jonaharagon
force-pushed
the
jonaharagon/remove-raivo-otp
branch
from
7ba851f to
b6d8df1
Compare
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
dngray
added
the
c:software
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this PR:
We've removed (and occasionally relisted, to be fair) a number of apps/services post-acquisition. The general lack of communication (e.g. https://github.com/raivo-otp/marketing-website/issues/19) leaves a lot to be desired, so I don't think we should be promoting Raivo OTP until this is sorted out, then we can reevaluate. If we still don't like Raivo OTP, a replacement alternative can be added in a separate PR.