Splicer splicer@awkwardly.social

South Schodack NY USA

I blog at https://splicer.com/ and dream of the day when my blog and everyone else's will be federated.

  • Is there life after snowflake?

    2017-09-28T17:31:14Z via Dianara To: Public CC: Followers

    This is a doozy for me. Hopefully someday I can title this How I Learned To Stop Worrying And Love The Abundance.


  • Walkaway

    2017-09-27T16:19:29Z via Dianara To: Public CC: Followers

    There's something very wrong when the idea of a post-scarcity world gives me panic attacks instead of hope.

    Claes Wallin (韋嘉誠) likes this.

  • Pretty and red

    2017-09-26T20:10:13Z via Dianara To: Public CC: Followers

    Montblanc Marilyn Monroe looks like my Omas Emotica:


    Pretty and red. Don't think I want to pay for it. And the nib really should be platinum if it's an homage to Marilyn.

  • Rockin' it old school

    2017-09-26T19:20:04Z via Awkwardly Social Web To: Public CC: Followers

    Literally. Phone charging so it can't be carried around. 11 year old music player works great. 

    Claes Wallin (韋嘉誠) likes this.

    I have an older (and probably way cheaper) player I still carry around sometimes.

    Using the phone for music is not for me =)

    JanKusanagi at 2017-09-26T20:40:12Z

    Splicer likes this.

    >> JanKusanagi:

    “Using the phone for music is not for me =)”

    I paid what seems like a lot of money to me to have a phone with enough storage that I could fit my music library on it. I justified it because having bought it without a carrier subsidy I didn't get locked into a contract. Almost US$1000 up front for the phone, but my wireless bill went from $100/month to about $12-20/month. So even with the pricey phone going no-contract paid for that phone in the first year. I've had it two and a half.

    Anyway, I almost never actually have phone calls. Basically what I call my "phone" is my music player that also has messaging, email, and other apps and which can make a phone call if I need it.

    Splicer at 2017-09-27T00:15:53Z

  • Adventures in looking over the shoulders of contractors

    2017-09-26T15:15:39Z via Dianara To: Public CC: Followers

    What kind of chucklehead reads server error logs with vi?

    McClane likes this.

  • Kirk, Spock, and McCoy were the original TV SJWs

    2017-09-25T01:13:51Z via Awkwardly Social Web To: Public CC: Followers

    Anyone who complains about Star Trek pushing a social agenda can shove a photon torpedo up their alt-starboard nacelle.


    Claes Wallin (韋嘉誠), Jason Self likes this.

    Show all 5 replies

    >> JanKusanagi:

    “They're really saying this kind of thing about Discovery, as opposed to the previous shows? xD

    One has to wonder which Star Trek did they watch before xD”

    Maybe the JJ Abrams movies.

    Splicer at 2017-09-25T01:41:54Z

    Claes Wallin (韋嘉誠) likes this.

    » Splicer:

    “Maybe the JJ Abrams movies.”

    That was my guess too =)

    JanKusanagi at 2017-09-25T01:46:58Z

    Splicer likes this.

    You mean the JJ Abrams movies that have mixed-race alien first officer, take-no-shit African communications officer, Asian navigator who is gay, Russian helmsman, incredibly brave captain of the first ship we see is Indian? Kirk's mentor is in a wheelchair at the end of the movie? I saw some diversity in at least the first one....

    Euthymia at 2017-09-25T04:10:37Z

    Splicer likes this.

    >> Euthymia:

    “I saw some diversity in at least the first one....”

    Yeah, that one. So yes, you have that diversity in the crew, although today's standards are not really the same as they were in the 60s, so having one woman with a speaking role doesn't seem quite as progressive as it might have then.

    But the plots haven't had any social commentary to speak of. There's been no "Let This Be Your Last Battlefield" (terrifying title considering the ending). All other Star Treks have had aesops about our present world at the front and center. I think your favorite is Undiscovered Country. That's all end-of-the-cold-war stuff.

    Splicer at 2017-09-25T04:18:37Z

    Euthymia likes this.

  • Pump as a comment system?

    2017-09-21T00:39:58Z via Dianara To: Public CC: Followers

    This is a half-baked idea that's been bouncing around in my mind for some time. Folks here in the pumpiverse may be able to tell me whether it's worth baking.

    My thought is to use pump as a plug-in comment system for some blogging CMS like Ghost or Wordpress, where a site admin would have to add a bit of javascript to their site and folks could reply to those posts as though they were replying to a post on someone's pump instance. This would make it a federated/free alternative to systems like Disqus

    Like I said, half-baked idea. I keep running into my own ignorance when I think about it, which means I should be learning more. I guess this would mean making the site with the CMS run its own pump node, right? Or perhaps it could piggyback on some other pump's node. Maybe automatically posting with one account and keeping track of the responses to that account.

    The next thing that occurs to me is the problem I've encountered being unable to reply to a notice that existed before I followed the poster of the notice. I can reply to anything that user posts afterward, but not the notice that called my attention to that user in the first place. Is that still a real thing? I can see how that would be a monkey wrench.

    Maybe I'm trying to shoehorn something I oughtn't into a space it won't fit. Just mean to toss it out there as to whether it's worth pursuing.

    PS of course having some kind of decentralized federated comment system would be rad. Broadly I don't have any doubt that it's a goal worth pursuing.

    PPS and also this raises the question: why not just blog with Pump? Well, slug URLs for one. Also not sure how annoying a bunch of 30-paragraph essays would be in people's activity stream. It's not a bad proposition; just something I'm not totally sure meets my use case.

    Laura Arjona, Claes Wallin (韋嘉誠) likes this.

    Claes Wallin (韋嘉誠) shared this.

    Show all 5 replies
    You are not the first to think it, but nobody has done it well yet, with OStatus or with Pump. There was a WordPress plugin for OStatus, but I think it was very rudimentary.

    Claes Wallin (韋嘉誠) at 2017-09-21T12:35:58Z

    It's definitely a thing that should fit.

    Claes Wallin (韋嘉誠) at 2017-09-21T12:36:19Z

    I think it's definitely doable, since Pump.io allows "remote login", and has a pretty good API. But of course, this would require work on the blog side.

    We can look at OpenFarmGame as an example of something that's not really a Pump client in the traditional sense, and uses your Pump.io account from your server to login to the game. And it's a web app, meaning that this fits the website usercase, not just desktop or mobile clients =)

    » Splicer:

    “[...] he problem I've encountered being unable to reply to a notice that existed before I followed the poster of the notice. [...]”

    That still happens, AFAIK, but I should point out that the problem only happens if nobody on your server followed that user yet, not you personally.

    So, if userFrom2016@datamost.com follows you, newUserSept2017@datamost.com who just registered right now, will be able to comment on most of your previous posts.

    This is obviously a much bigger problem if you're the only user on your server, of course (for the reverse case) xD

    JanKusanagi at 2017-09-21T13:17:44Z

    Claes Wallin (韋嘉誠), Splicer likes this.

    Mastodon has several mitigations for this and neighboring issues:

    • Fetches parents of posts that you read
    • Allows you to search for a post URL and tries to fetch that post if it doesn't have it
    • Goes out and fetches the latest bunch of posts from an account when you start following it

    Claes Wallin (韋嘉誠) at 2017-09-21T23:58:02Z

  • Six hours with iOS 11

    2017-09-20T01:20:05Z via Dianara To: Public CC: Followers

    New post on Monochromatic Outlook: https://splicer.com/2017/09/19/six-hours-ios-11 

    (No, those images weren't that much trouble. Not really sure they helped the post much either. Oh well.)

  • Yes, I'm complaining because I'm lazy

    2017-09-20T00:39:44Z via Dianara To: Public CC: Followers

    After writing a post and taking some screenshots, you know what I really don't want to do? Manually resize those images and upload them and manually build links and image tags.

    It's not that I don't know how. I've been doing this stuff since 1995. It's that this should have been automated in a way that actually works before.

    Yeah, I know that Wordpress and Ghost and pretty much every content management platform has made this easy and simple to automate. But my blog is on Drupal. Which means that at various times I've had some half-assed mechanisms in place. But those solutions competed with one another. Image, Image Field, Image API, Media, Imagepicker. One of those is now in Drupal Core and there still isn't any solution that makes it convenient to just put arbitrary images in a post.

    Thanks for listening. I've got some images to resize.

  • 2017-09-19T21:38:42Z via Awkwardly Social Web To: Public CC: Followers

    I just received a phone call from something which failed the Turing test.

    cedeo likes this.

  • 2017-09-12T19:21:21Z via Dianara To: Public, JanKusanagi, JanKusanagi CC: Followers

    @JanKusanagi if you were to share the post you linked to the other day https://identi.ca/balleyne/note/cVDOCTBDQSq9eb02tuhLvQ  to me, would it appear in my stream, and then (the aim of this experiment) would I be able to follow @balleyne using Dianara rather than the web interface?

    Show all 5 replies

    >> JanKusanagi:

    “[...] Just enter his address in the upper field of the Contacts tab =) [...]”

    This is odd. When I do that, Dianara gives me an error. From the log:

    [9/12/17 3:34 PM] HTTP error: Internal Server Error (500) - : http://awkwardly. ... user/splicer/feed

    Splicer at 2017-09-12T19:37:53Z

    Without any further error message?

    I suspect it might be the "upstreamDuplicates error", but without a clearer message...

    What version of Dianara is that?

    JanKusanagi at 2017-09-12T19:45:26Z

    >> JanKusanagi:
    What version of Dianara is that?”

    1.3.2. Looks like 1.3.7 is the newest. Darnit. This is the version that apt-cache policy says is current in ElementaryOS (Loki)

    ElementaryOS is based on Ubuntu, and 1.3.2 is the version on my 16.04.3 install. My Debian (Stretch) install reports 1.3.6 as current, which is better, but it's a headless server. Maybe it's time for me to install a plain Debian desktop VM. Or sigh build from source.

    Splicer at 2017-09-12T20:02:33Z

    Ah, that ancient version explains why it's having trouble reading the error message. Pump.io 4.0 changed a few things on how error messages are reported.

    Supporting that is actually one of the improvements in the changelog for 1.4.0, so 1.3.7 wouldn't help with this.

    You could try running from a command line with the --debug parameter (besides whatever parameters you already use, like --nohttps of course). The error could probably be read in the console output.

    JanKusanagi at 2017-09-12T20:07:12Z

  • Unable to log in to identi.ca or mipump.es

    2017-09-12T18:39:29Z via Dianara To: Public CC: Followers

    I'm presently unable to log in to identi.ca or mipump.es as splicer@awkwardly.social in order to follow others on those pump instances.

    Firefox tells me: "The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."

    Safari says the address that isn't responding is /authorized/awkwardly.social?oauth_token=[redacted]&oauth_verifier=[redacted] on either server.

    That looks like a problem on their end, and I am able to log in to some other pumps. Not certain what to make of it, though.

    Related meandering thought: Maybe I should get a new SSL cert and see what happens if I switch my main URL to https. I've been taking it for granted that it isn't gonna work.

    Might be related to the fact that those are still on 3.x.

    JanKusanagi at 2017-09-12T19:01:24Z

    >> JanKusanagi:

    “Might be related to the fact that those are still on 3.x.”

    Ah, that makes sense. Thanks.

    Splicer at 2017-09-12T19:09:14Z

    » Splicer:

    “[...] Maybe I should get a new SSL cert and see what happens if I switch my main URL to https. I've been taking it for granted that it isn't gonna work. [...]”

    @AJ Jordan suggests not doing that at this point =)

    JanKusanagi at 2017-09-12T20:01:03Z

    Splicer, Claes Wallin (韋嘉誠) likes this.

  • If commenting doesn't work

    2017-09-11T18:36:21Z via Dianara To: Public CC: Followers

    https://splicer.com/contact me if there's something that seems to be broken after the nginx addition and you don't have my email address. (Hopefully some of this still works)

    Test comment...

    EDIT: seems fine =)

    JanKusanagi at 2017-09-12T00:07:55Z

    Splicer likes this.

  • Awkwardly now with added nginx

    2017-09-11T17:58:24Z via Dianara To: Public CC: Followers

    At least for the moment, I've got awkwardly.social now sitting behind an nginx proxy. I know I don't need it for pump.io; I've been running Awkwardly without a proxy for as long as Awkwardly has been up. I used JRobb's config as a starting point to make sure that WebSocket proxying would work happily. That link seems to be down, so here's the Wayback archive: https://web.archive.org/web/20160722040135/http://jrobb.org/moving-my-pump-home.html 

    This frees me to move other things onto the same Linode and save a few bucks by consolidating my various installations. It doesn't seem to be affecting the site's responsiveness or functions. My load average is reported as a consistent 0.00 and I still have three-quarters of the memory on this Linode free. So far, I don't see any downside.

    One small detail: your server is now replying with "nginx/x.y.z" as the Server header instead of the one from pump.io.

    You can fix it with the "proxy pass_header Server;" parameter, like in this example by @sazius:


    JanKusanagi at 2017-09-12T23:25:38Z

    >> JanKusanagi:

    “One small detail: your server is now replying with "nginx/x.y.z" as the Server header instead of the one from pump.io.

    I'd noticed that the nginx header was in there but I hadn't thought of it as a problem. I added the directive as suggested and I don't see any mention of nginx any longer.

    Splicer at 2017-09-16T19:38:50Z

    Yep, now the Server: header states:

    pump.io/4.0.0 express/4.15.2 node.js/v4.8.4


    JanKusanagi at 2017-09-16T22:57:30Z

  • Drupal, maybe we should just be friends

    2017-09-11T17:36:55Z via Dianara To: Public CC: Followers

    New post on Monochromatic Outlook about my struggles and thoughts about continuing to use Drupal for my personal blog.


  • 2017-09-08T01:22:24Z via Awkwardly Social Web To: Public CC: Followers

    Every one of my attempts to convert Drupal 7 sites to Drupal 8 has been a nightmare followed by defeat. I feel thoroughly worn down.

    Just the other day @Blaise Alleyne was talking his the good results migrating from Drupal to Backdrop.

    You might want to check that out =)

    JanKusanagi at 2017-09-08T01:38:58Z

    Splicer, Claes Wallin (韋嘉誠) likes this.

    >> JanKusanagi:
    You might want to check that out =)”

    Thanks. It looks very interesting. It may be useful as I split the site into multiple installations with individual configuarations, if that's what I end up doing.

    Splicer at 2017-09-11T17:33:17Z

  • 2017-09-01T02:52:25Z via Awkwardly Social Web To: Public CC: Followers

    I'm compiling GnuPG from source on this Beaglebone Black running FreeBSD.

    Because freedom.
  • 2017-08-29T21:29:07Z via Awkwardly Social Web To: Public CC: Followers, JanKusanagi, Evan Prodromou

    Trying to migrate my pump instance to another server. Starting to think that the answer is: don't do that. :-)

    The server that I want to put it on is already running other sites. That means I will have to run this one behind nginx. https://github.com/pump-io/pump.io says that's discouraged and things won't work very well. http://pumpio.readthedocs.io/en/latest/sysadmins-debian.html on the other hand seems to recommend it. My test instance is on :8080 so I've just kicked this question down the road.

    The test instance seems to come up OK until I try to log in or visit a user's stream. Then it pegs my CPU at 100% (85% node and 15% mongo) until mongo crashes.

    All this makes me think that if I want to save a little money each month on fewer servers that what I really need to do is move everything else from other servers to the one awkwardly currently runs on and shut down those others.

    Ultimately, as sad as this is, if I can never have the awkwardly.social domain on https without breaking federation, I should probably just delete it and start over with another domain name. Believe me, I'm kicking myself hard for not reading the instructions more closely when I first set it up and tested it. I bought a certificate before I even installed pump but unfortunately tested it (including following people on remote servers) on http, poisoning my instance for all time.


    Claes Wallin (韋嘉誠) shared this.

    » Splicer:

    “[...] un this one behind nginx. https://github.com/pump-io/pump.io says that's discouraged and things won't work very well. http://pumpio.readthedocs.io/en/latest/sysadmins-debian.html on the other hand seems to recommend it. [...]”

    From the little I know about this, it's not as much that it's discouraged, as it is that it's "not needed", since Pump.io is its own webserver.

    AFAIK, the main problem with using (at least certain) proxys is that the Websockets goodness breaks. That mainly means the realtime auto-updating of the timeline, on the web interface.

    Other than that, I know of several people running Pump behind Nginx who seem to be quite happy with their setup.

    But certainly @AJ Jordan is the man to ask ;)

    He might also have some answers regarding your non-https dilemma. I imagine that if there's no fix for that, maybe that could be different when Pump.io moves to ActivityPub-land. Just a thought.

    JanKusanagi at 2017-08-29T21:59:42Z

    Claes Wallin (韋嘉誠), Splicer likes this.

    Sure, I understand that it's unnecessary so long as it's running on its own server. Basically right now I'm paying twice as much as I have to for two linodes, each of which using less than 1% of the resources they are permitted. It would be nice to pay for just one.

    Probably a better idea is to just look for a job so the small amount of money doesn't matter. :-)

    I've been meaning to research nginx's websockets handling. It's probably about time.

    Splicer at 2017-08-30T00:09:54Z

    Claes Wallin (韋嘉誠) likes this.

  • 2017-05-17T16:21:52Z via Awkwardly Social Web To: Public CC: Followers, bill

    It's been a few days now with Mastodon. Maybe it would be different if I had a multiple people I was following, but I don't care for the four-column format.

    I like being able to compose a toot at any time, but that seems like it doesn't require a quarter of the screen space at all times. And "home" and "notifications" seems kinda redundant.

    If I were to use it, it'd certainly be via a desktop client, assuming there are any available for GNU.

    No web interfaces for me, thanks.

    JanKusanagi at 2017-05-17T19:24:14Z

  • Relief

    2017-05-16T03:49:38Z via Dianara To: Public CC: Followers

    I think that Roxie might just be eating the food with her medicine in it! Hopefully I won't have to spend all night watching Iron Fist and waiting for her to get so hungry that she gets her meds.

    Stephen Sekula likes this.