If you have a project where the ability to import/export OPML is on the roadmap but you haven't added it yet, consider taking a few minutes to implement text/uri-list first.
1. <https://github.com/Automattic/pocket-casts-android/blob/864d...>
If you have a project where the ability to import/export OPML is on the roadmap but you haven't added it yet, consider taking a few minutes to implement text/uri-list first.
1. <https://github.com/Automattic/pocket-casts-android/blob/864d...>
text/uri-list seems like joy to use technically, but in practice simple formats have tendency to evolve into frankenstein monster with a mess of extensions and variations (see markdown for example) where every vendor will extend the format to support something for their platform.
Users expect to maintain their feed structure for example when moving to a new platform just like a file system hierarchy, which text/uri-list doesn't seem to support right off the bat
Compare to OPML, which is supposed to support other things—exactly the type of things you describe—but it requires special handling in the implementation to actually do it, so you get implementations that don't, which isn't far off from the exact situation of variants that you describe. See the previous OPML importer that I linked to for an example.