-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Implement private and public donations #2088
Conversation
It would be nice to write a blog post about this new feature, and share it on our long-dormant social media accounts. I can write the blog post tonight using screenshots from this developing branch, so that you have time to review it before publishing it. |
Nice to see this feature coming. |
There will be a blog post of course. I was planning to write it myself as usual, but you can try to do it if you want to, @jorgesumle. |
Users can now thank their sponsorsWe are happy to announce that users can now allow non-anonymous donations. What do we mean? Donations in Liberapay were anonymous until now, so users could not thank their sponsors. By adding this feature we hope that donators can now be credited for their contribution. If you are a creator who wants to allow donators reveal their identity to you and to the public, you should activate this new feature in the Receiving>Patrons menu... When you activate this feature, you will see something like this: With this feature enabled users will be able to select a privacy level in the donation form: |
I believe that the following code should be added to
I don't have much time right now to write a proper blog post, but the comment and the images above can be useful to get you started. We should also show the list of patrons. I didn't have time to connect the payment account and play with fake users to show this. @Changaco, can you finish my work? I can help review it before publishing. It would be nice to figure liberapay/salon#136 out. We could also post it in Spanish, French, etc., and reach more people, and under something like |
The last two weeks have been more busy than expected, so I'm a little late on this, but everything should be ready tomorrow. The blog post is almost complete, here's the link to the draft: https://medium.com/@liberapay/lifting-the-veil-of-anonymity-479dadd369be |
The deployment is done. Any feedback on the blog post draft before I publish it? |
Sure!
The colon is incorrect there, it should only be used "to introduce a list when the introductory phrase is an independent clause" (not in conditional sentences or dependent clauses). Also, the "then" in conditional sentences can be omitted if you want.
This sentence sounds overly complicated to me. I would rewrite it to "these lists will be empty until your donors opt-in and input their public names".
I'd say "new donors" instead of "any new donor" here.
I'd say "it will be possible". I think "become possible" is incorrect. |
Thanks. I've made some cosmetic changes.
Not containing names isn't the same thing as being empty. |
"these lists won't have any name until your donors opt-in and input them" or "these lists won't have any name until your donors opt-in and input their public names". |
I've rewritten the sentence in a very different way, and published the blog post. |
Nice to see this feature coming in, congratz! |
So far 354 creators have opted-in to see who their donors are, and 84 have opted-out. SELECT value, count(*)
FROM ( SELECT DISTINCT ON (participant)
payload->>'patron_visibilities' AS value
FROM events
WHERE type = 'recipient_settings'
AND payload ? 'patron_visibilities'
ORDER BY participant, ts DESC
) x
GROUP BY value;
value | count
-------+-------
1 | 84
7 | 354
(2 rows) |
This branch will close #271. I'm hoping to complete and merge it this week, then give translators two weeks to do their work.