Conversation
Notices
-
@steve my share level is Public or All on everything in NavierStokes, but notices show up to Followers only on pump.io. Is there an easy way to fix that?
-
You have to edit one line in the GNUSocialTools.py code. Uncomment this line:
message.public = True
Then all messages from GNUSocial will default to "public"
-
I did a hard override on publicness for GNUSocial because there is no way (from the API) to determine if a message is intended to be public or not. At least, I couldn't figure it out.
-
I appear to only have "elif self.sharelevel.find("Public") != -1 and message.public == 1:" ...I may be working from an older version though. I'll dig into it on Wednesday.
-
You might be using an older version. Nonetheless, you could add the line I suggested you change and it would have the same effect. By default, message objects harvested from social networks are not considered "public" unless tests for publicness are passed. Since those tests are not possible (as far as I can tell) on GNUSocial, I erred on the side of leaving them at the default of "non-public." But you can override that manually.
-
@steve @jrobb so, I know I'm not using an old version because I just started this install (see 9-day-old context if that doesn't make sense), but
cat GNUSocialTools.py | grep True
return True
message.reply = True if self.find_element_of_status(dent_xml,"in_reply_to_status_id") != "" else False
do_write = True
do_write = True
do_write = True
I tried adding "message.public = True" but then it wouldn't run. I don't know where to put it. I experimented with some other changes of things from False to True that seemed like it would help...but they did not.
-
If you're using v0.9.2, I'd suggest adding message.public = 1 to line 147 of GNUSocialTools.py. Did you put that line in that part of the code? I'd be curious to know where you put the line, and what the error what that prevented it from running. I'm sure we can sort this out...
-
yep, using 0.9.2. I can't remember exactly where I put the line, but the error was an improper indent. I tried to remove all the white space in that area and it still wasn't happy. I'll give line 147 a shot now.