sudo-sys

sudo-sys@sudoroom.org

3 participants
902 discussions

Fwd: [mesh-talk] [#2110] Re: Gratipocalypse

by max b

I know there's been a lot of talk about sudo having its own integrated payments processing system, but I figure we want to talk to this fellow anyhow? Has anyone already gotten in contact? ---------- Forwarded message ---------- From: max b <maxb.personal(a)gmail.com> Date: Wed, May 13, 2015 at 5:04 PM Subject: Re: [mesh-talk] [#2110] Re: Gratipocalypse To: Gratipay Support <support(a)gratipay.com> Cc: Mo Balaa <buddybalaa(a)gmail.com>, mesh-talk <mesh-talk(a)lists.sudoroom.org > Hi Chad, Sorry no one got back to you sooner. This mailing list is actually pretty much exclusively for sudomesh, NOT sudoroom. I feel reasonably comfortable speaking on behalf of sudomesh, but in order to get in touch with someone who can help you with sudoroom, I would send this question to the following emails: sudo-sys(a)lists.sudoroom.org, mattsenate(a)gmail.com, marc(a)juul.io, tunabananas(a)gmail.com, yardenack(a)gmail.com (I'm sure I'm leaving someone out, but I think one of these folks can help) As for sudomesh, I believe we're interested in making the migration. I know someone is working on writing their own stripe implementation, but depending on the new requirements, I think we would be interested in doing the migration at least until we can get our own platform up and running. What are our next steps? Thanks! Max On Wed, May 13, 2015 at 4:50 PM, Gratipay Support <support(a)gratipay.com> wrote: > Greetings, > > We're trying really hard to get back on track tomorrow > <https://github.com/gratipay/gratipay.com/issues/3399>. However, Sudo > Room/Mesh will need to take action to migrate to the new Teams feature > we're developing in order to receive payments in the future. I'd love to > help make sure you start receiving payments again tomorrow. Are you > interested? > > > chad > ---- > Chad Whitacre, Founder, Gratipay <https://gratipay.com/> > Twitter <https://twitter.com/Gratipay> / Facebook > <https://www.facebook.com/Gratipay> / Google+ > <https://plus.google.com/+Gratipay> > > On Fri, 8 May at 2:57 PM , Gratipay Support <support(a)gratipay.com> wrote: > Were you able to read the blog post linked from the email? > > https://medium.com/gratipay-blog/gratipocalypse-42fd0ec0d9e8 > > Happy to try to answer more specific questions. > > I'm really sorry for the disappointment. :-( > > I consider Sudoroom/sudomesh to be a model Gratipay user and I know you've > been depending on us. We're going to be making some big changes quickly in > order to get back on track. Our goal is to begin process payments for > sudoroom/sudomesh again next week, but it's going to take some input on > your part because we're going to be implementing a new separate terms of > service for receivers that we'll need you to opt in to before we can get > back on track. Would you be a good person to schedule a call with to let > you know what we're looking at over here? > > > chad > ---- > Chad Whitacre, Founder, Gratipay <https://gratipay.com/> > Twitter <https://twitter.com/Gratipay> / Facebook > <https://www.facebook.com/Gratipay> / Google+ > <https://plus.google.com/+Gratipay> > > On Fri, 8 May at 2:34 PM , Buddybalaa <buddybalaa(a)gmail.com> wrote: > any ideas what this is about? > > On Thursday, May 7, 2015, Gratipay Support <support(a)gratipay.com> wrote: > >> [image: Gratipay] >> We have an unfortunate announcement to make: after 152 weeks of >> continuous operation, we are for the first time today skipping >> Gratipay's weekly payment cycle >> <https://medium.com/gratipay-blog/gratipocalypse-42fd0ec0d9e8>. We are >> deeply sorry. :-( >> Something not right? Reply to this email for help. >> Sent by Gratipay, LLC <https://gratipay.com/> | 716 Park Road, >> Ambridge, PA, 15003, USA >> > 2110 > > _______________________________________________ > mesh-talk mailing list > mesh-talk(a)lists.sudoroom.org > https://lists.sudoroom.org/listinfo/mesh-talk > >

10 years, 10 months

Re: [sudo-sys] Bounce action notification

by yar

On Mon, Apr 27, 2015 at 5:46 PM, yar <yardenack(a)gmail.com> wrote: > I think I fixed the spam problem but we are still getting lots of > deferred deliveries because of this. It may be an issue for a while, > possibly even until we migrate the server. Deferrals are still happening. Mailman is seeing the bounces and starting to suspend gmail addresses. I had to confirm to stay subscribed to Info. Is anyone else getting these? Is it happening for other lists or just Info? I'm going to try to start migration ASAP.

10 years, 10 months

Automated last BART announcements in sudo

by Marc Juul

sudo room now automatically announces last BART departures. It should announce last departures from MacArthur station for each of the BART directions, SF, Richmond, Pittsburg and Fremont. It will announce each last departure twice in the window 30 minutes to 10 minutes before departure. Here's how it works: I hooked up a usb audio adapter and some speakers to the sudo server, wrote a little script that talks to the BART API and set it up to run as a cronjob that speaks the results using espeak. The code is here: https://github.com/Juul/lastbart It's all new and fragile so you probably shouldn't rely on it just yet. -- marc/juul

10 years, 10 months

Re: [sudo-sys] Bounce action notification

by yar

On Sun, Apr 26, 2015 at 2:37 PM, yar <yardenack(a)gmail.com> wrote: > Gmail seems to be rate-limiting our IP because we keep reflecting > info(a)sudoroom.org spam. Incredibly, our postfix config lacked even > basic spam protections. I've added a bunch of > smtpd_recipient_restrictions which will hopefully help until we > finally migrate to digitalocean. I think I fixed the spam problem but we are still getting lots of deferred deliveries because of this. It may be an issue for a while, possibly even until we migrate the server.

10 years, 10 months

Fwd: Bounce action notification

by yar

Gmail seems to be rate-limiting our IP because we keep reflecting info(a)sudoroom.org spam. Incredibly, our postfix config lacked even basic spam protections. I've added a bunch of smtpd_recipient_restrictions which will hopefully help until we finally migrate to digitalocean. ---------- Forwarded message ---------- From: <mailman(a)lists.sudoroom.org> Date: Sun, Apr 26, 2015 at 12:59 PM Subject: Bounce action notification To: info-owner(a)lists.sudoroom.org This is a Mailman mailing list bounce action notice: List: Info Member: juul(a)labitat.dk Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.sudoroom.org. ---------- Forwarded message ---------- From: Mail Delivery System <MAILER-DAEMON(a)labitat.dk> To: info-bounces(a)lists.sudoroom.org Cc: Date: Sun, 26 Apr 2015 21:46:39 +0200 (CEST) Subject: Undelivered Mail Returned to Sender This is the mail system at host labitat.dk. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <marcjc(a)gmail.com> (expanded from <juul(a)labitat.dk>): host alt1.gmail-smtp-in.l.google.com[74.125.203.27] said: 421-4.7.0 [185.38.172.72 15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0 http://www.google.com/mail/help/bulk_mail.html to review our Bulk 421 4.7.0 Email Senders Guidelines. bz10si7534492pad.171 - gsmtp (in reply to end of DATA command) Final-Recipient: rfc822; marcjc(a)gmail.com Original-Recipient: rfc822;juul(a)labitat.dk Action: failed Status: 4.7.0 Remote-MTA: dns; alt1.gmail-smtp-in.l.google.com Diagnostic-Code: smtp; 421-4.7.0 [185.38.172.72 15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0 http://www.google.com/mail/help/bulk_mail.html to review our Bulk 421 4.7.0 Email Senders Guidelines. bz10si7534492pad.171 - gsmtp ---------- Forwarded message ---------- From: Ila Marcus <Weeks_Darrela1(a)comerciallabor.com> To: Info <info(a)sudoroom.org> Cc: Date: Wed, 22 Apr 2015 02:26:42 +0600 Subject: [sudo-info] The erection you seek exists in the form of a pill ----38100116211850180 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit These amazing medicines will bring you back to life Your girlfriend will want nothing but your rock hard erection We are the biggest shop in the net! Get FREE tablets for every our customer! http://zzb.bz/xwrDp Experience true sexual Potential ----38100116211850180-- _______________________________________________ Info mailing list Info(a)lists.sudoroom.org https://lists.sudoroom.org/listinfo/info

10 years, 10 months

$150 charge for not returning DSL equipment to sonic.net

by Maximilian Klein

FYI, sonic.net (our original ISP at sudo and the omni) charged our card $150 because we did not send back the modem, which I wrote to the list about one month ago. C'est la vie. From: Sonic.net Billing <billing(a)sonic.net> Date: Thu, Apr 16, 2015 at 2:01 AM Subject: Sonic.net Invoice #7734422 <ooc(a)sonic.net> 4799 SHATTUCK AVE OAKLAND, CA 94609-2032 _______________________________________________________________________ Description Unit Price Total ----------------------------------------------------------------------- Charge overdue RMA for SRA06DD04 149.00 149.00 Total: 149.00

10 years, 11 months

Re: [sudo-sys] Gratipay Payout and Internet Archive Federal Credit Union deposit issue

by yar

On Thu, Apr 2, 2015 at 4:24 PM, Matthew Senate <mattsenate(a)gmail.com> wrote: > We had some issues getting Gratipay (our donation service provider at > https://gratipay.com/sudoroom) to work with their payment processing > Balanced Payments to make successful payouts (transactions) to our bank > account with IAFCU, the Internet Archive Federal Credit Union, aka the > Internet Credit Union. > > Now, the issues should be resolved. I am waiting to see the credit appear in > our IAFCU account records, but I got confirmation that Gratipay successfully > transacted the payout today via Balanced Payments. Wow. THANK YOU SO MUCH for fixing this.

10 years, 11 months

Gratipay Payout and Internet Archive Federal Credit Union deposit issue

by Matthew Senate

Hey all, We had some issues getting Gratipay (our donation service provider at https://gratipay.com/sudoroom) to work with their payment processing Balanced Payments to make successful payouts (transactions) to our bank account with IAFCU, the Internet Archive Federal Credit Union, aka the Internet Credit Union. Now, the issues should be resolved. I am waiting to see the credit appear in our IAFCU account records, but I got confirmation that Gratipay successfully transacted the payout today via Balanced Payments. These were the primary issues, which took substantial digging to figure out: 1. There seem to be some federal regulations that required our credit union to explicitly post payments to either our savings or our checking account, without ambiguity. This is done by adding a suffix to our account number for any given transaction, i.e. add "000" to correspond to our savings account. 2. However, also, when this suffix is appended to our account number, there must also be a matching value that corresponds to "savings" or "checking" called a "TRANS code". Unfortunately, gratipay did not expose this value option in their interface, despite it being supported by Balanced Payments's API. We should now have the correct suffix and the correct TRANS code that matches to deposit gratipay payouts to our savings account at IAFCU. Whew. // Matt

10 years, 11 months

Re: [sudo-sys] migrating BAPS wordpress to omni server

by yar

On Thu, Mar 19, 2015 at 2:50 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote: > I believe the Wordpress was being maintained by Joe Maloney (probably a misspell there), and that the server was set up by DK. Do you mean Joe Matheny? I'll email him and DK seperately.

10 years, 11 months

migrating BAPS wordpress to omni server

by yar

We're preparing to migrate the sudoroom.org server sometime soon. The BAPS wordpress is also sharing that server. It might be easiest - and maybe even more appropriate - to move BAPS to the omni server ahead of time and have it live there from now on? I'd also like to get them an https cert while we're at it. Who manages the BAPS wordpress? Who's the best person to contact and coordinate with? I'm happy to do all the legwork and logistics and will only need help to reset their DNS at the right time. That and permission or blessings from all people effected by it would be nice. Thoughts? :)

10 years, 11 months

← Newer
1
...
70
71
72
73
74
75
76
...
91
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys