Conversation
Notices
-
@steve any immediate thoughts on "The list of messages to write (targets and message objects):
{}"? That's what I got when I used -d on NavierStokes. I'm not sure if this is to the point to use http://polari.us/dokuwiki/doku.php?id=bugtracker yet. I assume #pebkac on my end at this point.
-
OK, I've had some time to consider these questions. The "list of messages to post" will be empty if your attempt to harvest messages from a social network failed, or if there are no fresh unshared posts from within the last hour. What network(s) are you trying to share between?
-
@steve that's really interesting. I am no longer getting that error, even as root. I get no output as root. I suspect it has to do with permissions. At the moment, this doesn't matter. Assuming I can get the eventual cronjob to work under a normal user account, I'll do that instead of root. As for the networks, I'm trying to do GNU Social, Pump.io, and Diaspora. I get notices from Diaspora. but they don't seem to go anywhere. I'm not sure I'm properly authenticated to pump.io. GNU Social appears to be throwing an error. I didn't set up any logic for what goes where. I haven't really looked at the code yet, but how does it avoid creating a loop? Does it just do text matching? Thanks!
-
As for how it avoids reposting, this is explained on the wiki:
"It employs “fuzzy text matching”, as well as a record of posts that have already been shared between networks, to try to prevent a post from being shared more than once to other networks (or back to the originating network). Fuzzy text matching is needed because different social networks encode or format the same information slightly differently. For instance, a post in HTML on Pump.io will not be formatted in HTML on Twitter, and Twitter will shorten links, thus altering the text of the original post. Fuzzy text matching uses statistical methods to attempt to compute the probability that the message has already been shared on a network. Above a match threshold, the post will not be shared.
NavierStokes considers only posts made in the last hour when it scans the streams from different social networks. It won't re-post something that is 6 hours or 6 days old."
http://polari.us/dokuwiki/doku.php?id=navierstokes
-
I am not sure why running as root makes a specific difference, unless root is (somehow) unable to find things like cliaspora. I would recommend picking 2 networks and starting small to see if you can get it to work between just those 2.
GNU Social is accessed via curl, so that should be the easiest one to debug. I have a suspicion about what is happening there. Let me look. I will get back to you shortly.
-
Yeah, I spotted the bug. I hard-coded the use of "https" into the curl call. However, your GNU Social instance _doesn't_ use SSL. I will find a way to allow either. Thanks for spotting this bug. For now, you can edit GNUSocialTools.py and change https to http in the curl calls. See if that fixes the problem with GNU Social access.
-
@steve do I need to do .py and .pyc or just .py? I haven't checked edited just yet. I will here in a minute.
-
@steve @daw just the .py (the pyc is the "compiled" file)