Twitter API plugin required for feed2red.pl

  
@!Feed2Red+

Just a quick heads up for those still using feed2red.pl: If you are on dev, and in the future on master, too, you need to install the Twitter API plugin for feed2red.pl to continue working.

It would surely be possible to switch to current Hubzilla API calls, but as the script isn't really required anymore in most cases, I don't think it's really worth the effort, given that installing the plugin is enough to keep it working.
  
Thanks @zottel for the heads up. Yes I'm still using it on a few forum channels. Still better to automate than other methods.
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sat, 13 Aug 2016 01:36:17 +0200

more red -> hubzilla

more red -> hubzilla
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sat, 13 Aug 2016 01:31:34 +0200

even more red -> hubzilla

even more red -> hubzilla
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sat, 13 Aug 2016 01:19:06 +0200

more red -> hubzilla

more red -> hubzilla
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sat, 13 Aug 2016 01:15:34 +0200

Red -> Hubzilla

Red -> Hubzilla
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Tue, 21 Jul 2015 14:46:06 +0200

make UseContentHash work with special characters

make UseContentHash work with special characters
  
@Feed2Red+

I just pushed a fix to the Feed2Red git repository that should fix relative links in feeds.

Please test that—it worked in the one feed I had that used relative links, but I'm not 100% sure that I got the regular expressions right. Also, I don't have any feeds with realtive links in images.

In some circumstances, it produces a double slash in the URL, like http://example.com//link/to/article/ . This was no problem in some tests I made, but I'm not sure if there are web servers out there that might not like this. It's fixable, but only in ugly ways, so if it doesn't matter, I'd rather keep it like it is. :-)

While testing, I saw that one of my feeds shows a relative link as its own address (the link the should lead to the blog, e.g.). :facepalm We can't fix that. We need the information about the actual server where the blog resides, because the feed might be hosted somewhere else (feedburner, e.g.). If we don't have that information, we can't fix relative links. The site I'm talking about doesn't use relative links anywhere else, so no problem here, but I wanted to tell you in case you run into such a situation.

If you find a feed where it doesn't work, please give me the feed address so that I can test with that feed myself and see what's going wrong.

If you don't have any problems with relative links, maybe wait a bit before you update. It could be that the regular expressions break something I wasn't thinking of.
  
Thanks a lot Zottel. I will test it later this day.
 
No problems so far. But have to wait for a week or more for some rogue feed item.
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Fri, 03 Jul 2015 12:18:41 +0200

fix relative links

fix relative links
  
No time to test it yet, but I will.
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sun, 14 Jun 2015 16:58:02 +0200

Allow setting feed title via CustomFeedTitle config

Allow setting feed title via CustomFeedTitle config
  
@Feed2Red+  @zottel
I try to add an option to have custom feed titles, because some are empty or unusable. I tried this:

my %confVars =
    (
    'CustomTitle' => '',    
    );

And later in the 'post to red' section:

            if ($$f{UseShare} =~ /^y/i)
                {
                if ($$f{CustomTitle} !~ /^$/)
                {
                $title = $$f{CustomTitle};
                }
                $status = "[nobb][[/nobb]share author='" . uri_escape_utf8($title) . "' profile='$feedLink' link='" . $entry->link . "' posted='$modUTC']$status\[/share]";
                }


I get the following error in the terminal (testbed.pl is my test script):

testbed.pl: Error in [FEED] section before line 12 in file testbed.conf:
testbed.pl: No CustomTitle line found, and no default for CustomTitle available from previous [DEFAULTS] section.
testbed.pl: Skipping this feed.


Help!
  
Hi Zottel. Hopefully you had a great holiday. Thank you looking into this. Much appreciated.

It's very simple. The title of the feed (not the individual post) is sometimes empty or non descriptive. For those feeds I like to override the title. This can than be placed in the config file with the parameter CustomTitle.
  
@jeroenpraat I just updated the git of feed2red.pl. You can now set the variable CustomFeedTitle (note that I added "Feed" to your CustomTitle implementation to make it clearer what that does) at a feed to set a custom feed title.
  
@zottel Thank you!!!! :-D
 
Hi I used to use the feed2red plugin in the past and it worked great, but I had it disabled for a while, and I am having trouble getting it re-enabbled..

The feed2red.pl runs fine and populates the db.* files but I cant actually enable the plugin.. when I attempt to from the admin interface I get the below message.. but nothing I can see in the logs to point me in the right direction..

Bild/Foto


This is from a clean git clone for the github page as well..

Sugestions?
  
ok, so if it isn't a addon I should move it out of that sub folder.. is there a recomended place for it ?
  
It's a script that's unrelated to redmatrix. It just sends the data it gathers to redmatrix.
So basically you can put it anywhere you want, with the restriction that it shouldn't be in a directory that's scanned by another program to find plugins/addons.
Typically I put those scripts into a folder $HOME/bin in my own user account or in a special user account created for that script.
  
ok, cool thanks seems different than I recall.. Guess memory is fuzzier than I recall too ;-)
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Mon, 23 Mar 2015 17:15:11 +0100

Fix garbled titles/authors from Atom feeds

Fix garbled titles/authors from Atom feeds
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Mon, 23 Mar 2015 15:36:05 +0100

revert 3d4149a

revert 3d4149a
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Mon, 23 Mar 2015 08:55:55 +0100

Merge pull request #3 from filipesaraiva/patch-1

Merge pull request #3 from filipesaraiva/patch-1

Fix UTF-8 encode in title and author
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Sun, 22 Mar 2015 01:52:50 +0100

Update feed2red.pl

Update feed2red.pl
  
@!Feed2Red+ I still have problems with the character encoding of the titles. Example: There’s a 30% chance your shrimp isn’t what you think it is

Do you think this is a feed2red issue, a Perl issue or something else? Other texts look okay.
  
This particular example looks like coding issues, e.g. the web server says it serves latin1, but the contents are actually cp1252 or something like that. I'd have to see an actual feed example to be sure.
  
Mmm I think it's related to the TinyTinyRSS feeds. Let me investigate that first.
  zuletzt bearbeitet: Thu, 30 Oct 2014 21:56:46 +0100  
The feed start like this (the URL from my TinyTinyRSS instance has been replaced by xxxxxxxx):

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="atom-to-html.xsl"?>

<feed xmlns="http://www.w3.org/2005/Atom">

And here the example in the feed:

<entry>
    <id>http://xxxxxxxxxxxxxxxxx/public.php?url=http%3A%2F%2Fqz.com%2F289087%2Ftheres-a-30-chance-your-shrimp-isnt-what-you-think-it-is%2F</id>
    <link href="http://qz.com/289087/theres-a-30-chance-your-shrimp-isnt-what-you-think-it-is/" rel="alternate" type="text/html"/>
    <title type="html">There’s a 30% chance your shrimp isn’t what you think it is</title>
    <summary type="html"><![CDATA[Be it cocktail, scampi, or alfredo, that shrimp you just ate was very possibly an impostor.
The envi...]]></summary>
    <content type="html"><![CDATA[<html><body><img width="640" height="360" src="http://img.qz.com/2014/10/pink-sherbet-photography_ed.jpg?w=640" alt="The ol' bait and switch."><p>Be it cocktail, scampi, or alfredo, that shrimp you just ate was very possibly an&nbsp;impostor.</p>


...etc.

Now I see that in the text they use HTML-codes for exotic characters. So that explains probably why the text is displayed normally.
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Tue, 23 Sep 2014 15:24:44 +0200

explain that the RedMatrix now supports feeds natively

explain that the RedMatrix now supports feeds natively
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Tue, 23 Sep 2014 15:08:15 +0200

cherrypicking jeroenpraat's pull request

cherrypicking jeroenpraat's pull request
  
The biggest change is there is now a config option named UseQuote that, if set to Y, will put the post into [quote][/quote] tags. Plus some quirks in html2bbcode conversion that jeroenpraat has fixed. Thanks!

I also added that, as the RedMatrix supports that now, <h1>, <h2> ... tags will be translated to [h1], [h2] etc.
  
Recent Commits to feed2red:master schrieb den folgenden Beitrag Tue, 08 Jul 2014 09:45:27 +0200

Added explanation about problems with hash signs in passwords, thanks to Christian Kalkhoff for the hint!

Added explanation about problems with hash signs in passwords, thanks to Christian Kalkhoff for the hint!
  
Tried to install @Feed2Red, installed needed perl modules and set it up. Unfortually I get

feed2red.pl: Error posting to Red: Unauthorized
feed2red.pl: Skipping id www.softmetz.de/feed http://www.softmetz.de/?p=1638
feed2red.pl: for channel softmetzbetrieb on server https://matrix.softmetz.de/.

I copy'n'pasted the config values and was able to perform a regular login. Anything I have to enable in the channel to get feed2red to run?
  
I quess quotation should be fine. In this case you have to watch out for quotation characters in the password.
  
Maybe a suggestion:
You could just limit the possibility to add comments to full lines
so instead of allowing
somevariable = somethingst\#range # this comment is really necessary
you'd only allow comments on full lines:
# this comment is really necessary
somevariable = somevariable = somethingst#range


Most programs only ship with configuration files in that form for that exact reason and it's very rare that I have a comment that really should be on the same line.
Escaping would only add to confusion.
  
That would have worked if I had done it like this from the start, but now an update could make existing configs unusable, especially because the example configs use this kind of comment.

As I said, I'll just keep it like it is for now. If there's really somebody who can't live with it, I'll probably do some special escape that can't break anything else that is already existing. But I'll only start thinking hard when that happens. ;-)