unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: patreon or alternative?
Date: Wed, 06 Jun 2018 10:52:52 -0400	[thread overview]
Message-ID: <874ligdl17.fsf@fastmail.com> (raw)
In-Reply-To: <87efhn3exp.fsf@aminb.org> (Amin Bandali's message of "Sun, 03 Jun 2018 14:25:38 -0400")

Amin Bandali <aminb@gnu.org> writes:

> I can think of Liberapay [0] and fosspay [1] off top of my head.
> Liberapay is licenses under CC0 and fosspay under MIT.
>
> Liberapay seems to be using MangoPay behind the scenes, with whom
> they've apparently run into trouble with, and are in danger of
> closing ([2]).  Worth keeping an eye on.

Ahh man.  I thought librepay was here to stay!  I didn't realize that it
had some issues.

>
> fosspay, on the other hand, uses Stripe for doing the actual
> payment, which requires running non-free JS I believe.

Also sad day.  :)   Let's hope gnu wallet (is that what's it's called)
reaches 1.0 soon.

>
> There used to be a Gittip (later, Gratipay) at one point but it
> sadly closed down last year. Liberapay and fosspay seem to be the
> least worst of the available options, but I'd love to hear if
> there are any better options.
>
> [0]: https://github.com/liberapay/liberapay.com
> [1]: https://github.com/SirCmpwn/fosspay
> [2]: https://github.com/liberapay/salon/issues/232
>
> P.S. PayPal seems to have an Apache-2.0 licensed JS checkout
> implementation here [4] but I don't know whether or not by using
> that one could entirely avoid non-free JS when making a payment.
>
> [4]: https://github.com/paypal/paypal-checkout
>
> Best,
>
> -amin



  reply	other threads:[~2018-06-06 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 15:26 patreon or alternative? Stephen Leake
2018-06-03 18:25 ` Amin Bandali
2018-06-06 14:52   ` Joshua Branson [this message]
2018-06-04  4:16 ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ligdl17.fsf@fastmail.com \
    --to=jbranso@fastmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).