Closed Changaco closed 7 years ago
Just our of curiosity: Who is running the payday if @Changaco is sick or on vacation?
@aggsol Theoretically one of the other codirectors could run payday if I'm unable to do it. Relevant issues: #32 and https://github.com/liberapay/liberapay.com/issues/485.
@Changaco Ok, let your replacement do it once in a while for practice.
New release: Unicorn | MANGOPAY API Docs
New functionality included in this release
- Cards that you register now have a unique identifier called the
Fingerprint
- this value will always be the same regardless of how many times you register the same physical card, or for whichever user. We'll be adding more functionality to do with this in the future (like card unicity tools, fraud prevention and the same information for web payins).- Add a new parameter for legal users for their registered/official company number called
CompanyNumber
which is not required at this time, but we highly recommend that you provide this informationImprovements included in this release
- We're excited to announce the next stage in our performance and scalability improvements whereby you'll find that the transactions list responses are now much quicker and more reliable
- Following your feedback, we've now removed the last phrase from direct debit payment notification emails which said "You'll be notified three days in advance of any further payments" as some end-users found this unnerving if they were doing a one-off payment
- Validated KYC documents for a user are shown in their user object, however previously the value given was an internal reference - we've now changed this to show the actual document ID instead which should be more useful
- The version part of the API URL is now case insensitive, to avoid any confusion
- The
CreditedUserId
is now correctly shown for repudiation refunds- The URL of your branding logo is now given in HTTPS format for increased security
- We've optimised a process when an intial payment for a card fails in some cases but the card validity was not correctly set to show that it was invalid
- There is now a specific error when you try and transfer funds to the same wallet
New release: Dragon | MANGOPAY API Docs
New functionality included in this release
- You can now see when a KYC or dispute document has been processed by us (either to be accepted, or refused) via the new parameter
ProcessedDate
- We've added a new endpoint to list the disputes that can (and need to be) settled to assist you in your processing
Improvements included in this release
- The file formats .doc and .docx are no longer accepted for KYC/dispute document pages to help us provide you with the quickest service possible
- We've fixed a bug whereby hook notifications and events were not triggered for transfer and payout refunds, as well as for external instruction payins
- The disputed amount of a dispute previously didn't include the payment's fees, so we've now corrected this
- There is now a specific error if you try and create a bankwire payin which will result in a negative credited funds
- We've corrected a potential error in rare cases for some direct debit mandate creations
- If you try and cancel a preauthorisation that hasn't yet been completed (because it's awaiting the 3DS step for example), you'll now get a specific error instead of an error 500
- If a bank account doesn't support direct debit, you'll now get a specific error when creating a mandate for this bank account
For some reason a legitimate GET request to https://liberapay.com/svnet/emails/verify.html has been repeated thousands of times (more than 2 requests per second for more than 30 minutes). I noticed the flood in the logs and "blocked" the URL at Cloudflare.
Edit: I've sent an email to the user.
Why We Terminated Daily Stormer (Cloudflare)
@Changaco We have a writer of the Daily Stormer on liberapay (https://liberapay.com/Zeiger/) Do you see a need for action?
@aggsol I've put that profile into isolation mode (you won't find it in search results anymore).
Good decision.
Why We Terminated Daily Stormer (Cloudflare)
That's not good. Censorship is always bad. I'm still beign blocked by Cloudflare just for using Tor, so I can't even read that article.
@aggsol I've put that profile into isolation mode (you won't find it in search results anymore). Good decision.
Why did you do that? Is there any section in the terms of service that can justify that action?
Why did you do that?
To prevent others from finding the profile by accident or the way @aggsol did.
Is there any section in the terms of service that can justify that action?
Yes, article 1 paragraph 2: "The service normally allows the user to increase the visibility of its profile in various way, but the organization reserves the right to disable the user's access to those features."
Yes, article 1 paragraph 2
Thanks for the reference. But when you do that could you just write a justification like why exactly that measure is applied. It looks very arbitrary and not everyone necessarily agree with that measure. Also that undermines free of speech, see http://www.tomshardware.com/news/eff-daily-stormer-free-expression,35258.html. It looks scary that you could do that to any account without a proper justification.
I must say I'm antifascist, and I don't defend their ideas.
Hi all, I just wanted to let you know that - after a few months being a liberapay user - a project of which I am core developer started accepting donations on liberapay. The project is AGPLv3 licensed and all core developers are EU citizens, so liberapay was a perfect fit. As we are not a legal entity we set up a team for now. I truly hope we can bring more visibility to liberapay as well, as the project has its niche of users and contributors (1500 stars on github).
shameless plug: if you have an android device and a pebble, miband, hplus or amazfit bip wearable, and don't like sending your data to the vendors' servers: we've got you covered. If you have another wearable device, we can help you getting it supported. Liberapay team: https://liberapay.com/Gadgetbridge Github repo: https://github.com/Freeyourgadget/Gadgetbridge/ Project blog: https://blog.freeyourgadget.org/ (a blogpost will follow soon) A tweet by me with the announcement: https://mobile.twitter.com/daniele_360/status/899167742842073088
@danielegobbetti That's great! I've retweeted your announcement.
Thanks!
We're getting significantly more traffic than usual today, mostly from https://www.reddit.com/r/linux/comments/6vq0a1/opensource_nofees_donationpatron_system/
This is a good way to see if people understand the basic concept, FAQs etc.
Someone created a Wikipedia page for Liberapay 3 weeks ago: https://en.wikipedia.org/wiki/Liberapay
For anyone here who would want to edit that page: Wikipedia:Conflict of interest and Wikipedia:FAQ/Organizations.
Some thoughts on GitFund:
I agree with you on all points, especially the money escrow is worrying. Also the way of "buying features" or driving the direction of development with money is IMHO not the way FOSS should operate.
For the record GitFund's founder answered me in their IRC channel, the conversation is continuing there. I'll try to post logs or a summary later.
Gratipay is relaunching again: https://github.com/gratipay/inside.gratipay.com/issues/1160.
I call bullsh*t on the whole calculation. It's clickbait for their relaunch.
I've just realized that we're currently transferring a bit more monetary value per week than Gratipay (their stats vs our stats).
Logs/summary of the conversation with GitFund's founder:
i don't know if you saw the conversation i had with Chad of Gratipay, but i'm in agreement for me, the ideal model is where projects and the people working on them get funded directly but, from talking to companies, this is (right now at least), a much harder sell and, with gitfund, i've tried to make the benefits be fairly symbiotic e.g. it's not just renting random ad space, but rather limited to just the sponsor name/logo + ad use for only recruitment it's not perfect, but at least provides something which makes it easier for companies to buy into
true it's only open source, but that can cover pretty much all open efforts, not just software? fwiw, a lot of my personal efforts in recent years have been around open source hardware
His plan is for GitFund to comply with financial regulations by getting its own licences, instead of delegating compliance to a partner like we do with MangoPay. He wants to do everything by the book and make sure GitFund respects the laws of every country in which it has users.
Here's what I said about this approach:
I see two possible outcomes if you decide to get your own licence(s):
- either you somehow manage to do things better than existing e-money platforms (Stripe Connect, Mangopay, etc), then you'll have an advantage over other open source funding platforms, but you'll also have people wanting to use the system you've built for other things than GitFund (i.e. you'll be encouraged to become a competitor of Stripe and the others);
- or you're going to waste time doing things that other e-money platforms are already doing as well or better than you and that will significantly slow down the development of GitFund without providing you with an advantage.
He answered:
ah, thanks for explaining — i think i better understand your line of reasoning now
New release: Rhinoceros | MANGOPAY API Docs
New functionality included in this release
- As you know, successful payouts can be rejected by the recipient bank (eg the bank account is now closed, or a savings account and can't receive funds) - in this case, we will create a "payout refund" and the funds will be returned to the wallet. From now on, we'll also automatically disable the bank account so you can't use it again (if the refund reason is irreversible)
- Following our previous new functionality with regard to card fingerprints, we've added a new endpoint to list users that have registered the same card - this is useful for checking for potentially fraudulent cases, or different users who are actually the same in real life etc - more info
Improvements included in this release
- Following your feedback, the wording "by MANGOPAY" is no longer included in payout references shown on the end-user's bank statement
- We've completed the next stage in our performance and scalability improvements whereby you'll find that the card, card registration and bank account list responses are now much quicker and more reliable
- We've fixed a very minor bug where the naming of some payment methods was different between the reporting tool and the API
Gratipay's founder says he's going back to having a separate full-time job:
[My wife] and I just decided that I should find a full-time salaried job. I'm hopeful that with our new focus (new homepage and simpler focus on being "the easiest way for companies to pay for open source") Gratipay will be able to exist more readily as a side-project for a while. I don't know fully what this will mean yet though, so stay tuned! :-)
Mangopay Api Status - [PRODUCTION] PSP Scheduled Maintenance
• Our PSP scheduled a maintenance on their infrastructure. The service might have some troubles. • Who is concerned: Anyone on PRODUCTION environment. • Date : The 16th Octobre from 01:00 UTC to 05:00 UTC.
Traffic surge from Twitter today: https://twitter.com/timpritlove/status/912246780951191552
@Changaco That is great, he has a wide reach out to the German podcaster scene!
This is Liberapay's quarterly "what's up?" thread. Previous: #121.