Newsfiler - simple RSS to file with fulltext support

situation: imho, all RSS-readers suck
thoughts: "everything is a file", why not news?
motivation: handle news like normal textfiles with regards to linking, sharing, searching, archiving, ... them
(my) solution: newsfiler
newsfiler is a simple script, which iterates over a list of feed urls and transforms it's items to textfiles.
Short description of functionality:
a) read in a list of feed urls
b) extract news item direct links
c) pass these to readability port, thus receiving the fulltext - since most feeds still don't provide them on their own
d) do some formatting
e) write out the contents to: $HOME/news/$feedtitle/[YYYY-mm-dd] @ [HH:mm] with content
Feed Title: Item Title [DATE TIME]
Original Link
Full Content
available featurs:
receive fulltext for any feed
fix feeds not giving a date on their items
todo:
replace links with 'linktext [X]' and having a list of '[X] reallink' at the end
somehow implement parallel threads, it's currently not really fast
some kind of configuration per feed, ie timestamps to only fetch a feed in certain intervals
pass the site hosting the feed as referrer* done *
maybe a mode to write every item of a feed to the same file, so it could easily be followed by ie `tail -f`
maybe a mode to keep html, so it can easily be formatted and looked at in the browser
code clean-up, maybe try to get rid of some deps
written in: Python
deps: feedparser, BeautifulSoup, readability-lxml
download: http://phorcix.org/code/newsfiler
contact: here or see email-comment in the source
Ideas/patches welcome, flame too
Enjoy, or not?!
avx
Edit 1:
quick fix/addition: added dupe-check based on the article's title and date(where available) (needs proper fix for feeds without dates).
some cleanup, more "python-style"-coding
Edit 2:
fixed stupid error not saving anything
added support for custom user-agent and referrer
Last edited by avx (2011-10-22 23:18:16)

Why use Boot Camp: Sometimes you need to run a windows only program. Boot Camp lets you do that with the speed and smoothness of a full windows OS.
How is it different from Mac Virtual Machine: A VM allows you to run another OS simultaneously while you are running OSX, while in a window similar to any other application. A VM is not as fast, smooth, and may have limited screensize/view.
Is it possible to have a VM and Boot Camp: Yes, and I do this because sometimes I want to use a VM quickly without shutting down, sometimes I want the advantages of Boot Camp
How do I get Windows in VM: how-to here:
https://discussions.apple.com/thread/6043251

Similar Messages

For the first time, I'm trying to use adobe premiere elements10 that came with my pc Windows 8. I created a single project, saved it but cannot open it. My pc shows the file I created but I get an error message that says this type file is not supported or

For the first time, I'm trying to use adobe premiere elements 10 that came with my pc Windows 8. I created a single project, saved it but cannot open it. My pc shows the file I created but I get an error message that says this type file is not supported or the codex is not installed. As a test, I created another very small project and get the same error message, when I try to open it. Pls give me a simple answer, a refund or a phone

mike frischenmeyer
What computer operating system is your Premiere Elements 10 running on? And, what video card/graphics card does that computer use?
Is this the first time you are using Premiere Elements 10 or have you worked with it before successfully? There is no easy solution until we
know the details and troubleshoot to determined what caused the problem.
1. Can you open a new project?
2. After you saved/closed the problem project, did you move, delete, or rename any of the files/folder that were related to the source media
for that project?
3. Please review the Adobe document on troubleshooting damaged projects.
Troubleshoot damaged projects | Adobe Premiere Elements
4. What are the steps that you are using to reopen this saved closed project.
a. File Menu/Open Project/Name of Project
b. Other
Please review and consider and then we can decide what next based on your further details and results..
Thank you.
ATR

When a file with extension .htm as a product from Epilex is opened, there was a notify a screen, "This epiLearn is not supported on Netscape browsers. epiLearn supports Internet Explorer 5.5 or above. Please launch it in Internet Explorer"

My company has decided to use Epiplex software.
But when a file with extension .htm as a product from Epilex is opened, there was a notify a screen,
"This epiLearn is not supported on Netscape browsers. epiLearn supports Internet Explorer 5.5 or above. Please launch it in Internet Explorer".
I prefer to use Mozilla than Internet Explorer. Would u please handle Mozilla browser along this problem to be available in this matter?

This might be simple but it works well for me.
1.
Right click on the tool bar in IE8 and uncheck adobe PDF to disable. Click yes when it ask if you are sure.
2.
Open Adobe
READER located in the start menu.
3.
Click on Edit and then on Preferences.
4.
Select the "General" category.
5.
Click on "Select default PDF handler"
6.
Adobe Reader should be already selected. Change it to reader if it is not.
7.
Click on "Apply" and except changes.
8.
Restart the computer and you are done.
Now you can open and save PDF's from IE8. Once you save it, you can right click and "open with" Acrobat if you choose.
Be careful to not make Acrobat the default or you have to start over.
You can still create PDF's from docs, scans, and picture like before. You might think this is a work around but it really isn't.
Some forms that are available on the internet can't be opened by Acrobat for security reasons.
Good luck! P.S. I am not an IT tech but I play one on TV.

How do I import old FCP projects that have mysteriously changed to Linux Executable files? Is it as simple as renaming the files with the.fcp extension?

I had some FCP projects on an old G3 tower that I finally want to finish. I was able to grab everything, media, etc. to my macbook pro but all of the Final Cut Pro actual movies/projects have turned into "linux executable files" that FCP X won't import.
I tried googling this issue but didn't really see any good answers. Would it be as simple as renaming the files with the .fcp extension? I can't recall if my old version (really old) of FCP saves projects as .mov or .fcp files, but I'm assuming I'm not the only person this has happened to.
Thanks for your help!

I had some FCP projects on an old G3 tower that I finally want to finish.
What version of FCP was this? The project files can probably no longer be opened in the newer version of the OS. You could try adding the .fcp suffix, but I don't think it will help for this. Projects files are .fcp.
Regardless of the version, no legacy FCP projects will import into FCPX.
Media is a different matter. These are probably QuickTime .mov files. If these are appearing as Unix ececutables, they're probably not recoverable either.

Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

haben
From looking at the specifications of your camera (SJCam 4000), we know already what video compression your camera is using. It is H.264.
A H.264.mov file should be supported by Premiere Elements 11. On what computer operating system is your Premiere Elements 11 running?
Do you have the latest version of QuickTime installed on your computer? And, are you running QuickTime and Premiere Elements 11 from a
User Account with administrative privileges? Please go to Premiere Elements 11 Publish+Share/Computer/QuickTime to confirm that you find
presets there for the QuickTime choice there.
What are the properties of these H.264.mov files - is it 1080p30 (1920 x 1080p30) or something else? Do you know if this camera is recording with a variable or
a constant frame rate?
Please review and consider and then we will decide what next.
Thank you.
ATR

"there was a problem connecting to the server. URLS with the type 'file' are not supported"

i have a new macbook pro 13" and every 6 minutes or so it pops up a window that says "there was a problem connecting to the server. URLS with the type 'file' are not supported". it never seems to cause any problems but is supremely annoying. how can i make this come to an end?

I tried someone's solution of taking another external disc and plugging it in, then when it showed up and time machine asked if I wanted to use it or that someone might be trying to trick me, I chose not use it. Then I shut down my computer, plugged in the original Lacie, and rebooted the computer and all seems to work fine now-- the Lacie appears on my desktop and all seeems to be in working order. Who knows why or anything else,- as weird as it gets- but for now things seemed fixed--- maybe others can try this too-- it worked for me so far.

"There was a problem connecting to the server. URLs with the type "file:" are not supported. Why? What can be done to eliminate it?

After upgrading to Mountain Lion, I repeatedly get this message: "There was a problem connecting to the server. URLs with the type "file:" are not supported.
Why?
What can be done to eliminate it?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Message - There was a problem connecting to the server. URLs with the type "file:" are not supported

new macbook pro receving this message: There was a problem connecting to the server. URLs with the type "file:" are not supported. What is causing this and how do

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

There was a problem connecting to the server. URLs with the type "file:" are not supported. OK

I have just upgraded to Mountain Lion from Leopard, but now I keep getting this message when I open some web-pages and every time I wake the Mac up after going to sleep. For some odd reason I get it in Swedish sometimes (installed language) and some times in English...
There was a problem connecting to the server.
URLs with the type "file:" are not supported.
OK
What is this and how can I get rid of it. I use Firefox and have updated to latest version.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

A Davey1 wrote:
Not a nice answer!
Posting "Check the 'More like this'" area and not simply providing the answer is a great way to make these groups worthless.
You're ignoring context. On the old Apple Discussion Groups I never posted replies like that, instead giving people relatively detailed answers. The new Apple Support Communities made things worse by introducing certain inefficiencies. Then came Lion. The flood of messages that came with Lion required a painful choice for any of the people who had been helping here: (1) Give quality responses to a few questions and ignore the rest. (2) When applicable, give a brief answer such as the one that you found objectionable. (3) Give up all the other normal activities of life and spend full time trying to answer questions here.
People who needed help with Lion problems seemed to have trouble discovering existing message threads that described how to solve their problems. I never posted the suggestion of "Check the 'More like this' area" without verifying that the help that the poster needed could be found there. Even doing that, what I posted saved me time that I could use to help someone else.
The people helping here are all volunteers. None of them is being paid for the time they spend here. They all have a life outside of Apple Support Communities. It's arrogant of you to demand that people helping here spend more time than they already do.

No permission to copy file (to NAS with AFP support) - extended attributes?

For certain files that I copy from one of my drives to the NAS here (Synology 206j), ever since upgrading to Snow Leopard, Finder's behaviour has changed. It will simply refuse to copy the file, stating that "The operation can’t be completed because you don’t have permission to access some of the items."
The source is an external USB drive in Mac OS Extended format, I do have full permissions on the files and in any case the drive is set to ignore ownership.
The target is, like most NASes, in EXT3 format. It's sharing via its own AFP implementation.
I'd have tried repairing permissions, but for whatever reason, it's greyed out on my external drives. Since then I've figured that it was probably not that anyway, which will become apparent:
I tried copying the file via the terminal and it actually worked, but also gave an error: "cp: myfile: could not copy extended attributes to /Volumes/media backup/myfile: Operation not permitted"
This suggests to me that, as expected, the target volume doesn't support extended attributes. But rather than popping up with the message that Leopard did (something along the lines of "your target volume doesn't support extended attributes so your file's metadata may be lost, do you wish to continue") it just aborts instead.
I'm not sure if this is a Snow Leopard problem or a change that Synology need to catch up with. A workaround is to compress the file to ZIP first.
Thought I'd mention it here before trying to report it as a bug somewhere. Anyone else having similar issues, either with a NAS or some other storage, in which case please specify?
Message was edited by: Cloudane

Thanks guys, yeah I've been monitoring the netatalk mailing list myself: they're onto the same problem, have come to the same conclusions about it being Extended Attributes and have much better proof of such than I
It looks like they're currently debating the best way to fix it (pretending to support EAs but sending them to a black hole being the quick and dirty way, but I suspect they'll go for implementation)
It'll be a while for sure, but the Synology guys are very good with Mac support so I'm sure they'll apply the update fairly quickly once the netatalk crew get something public. FWIW, I did detect a certain sense of urgency from the netatalk discussions.
Although it's essentially answered, I'll leave the question marked as unanswered in case Apple come up with a better one
Message was edited by: Cloudane

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server.

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server, but this message continues to pop-up several times a day at random intervals. Is there something I'm doing wrong? Or is my computer just having a glitch? Other than that, and a mildly sticking caps lock button, it's working perfectly.
Thank you!

Alright it didn't solve it. Any other suggestions?
I haven't suggested a solution yet. I want to know whether you still get the messages while Time Machine is disabled. Do you? If so, try any or all of the solutions proposed in this thread:
There was a Problem connecting to the...: Apple Support Communities

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported." Can someone help me get rid of it.

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported" Can someone help me locate and get rid of this error.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off .

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off and continue working.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Problem with video support file format VOB (Video Object)

I have created a project with VOB files which premiere pro cs4 supported orginally but after an update from adobe it now suddenly it will not recognize them, marking them in the timeline as 'Media offline'. I have tryed to relink them but I kept running into the same problem - 'File format not supported'. I have checked Premiere pro cs4 help and it states that it does support VOB files which it did orginally. I can not tell if it is a codecs problem or not. Help anyone???

>after an update
You MAY have been hit by the "revert to trial" bug
Revert to trial http://forums.adobe.com/thread/763545?tstart=0
- and http://forums.adobe.com/thread/763334?tstart=0

Newsfiler - simple RSS to file with fulltext support

Similar Messages

Maybe you are looking for