Add RSS and Atom Reader

zakius

See Newsfox: essentially M2 or Smart RSS functionality with middle click on article list to open in new tab (or enter to open all selected in new tabs)

modedit Merged duplicate thread

--
ModEdit: Added the Missing M to the "ModEdit" Edit :smiling_face_with_open_mouth_smiling_eyes:

Seasonly

I'd would like one with images like brief

NemoAnonymous

Also, to be able to open in background tab. The biggest issue I have with separate RSS readers is losing focus on the reader with every tab I open. My workflow is to open a lot of tabs from my RSS feeds first and then go read them. That means I'm constantly clicking back and forth from the reader to the browser and back.

Wraith5

I'm guessing this will be part of the integrated mail client. But if it won't (of if that's too far out), I could live with an RSS panel with dynamic settings in the sidebar (and an accompanying symbol in the address bar automatically recognizing feeds so I only need to click to add them, like old Opera).

LonM

I liked M2's 3-column layout.

Having used M2's integration of both mail and RSS, I would much prefer to keep the mail and feeds separate.

A side panel would be nice, for example, to list feed items, when clicked on they open the feed item in a new tab. (Ideally, each subsequent click of a panel feed item opens the full feed item in this same tab , without spawning tons of new ones).

For my needs, I don't really care about seeing a list of subscribed feeds, so 2 columns is enough.

NoAidee

Pleas add a feed reader.

becm

When implementing this please do not mix these 3 vastly different functionalities.

The mail client can be a separate process without any understanding of website technology foo. While I fear its functionality will mostly be implemented with some fancy javascript, an (optional) HTML viewer should live in a separate constrained chrome renderer process. A good implementation should allow a standalone operation or UI-integration into Vivaldis sidebar.

RSS subscriptions are a special form of bookmarks, how to integrate with existing code/UI is more taste than technical decision. All a subscrition display needs is a way to query some feed metadata (already done for regular bookmarks).

Displaying RSS feeds requires "just" a special form of a chrome renderer to process special XML tags, keep track of entry tags (read/important/etc.) as part of parsing a feed and additional loading logic to append additional data for paged feeds. Keeping data other than a registry of entry tags should be an option (as well as purging tags for older entries) to save space and improve privacy.

Folgore101

@lonm Yes, a dedicated panel type this extension RSS Feed Reader would be perfect for my use.
alt text

ozoratsubasa

There a lot sites that uses the RSS to promote their articles and It would follow them better. Mainly the Vivaldi blogs.

Ayespy

@mau That hasn't been discussed. We'll have to wait and see.

zakius

well, I'd love to have TT-RSS integration, but since it natively doesn't support my workflow anyway it wouldn't be especially useful...

if we get complete newsfox workflow I can give up sync with no complains

wea0

All I need from any browser-integrated RSS functionality is that when I navigate to an URL such as https://vivaldi.com/feed/ the browser renders it in that tab as something remotely resembling a webpage (e.g., like Firefox) instead of spewing out source code like Vivaldi. Can I have that?

NemoAnonymous

@becm
I'm not quite sure I understand why people call RSS a form of bookmark instead of a message? Bookmarks are a static link that you click to pass a URL to the browser to open a page. An RSS feed has a sender, date, topic, and body (often a sample or preview of the page), like an e-mail message. The workflow that I, and others use, is to review the RSS feeds in the reader, which means 'opening the body' and rendering it like an e-mail. This allows us to decide which pages to open and which to skip. Old RSS notifications may be stored and reviewed at a later point, much like an e-mail message. For my workflow, a 3-pane display like the old M2 is ideal, whereas using a bookmark like interface would be useless.

zakius

@nemoanonymous M2 was almost perfect, it lacked ability to middle-click on second pane to open articles in new tabs (full pages, not whatever was embedded in feed)

NemoAnonymous

@zakius
True about middle-clicking the second pane, but most posts (third pane) have a link in them that you can middle-click to open the page, particularly if you have that assigned as opening in background tab. In fact, that functionality is what is missing from every other RSS feed and why, for certain high volume RSS feeds, I still use Opera 12.

becm

@nemoanonymous the feed (RSS/Atom) data is a linear XML document which has to be downloaded and parsed in its entirety.
The "reading software could … present a neat display to the end users".

feed selection → Bookmark (URL to check regularly)
feed content → metadata and items (for each feed)

The bookmark entries COULD be enhanced by the parser(/renderer) component with data retrieved from their corresponding feed or some other data related to feed-specific persisten storage (unread item count).

zakius

@nemoanonymous having to left click, move cursor to third pane, middle click, move back and so on isn't the most efficient way of using the reader imo

NemoAnonymous

@becm

Still not sure I understand the point... An individual e-mail is a linear mime encapsulated document that has to be downloaded and parsed in its entirety, similar conceptually to an RSS feed. But more fundamentally e-mails are metadata and content just like RSS feeds whereas bookmarks lack content. Why break content and metadata apart when you already have a conceptual framework for handling both together? Particularly when there is an interest in at least a portion of the customer base to implement something similar to M2's functionality for RSS anyway? I don't understand what the gain is to move to bookmarks.

@zakius
True enough it would be faster. I'd never really considered it that way, so it sounds like a good improvement to me, as long as the ability to open in a background tab is maintained. I typically go through my entire feed first before reading individual tabs, so opening them into the background saves a lot of time.

becm

@nemoanonymous the distinction is feed-subscriptions and mail-accounts.
Interaction with the remote point (appart from reading) is vastly different.

RSS/Atom data is a XML file (generally) retreived via HTTP(S), containing some header info and (generally) only the latest (5, 10, whatever) "news" items in bulk. A feed subscription is just an URL to this file ("bookmark").

Mail servers provide various operations via user-authenticated sessions. Single message retreival is supported. Transfer protocols and (regular) content do not require an HTTP engine or XML/HTML parser.

There is no mention of deviating from the way M2 actually interacts with or displays feeds (from a user perspective) anywhere in this thread (to this point).
The (other) discussion is to give feeds their own side pannel (as I and others would prefer) or ~~mis~~ reuse the mail panel (again).

zakius

@nemoanonymous surely I meant "default browser behavior on middle click" so if you set m-click opens in bg then it opens in bg, but some people change that to fg so they are free to do so

@becm you are talking about so called "live bookmarks"
proper RSS reader caches contents and remembers stuff that got removed from feed itself due to size limitations (you can't expect feed to store all entries since the very beginning, can you?)

But yeah, I wouldn't use the mail "panel"/fullpage for that, just the almost exact clone of it to separate concerns