-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blog: CCS wallet incident #2208
Conversation
✅ Deploy Preview for barolo-time-757cf9 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
81a9d16
to
eccc010
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked and can confirm that the PR does what the PR claims: It adds a blog post to the getmonero.org blog about this incident, as a copy of Luigi's announcement on GitHub.
What I can't judge of course: Whether making such a blog post in this form is a good idea in the first place, and whether people agree to do so.
My personal opinion: Looks ok to do so, because there will be more communication to come.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if core wants to send the message sent on github as a blog post. Better ask them what plans they have first. If this is good to go with them, we can quickly merge and publish it.
5a0f164
to
1e051e5
Compare
after discussion, a simple explination, pointing to the meta which contains the full detail was agreed upon, i have pushed a draft of this |
fc40e2d
to
10fe60e
Compare
7f665de
to
5385841
Compare
e08e2a7
to
802183c
Compare
after some discussion, a simple summary that points to the meta issue containing all the details has been agreed upon. i have pushed a draft here.
copy of monero-project/meta#916