@der_Jeff Changes haven't affected users' current charges. Pnut has a minimum that users can pay above, so reductions don't automatically reduce what someone is paying. When first introduced, though, some users started lower than the current minimum. 👍
Thanks everyone for working in the #hackathon! It sounds like @thrrgilag got some interesting work with gitlab+pnut integration, @kwood worked on a Ruby Pnut library, and there was some twiddling with Pnut scripts and the API. 👊
@33MHz became aware of the event and contacted colocation support to coordinate repairs. There apparently was a failure, but rebooting and fsck passed all tests. No SMART issues recorded. We will plan a better time for maintenance and for upgrades.
Join us May 5th for a day of hacking, slashing, and generally #winning. If you have an idea or something to punch around, speak up! Chat room [patter.chat]
The latest #pnut API update is live! Take a look at the changes [pnut.io]. This is a handful of small adjustments and improvements. The documentation now provides live calls, and is effectively its own client.
Today we've released version 0.7.5 of the #pnut API! With this update, we would love for any contributions of translations of the pnut.io account area. Contact us if you'd like to help!
Today version 0.7.4 has been released into the wild. Take a look! [pnut.io] Audio files, basic reporting, more scope options, a lot of small improvements, and restructuring.