Web Browser News #914
Comments
Martii
added
the
feature
|
Still hunting for a suitable RSS/Atom feed "puller" as well as "pusher" package... until this is assigned you are welcome to go visit https://npmjs.com , do some light reading, and give some recommendations. :) |
|
I find it appropriate to ask, with roughly 600 results for "rss" and over 1000 results for "atom", what do you want me to look up for?
If I understand correctly, you want a package that would download (pull) RSS/Atom feeds and create (push) a feed that would join all the downloaded feeds, is that correct? Would you accept more than a package to do this task? |
|
Hehe now you see my dilemma in past searches... lots of results and I have other coding tasks to take care of that are of higher priority... basically we need a fully configurable package that preferably has it's own cache, but not mandatory... if we have to make a model for it we will, ... configurable feed urls, limits, etc. This is generally how the node community works... each project handles smaller "things" well and the community at large pulls it all together... assuming you didn't know this and I do constantly teach. This is probably a later label but perhaps something you've seen somewhere else might be good... so IDK yet. |
|
I think, I have found a nominee. |
Please do assume so. |
|
Some observations:
Misc:
Generally with packages we like to start with middleware first, then asynchronous, and dead last synchronous packages... all JavaScript (ECMAScript based). "On the fly" is recommended because we would like to be able to use a JSON to configure it dynamically. The "flags" are my own internal system and is usually what determines if a package if viable or not. We used to have a basic html sanitizer but it was quite limited before I came on board... now we have the top rated, most supported, nice professional maintainers, good documentation, good activity, stability, etc. Refs:
There are a lot of ideas that we share from USO that I would like to implement here but every spare moment of free time is taken with the labeled priorities and other duties... so any help is much appreciated. The other members have their own lives too but contribute when they can. The TOS pretty much explains it all... progress can be slow at times and faster at other times. |
For record, combine-rss is licensed under BSD. |
|
|
|
Would you accept a command-line feed reader package, and generate a feed with another package? Readers Generators Note to myself, I have stopped at page https://www.npmjs.com/search?q=rss&page=8 at absolution by boutell |
The general terminology across the board for this type is CLI (Command Line Interface)... as long as it has a matching API as well, that we can programmatically use in node, it's fine if it has a CLI tool too... however I won't be adding a cron task in the VPS for CLI updating nor the process manager... the task needs to be done in our code via node.
Well you've given quite a few... very much appreciated and thank you... I'll spend some time checking them out... one by one... in between other issues. :) |
|
Hmmm I am seeing a pattern here with the current candidates... all seem to be missing Atom support. We need both RSS 2.0 and Atom aggregation... and would prefer it in one package if possible.
|
|
Please do let me know what is missing and I will resume seeking. Eventually, I will lookup for a package that does it all. What are has "smart" limits? |
https://github.com/fent/node-feedsub#new-feedsubfeed-options ... see
... stopping parsing of the document download is a very big plus! One problem I see currently with all of them so far is when I restart the server it has to download everything again in order to store the "history" in memory... this is where we can model in something for "last date" and some other API method/property from a package/project. e.g. don't continue to pull earlier than this date/time which seems to be missing for a manual specification... although |
I thought you find an appropriate module already. I think I should gh-wiki. This thread is too big. |
No, the issue discussion stays here... the wiki isn't meant for that.
I'll ignore that ... you know exactly what I've been up to and my patience is thin today. |
|
I apologies. I will continue to seek for it, weekly. Page https://github.com/OpenUserJs/OpenUserJS.org/wiki/RSS was deleted. |
|
In concern to the following resources: https://github.com/filipedeschamps/rss-feed-emitter Would it help to open issues in concern of lack of features that require for our (this) issue? |
|
There are two packages that seems to be relevant, but links to repositories are not valid. @krl @nfour Gentlemen, kindly provide up to date links, if you may. |
There are only 21 results for "opml". https://www.npmjs.com/package/planet-feeds
(written in .erb) https://www.npmjs.com/package/reading
(written in Javascript) The latter seems to be relevant. |
|
Is it possible to combine keywords in search? https://www.npmjs.com/search?q=planet%20feed (1 result) Added more potential packages Update: April 29th, 2016 Stopped https://www.npmjs.com/search?q=rss&page=11 at jstoxml by davidcalhoun ( 638 results for ‘rss’ ) |
Always provided they are receptive to that... licensing is a key as I previously mentioned too... no CLA's too as those are unenforceable and something we don't want for maintaining.
Again you see the issue that I was having... npmjs.com has search related issues. I appreciate your traversing through these and doing a pre-analysis so we can weed out the bad ones and concentrate on a good supported one when it's found. :) |
|
Mailing list is dead e.g. gone 👎 Not to mention ".erb". (whatever that is) Uses a banned sub-dep; a little overkill too since we really just need the urls and some "smart" limits to maintain traffic. 👎 (Core is feedparser) |
I should have done a list of modules that I have seen. Results are 646 (was 638) and 216 (was 212). I hope I have not skipped any results. Do you have a way to aggregate a list of results from npm? |
The whole of JavaScript under node and all of our current dependencies. If we need storage we can allocate a DB model (BSON) or a file system JSON ... but noise level via traffic will always be a concern. Probably an egg timer or a user initiated sweep on a period could be used to update. The storage mediums are outlined over here... currently in red. |
|
@Martii, I want to try to add this feature. Do you have a recommended resource to learn node.js? I know basic Javascript. Should I learn jQuery as well? |
Not really. However it depends on your learning curve. Some are reference learners (that's me) and others are tutorial style (usually not me).
jQuery is only on the front end DOM however at some point when I have time it will be converted to plain JavaScript. Some dependencies use jQuery which is unfortunate. There is also "jQuery slim" which I ran by a couple of weeks ago and haven't had time to see what it is. So for OUJS concentrate on real JavaScript but still keep jQuery in mind. |
|
I am a reference learner, but I am currently referring to tutorials. |
Try this... haven't visited those yet but may be something for you: Search engines too. I'll help when I can. |
|
Because we only need title and link, and an (x)HTML parser should be built in, I think this task can be done with no additional libraries. I would like to work on this task too. |
You are assigned. Just as a, possible reminder, note since GHacks.net has increased their news count we will need a limiter and probably some sort of filtering as we really don't want advertising to bleed through. Same goes for any site that provides a RSS/Atom/other feed. |
|
On Sun, 03 Dec 2023 09:35:04 -0800 Marti Martz ***@***.***> wrote:
@sjehuda
> I would like to work on this task too.
You are assigned.
Thank you.
Just as a, possible reminder, note since GHacks.net has increased
their news count we will need a limiter and probably some sort of
filtering as we really don't want advertising to bleed through. Same
goes for any site that provides a RSS/Atom/other feed.
Then we can add an approval mechanism.
The news items will be aggregated and the OUJS administrator will get a
notification for each item, in both forms, email and as a notification
in the UI of OUJS.
I like the idea of filtering, which I myself need to improve in my own
RSS bot (Slixfeed).
I think filtering would be an extra feature to colour/mark suspicious
items to ease on the administrator.
|
I'm thinking of relegating this to Moderator and up... I literally have too much on my plate... forwarding up a questionable item may be Admin and up. Since I also maintain the back end and migration I run out of time constantly.
The VPS in its current state will not be configured this way for some time. i.e. no emailing at this time. |
News section under Announcements section, similarly to the one that was on USO.
New news items to be featured would be Qupzilla, Tampermonkey, Violentmonkey, and WebExtensions.
I think that updates in concern to WebExtensions and the deprecation of XUL API would certainly fit.
The text was updated successfully, but these errors were encountered: