SoylentNews is people
SoylentNews
Bitcoin payments
<OfficialDevHat>
So, I'd given an estimate of "by this weekend" for crypto-currency payment processing. I was pretty close for not even having looked at it or picked a payment processor yet. It's looking like I'll finish Monday unless I find another 3-4 hours of coding in my brain today. I can't really speak to when it will deployed to prod afterwards.
The skinny of it is I went through two other payment processors before settling on Bitpay. It would have been nice to accept litecoin and dodgecoin as well as bitcoin but some payment processor who shall remain nameless had a dev environment that did not mirror their prod environment and all the documentation for the API was for their dev environment, so I killed with fire all nine or ten hours of coding I'd done to process payments with them and went back to looking for another processor. Maybe one of these days they'll update and bring some sanity to their system and you lot will be able to use litecoin and dodgecoin here. Until then, bitcoin payments via Bitpay are currently working from my dev environment but in need of some finishing touches and testing before being deployed for you lot to use.
</OfficialDevHat>
<PrivateCitizenHat>
A quick word about Bitpay. If you ever want to receive USD when being sent BTC, I personally highly recommend using them. Aside from test.bitpay.com not being mentioned in the docs at the time, they were bloody brilliant to code against. As a random code monkey on the Internet, they have my resounding personal endorsement.
</PrivateCitizenHat>
irc comment feed
if you're chatting away on soylent irc (irc.sylnt.us) check out #comments for a SoylentNews comment feed
the feed is based on the last 50 articles in the atom feed, and is updated every half hour
also highlights score 5 comments
examples:
<exec> *** new comment: Anonymous Coward (Score:0) "Microsoft Defies US Court Order, Will Not Give-up Emails" - http://soylentnews.org/comments.pl?sid=3678&cid=88065 (parent: http://soylentnews.org/comments.pl?sid=3678&cid=87969)
<exec> *** score 5 comment: Anonymous Coward for article "Microsoft Defies US Court Order, Will Not Give-up Emails" - http://soylentnews.org/comments.pl?sid=3678&cid=87971
proposed features include opt-in personalized feeds (to pm) with score threshold and other settings
suggestions/criticism/feedback/etc is always welcome
--
https://github.com/crutchy-/exec-irc-bot/blob/master/scripts/comment_feed.php
On Mod-Bombing
So, mod-bombing is becoming a problem. Where mod-bombing is defined as blowing a bunch of moderator points on one person's comments in pursuit of a personal vendetta. I think we're pretty much all in agreement that this type of behavior is NOT what the moderation system was designed to do and can't be allowed to continue.
So, I, personally, not anyone else on staff or the site as a whole, would like some input to use to further refine or outright change my opinion on how to deal with the matter. Bear in mind that I am not the person who gets to decide this, just the guy who would likely be coding it up.
At the moment my favorite idea is that after N downmods from person A to comments made by person B, person A be presented with a page offering them the choice of removing all their moderations from this set of modpoints or to continue on with the knowledge that an admin WILL be checking their moderations for today with the possible consequences of reversal of their moderations and their ineligibility to receive mod points again for a number of days ranging from 1 through infinity.
What say you, SN?
exec update
~help <alias>
gets first 3 lines from section of this wiki page: http://wiki.soylentnews.org/wiki/IRC:exec_aliases
followed by a url
~staff meeting
outputs paragraph in site news slashbox containing the word "meeting", with paras delimited by <br>
scripts can call lib.php function bot_ignore_next() to set a flag in the bot that tells it to ignore the next message, which is useful if outputting aliases that you don't want to be processed (such as for ~help)
~count <nick>
counts number of privmsgs in channel. also indicates over how many days and average of privmsgs per day.
rtl test
This text should be RTL if overrides are not stripped out.
exec update
some recent goings on with the exec bot that generally lurks in #Soylent channel on irc.sylnt.us:
- sed supports regex through use of preg_replace (FoobarBazbot's awk script no longer running under exec)
- reserved alias for logging script
- disabled ping script for auto-restart cos it was a disaster (i think i fixed the problem by disabling the ping until connection is established but not going to bother testing for now)
- implemented support for bucket_append messages, which allows creating lists from multiple concurrent processes without fouling each other (needed for users.php which builds lists of channels, nicks and nickserv accounts using list, who and whois irc commands)
- refined the weather script a little as a result of some feedback (thanks to those involved)
- put weather and time functions into lib files to make them accessible from a new welcome script that can (if enabled) show weather and local time on joining a channel (if your nick/location is registered using ~weather-add or ~time-add)
- created switches.php in an attempt to make enabling/disabling features on a per channel basis a little more uniform (used by sed and welcome scripts)
- script created to add suggestions to the wiki, using ~suggest (appends to a section of an article, with bullet formatting)
- added stats aliases ~first, ~last, ~find-first, ~find-last and ~count that make use of cached chat logs
- added interface for adding/editing/deleting ~define sources
- added ~killall admin command to terminate all scripts/programs running under the bot process
- admin setting to ignore/unignore nicks added
- added script start timestamp template for the exec.txt file
hoping to eventually get the nickserv account checking stuff in users.php to a point where i can use it to fix up the player authentication in irciv cos i really wanna get back into that
haf fun :D
===
https://github.com/crutchy-/test
http://wiki.soylentnews.org/wiki/IRC:exec
utf-8 regression testing
cf: http://dev.soylentnews.org/comments.pl?sid=1115&cid=27307
See: http://www.w3.org/2004/04/uri-rel-test.html
All of the following were entered using <a href="...">>...</a>
Test 101: http://www.w%33.org/
Should be: http://www.w3.org/
Test 111: http://r%c3%a4ksm%c3%b6rg%c3%a5s.josefsson.org/
Should be: http://räksmörgås.josefsson.org/
Test 112: http://%e7%b4%8d%e8%b1%86.w3.mag.keio.ac.jp/
Should be: http://�豆.w3.mag.keio.ac.jp/
Lameness filter encountered.
Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi porta tempus nunc, vel gravida eros. Fusce ac sapien sed elit adipiscing pharetra at vel neque. Cras consequat a nisi vitae interdum. Nulla pulvinar, nisi a varius venenatis, lorem mauris posuere nulla, sit amet venenatis enim mauris quis tellus. Fusce nec ullamcorper lorem. Proin vulputate leo sapien, sollicitudin tincidunt urna eleifend vel. Etiam eleifend nulla id leo egestas interdum. Sed dignissim mauris eget tincidunt fermentum. Sed nec felis et nisl ullamcorper gravida varius in augue. Morbi ac erat quis dolor ultricies pulvinar. Vivamus sagittis viverra leo et sollicitudin. Maecenas at vulputate tortor. Donec ipsum erat, bibendum vel viverra eu, ornare vel sem.
exec / SedBot2
exec now supports a reserved <startup> alias, which at the moment executes a script that triggers a sequence of aliases related to starting SedBot(2) in #Soylent and ##.
the <startup> trigger fires when the bot attempts to identify with nickserv, and like other reserved aliases can't be triggered from irc.
my intention is to make scripts to enable easy management of the current sedbot.awk script, unless FoobarBazbot returns beforehand in which case he'll be able to take the reigns.
the advantage of the <startup> alias is that if exec is disconnected temporarily, sedbot will restart when a connection is re-established.
a test was performed by pulling the network cable out of the machine hosting exec and leaving it unplugged for a while. when the cord was eventually plugged back in, exec came back up and restarted sedbot without any intervention.
https://github.com/crutchy-/test/blob/master/irc.php
https://github.com/crutchy-/test/blob/master/irc_lib.php
exec (irc bot) update
bot admins now have a little more control over scripts that are executed
to see a listing of running scripts/processes:
~ps
this will generate a list in the format:
[$pid] $shellcmd
to kill a process listed by ~ps:
~kill $pid
if the bot is restarted (~restart) or quits (~q), all processes (including any children) will be killed
bot source code is here: https://github.com/crutchy-/test
Bug #59 tests
This is fodder for testing https://github.com/SoylentNews/slashcode/issues/59.
Nested "blockquote" and "q" elements:
test1: zero
one two three
four five six
seven eight
nine.
Nested "blockquote" and "em" elements:
test2: zero
one two three
four five six
seven eight
nine.
