Finally got the first set of code committed to rehash to allow use of IPv6 properly (dev.sn.org has had a AAAA record for ages, but IPv6 address handling has been hosed since day 1, that's why we don't publish one for production). Just need to add some UI tags so admins can see if a ipid/subid is IPv4 or IPv6, and we're more or less set here.
Our IRC (http://irc.sylnt.us/) has a #comments channel that you can join to see an hourly feed of all new comments that appear in reply to SoylentNews stories.
This has been around for a while, but over the weekend a new feature was added to allow more personalized comment feeds.
Filtered feeds can be dispatched either as a PM to your nick or to a channel of your choosing. To dispatch to a channel you just need to make sure the exec bot resides in that channel (you can command it to join by visiting #soylent and typing "~join #mychannel").
There are two types of filters; cid and pattern
The cid filter is useful if you would like a feed of all responses in a specific comment thread. You simply add a filter that points to the parent comment cid and the bot will feed all child comments that appear.
Using a pattern filter enables you to feed comments that meet certain criteria. There are a number of fields you can match, and any new comment that matches the criteria in a filter will be output to the target nick/channel.
You can add multiple filters to track multiple cid's and/or comments that match multiple patterns.
The following commands can be performed in any channel where the exec bot resides:
~comments filter-add %id% %target% %cid%
~comments filter-add %id% %target% %field% %pattern%
~comments filter-delete %id%
~comments filter-list
%id% = unique name to identify filter (cannot contain spaces)
%target% = channel or nick to send filtered comments to
%cid% = SoylentNews comment id to track ("cid" parameter in uri)
%field% = any of user, uid, score, score_num, subject, title, comment_body (title refers to the story title)
%pattern% = regexp pattern for use with preg_match (surrounding #'s are added by the script)
examples:
- if you wanted a feed for all replies to this comment: http://soylentnews.org/comments.pl?sid=6634&cid=160651
you would use this command:
~comments filter-add my_test_filter #mychannel 160651
- if you wanted a feed with any comments that contain "systemd" you could use this command:
~comments filter-add systemd_filter_1 #mychannel comment_body systemd
and if you also wanted comments with "systemd" in the subject, add another filter:
~comments filter-add systemd_filter_2 #mychannel subject systemd
--
source (unlicensed): https://github.com/crutchy-/exec-irc-bot/blob/master/scripts/comment_feed.php
Squished an annoying bug in rehash that prevented formkeys working due to changes in how mod_perl works, I dunno worse, the abuse of the MP1 API, or the hack I had to code to emulate the old behavior; here's the comment I left about it:
# UNBELIEVE HACKINESS AHEAD
#
# Ok, under MP1, it was possible to use param as a "semi-persistant" scratchpad
# that is, to save a new element in the hashref, and get it back by future calls
#
# This worked because the older APR methods allowed you to store into the HASREF.
# even though this behavior was wrong, and bad according to MP documentation. MP2
# now removed the STORE method from the APR tables so any attempt to write to them
# goes BANG.
#
# Since we can't do that now, we're going to have to fake it. On our first call to
# getCurrentForm, we'll copy the param tables to a hashref, then shove it into the
# apache2 pnotes, and then retrieve it on demand.
#
# This is a fucking hack, but I can't think of a better way than to refactor a TON of
# perl, and perl is not a language that makes it easy to refactor ...
Title says it all really but I found it surprising that there wasn't much noticeable difference. It started out foggy but the fog had mostly risen to 100% low cloud cover at local eclipse maximum (88.8%) yet if I didn't know and someone told me there was an 88.8% eclipse at that moment I wouldn't have believed them at all. The level of light felt unexceptionally normal. It was more noticeable a while after the local maximum was over as it started to get a little bit brighter but for all purposes it was just like a normal variation caused by weather, no weird shadows, not even any streetlights turning themselves on.
It was so unnoticeable I double-checked the time of the event and my clock. I guess my eyes almost entirely compensated for the small and ever so gradual change. Right now it's not even supposed to be entirely over yet but meh :)
I slept through the last eclipse so maybe this is all completely normal, the lack of difference that is; me sleeping right through “events” is very normal :D
Currently deep in working on getting the first rehash (MP2 slashcode) release put together. lithium got rebuilt and is now on the MP2 release. Since this upgrade is disruptive anyone, we decided to go full-in and put in a migration to MySQL cluster as well; which will require some code changes for Search, but otherwise was mostly a drop in upgrade.
I have a friend named Jamie. She's in her 40s, and she might go to prison for four years on the 23rd of this month.
She had a DUI from 2012, which she was guilty of, and one from 2014, which she was not. Because of her prior conviction, she's getting a much harder time by the courts. She's been offered the choice of signing for four years of prison, or taking it to trial and possibly getting 10 years if found guilty. She's a mother with two sweet, young little girls. She won't get to see them for four years. They're going to end up with her mother in Idaho.
She let a friend drive her truck, who was sober, but because she was next to the truck drinking shortly after it parked, she was hit with another DUI when the cops pulled up over a domestic disturbance, which is common here. Her friend already told that she was not the one behind the wheel, but it doesn't seem to make much difference.
Here's where it bothers me. She is innocent, and she's being given the choice of admitting to a crime she didn't commit and getting four years, or fighting it, possibly losing, and getting ten years.
This is disgusting to me.
I'm writing this, I suppose, to ask for advice. How can I help her?
Time is of the essence.
This editor thinks about things... usually does not reach a conclusion.
Every so often an important story happens, or there are no usable submissions and an editor might elect to circumvent the normal process and set their own story for release. This goes against the normal submissions process, it is not something that happens very often. Site news is the exception to this for obvious reasons.
On the occasions we have released a story as described above -- not waiting for a submission -- there has been no complaints that I am aware of.
Honestly, I do not rush to start releasing my own stories, or to make submissions. Organic and original submissions are far better and what I really want to see more of.
What are your opinions on editors finding and releasing stories this way more often? Especially when it comes to 'breaking news', but more generally also.
[This journal entry is just that, it is not an official SoylentNews RFC or endorsed by any of the staff.]
I personally had an encounter with the great FSM. I'm not writing here to convince anyone, just to have an article to cite when modding other religious believes as "incorrect", should the new incorrect-mod with mandatory citation be implemented. If it should be decided that I'm not allowed to cite myself, could I ask someone to copy this journal entry and post it again? Or do I have to create a second account myself?