OPML export/import

[kuchta]

Hey, thanks for finally some local/offline-first rss/feed reader that doens't require any installation or backend. 👍🏻 👏🏻

It's quite unfortunate it suports export/import in some JSON, which probably no other RSS reader supports. Supporting OPML is quite paramount today.

I may try to implement that feature myself, if you are accepting PR and if I won't find any project, that already has that support...

[strdr4605]

This sounds like a good idea. Never heard of OPML format. I will look into it.

Also PRs are welcome (drafts too).
But let me know if you're working on this (I will assign this issue for you), so I or other contributors will focus on something else😊.

[kuchta]

Well, it depends on where you want to take this project. I'm personally looking for a project (with possible participation) that would work/look something like ⬇︎ (Feedly), but open-source and completely client-side, maybe just with some option to use CORS proxy, for users who don't know how to relatively "securely" bypass SOP just for this one site. I don't require any advanced features like (offline) reading of content in the app, but bookmarking articles would be great and p2p cross-device synchronization would be awesome, though...

[strdr4605]

From what I checked in. OPML export/import can be used only to migrate from/to https://cofeed-19.github.io/.
Initially, I thought that it could be a replacement for custom JSON export/import that is mostly used as backup or migration from one browser to another.

I think OPML export/import would be a valuable addition here.

Probably the best is to add a new Migrate to/from subsection in the Usage section.

[kuchta]

No, OPML is general feed export/import standard, that basically all RSS readers support and I've tried a TON of them. It's probably harder to find one, that doesn't support it since there's probably no other standard like it, or not used very much...

[strdr4605]

Yes, I understood this. And I think @cofeed-19 should support OPML. Will play with it in the next weeks. But if you want to contribute, I will be glad.

Importing (which seems more important first) probably should have a file input, then parse the file with some library https://www.npmjs.com/search?q=opml then call:

        await insertSiteFeed({
          url: feedUrl,
          visited: {},
          favicon: feedFavicon,
          priority: 0,
          ...feed,
        });

Exporting could be done as a separate PR later.

[kuchta]

Yes, that totally make sense. I was also thinking how to overcome SOP/CORS and I realized that Web Extensions can be granted permission to access any site. Unfortunately, mobile browsers usually don't support browser extensions, at least mine doesn't, so I thought about making the app in react native, since mobile apps don't have any such restrictions either. That would open the way for using the reader on both mobile and desktop, which I do quite often, so some kind of p2p sync engine would be useful. Would you be interested in developing something like that, or is it out-of-scope for you?

[strdr4605]

Unfortunately, mobile browsers usually don't support browser extensions

It depends; for example, Safari on iPhone supports extensions (I use them). Also, if I am mistaken, Firefox on mobile supports extensions.

making the app in react native

For now, this is out of my scope. I created @cofeed-19 as a way to explore local-first, client-side databases, localStorage, and IndexedDB. I don't want to deal with submitting a mobile app to App Stores. I would be open to exploring the PWA version of @cofeed-19. With or without the support of CORS. (But for this the point bellow is necessary).

p2p sync engine would be useful

This sounds interesting, I would like to see this. However, I am not sure how to implement it yet (without any DB in between of even server [maybe users will spin their temporary sync servers]). The main challenge is to stay close to the idea of client-side only. (Although, I am not strictly against breaking [a bit] client-side only).

[kuchta]

It depends; for example, Safari on iPhone supports extensions (I use them). Also, if I am mistaken, Firefox on mobile supports extensions.

Yes, but basically all the others (with exception of Edge and Samsung Internet) unfortunatelly don't...

making the app in react native

For now, this is out of my scope. I created @cofeed-19 as a way to explore local-first, client-side databases, localStorage, and IndexedDB. I don't want to deal with submitting a mobile app to App Stores. I would be open to exploring the PWA version of @cofeed-19. With or without the support of CORS. (But for this the point bellow is necessary).

I also don't want to deal with submitting app to app stores, but the app can be also sideloaded and with react native you can can have both web and native using just one codebase, basically without any code duplication...

p2p sync engine would be useful

This sounds interesting, I would like to see this. However, I am not sure how to implement it yet (without any DB in between of even server [maybe users will spin their temporary sync servers]). The main challenge is to stay close to the idea of client-side only. (Although, I am not strictly against breaking [a bit] client-side only).

It would be quite easy if the two devices were at least online at the same time, but usually that's not the case, which makes it quite complicated. Right now I'm thinking that it would probably be best to make an IPFS adapter for some reactive database sync engine (RxDB, SignalDB, Yjs, Automerge, etc...). Anyway, I'll keep looking to see if I can find something ready....

[kuchta]

I've probably found ideal technology for this use case. fireproof.storage is local-first, end-to-end encrypted, embedded, authenticated, reactive database with plugable object storage and it supports IPFS and passkeys out of the box. Check it out 😉

[strdr4605]

I've probably found ideal technology for this use case. fireproof.storage is local-first, end-to-end encrypted, embedded, authenticated, reactive database with plugable object storage and it supports IPFS and passkeys out of the box. Check it out 😉

Added a new issue for this topic:

• Sync between browsers/devices without a server #71