SoylentNews

<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>

For a few months now, aqu4bot's Windows support has been broken. Compilation would fail because nonblocking sockets were not properly doable in Windows the way it was intended. I was using the same network core I use on the IRC protocol to download HTTP.

It worked, except when it hung. This affected mainly the $title command. So I added the nonblocking, which was necessary, but this broke all Windows support. I was reluctant in using libcurl because although I love libcurl, I only had two commands for aqu4 that used HTTP. That was $ddg and $title.

The good news is libcurl is VERY portable and works well under Windows. So needless to say aqu4bot's Net_GetHTTP() function was removed in favor of a new CurlCore_GetHTTP().

There is now a hard dependency on libcurl, but that's fine I suppose, since I now have my precious and arguably useless Windows support once more.
To celebrate, I created a new icon for aqu4bot that is used as the icon for the Windows executable: http://universe2.us/collector/aqu4bot.png

There's still a small issue with $time, as Windows does not have zoneinfo so I can't set the timezone properly, but everything else appears to work!

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

Over the weekend, there's been a slew of images released showing celebrities in varying states of undress. Now, it appears that a flaw in iCloud could be responsible for the images making their way online.

On Monday, a Python script emerged on Github (which we’re not linking to as there is evidence a fix by Apple is not fully rolled out) that appears to have allowed malicious users to ‘brute force’ a target account’s password on Apple’s iCloud, thanks to a vulnerability in the Find my iPhone service. Brute force attacks are where a malicious user uses a script to repeatedly guess passwords to attempt to discover the correct one.

http://thenextweb.com/apple/2014/09/01/this-could-be-the-apple-icloud-flaw-that-led-to-celebrity-photos-being-leaked/

http://www.independent.co.uk/life-style/gadgets-and-tech/is-apples-icloud-safe-after-leak-of-jennifer-lawrence-and-other-celebrities-nude-photos-9703142.html

What impact does the proliferation of new mobile technologies have? How does the sharing of personal data over the Internet threaten our society? Interview with Professor Jean-Pierre Hubaux, a specialist in communication networks and privacy protection, a major field of IT security.
Jean-Pierre Hubaux as a professor at the EPFL's School of Computer and Communication Sciences. During the last decade, Jean-Pierre Hubaux and his team at the Laboratory for Computer Communications and Applications have focused their research efforts on privacy protection, in particular for mobile communication networks (and notably geolocation) and personal data (with genomic data as an application example).
http://actu.epfl.ch/news/protecting-privacy-also-means-preserving-democra-2/

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?

I got news.. That nefarious organization known as NSA is gone! or perhaps there is room for improvement in the search function. Because I have a very distinct memory that there has been a lot of writing on that subject .. ;-)

It's a bit surprising that submitters and editors don't change all links in the submissions from http to https for those sites that support security. Considering that it's fully known that all internet communications is logged by various governments and shady organizations. This perhaps is especially true for readers in less than democratic nations. But the most obvious is the chain of eyes that any person that keeps them selfs informed know about. This information can be used against yourself or your friends at any time in the future. The people that spends big money into that storage operation wants something for their effort.

So make all links https that you can!

~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.