Missing date/id in atom feed #673

Open
opened 2019-10-07 09:11:39 +00:00 by EliotBerriot · 7 comments
EliotBerriot commented 2019-10-07 09:11:39 +00:00 (Migrated from github.com)

Based on my research, entries included the Atom feed generated by Plume doesn't include any atom:id and atom:published elements.

While published is optional, atom:id looks mandatory in the specification and its absence is likely to confuse feed readers.

In a personal projects of mine, I am aggregating multiple Plume feeds, and the absence of the published value means it's impossible to order the entries by date after aggregation.

Example from https://plume.social/@/Aster@amplifi.casa:


<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Aster</title>
    <id>https://plume.social/@/Aster@amplifi.casa/atom.xml</id>
    <updated></updated>
    <entry>
        <title><![CDATA[Eu também ignorei essas coisas no começo]]></title>
        <id></id>
        <updated></updated>
        <author>
            <name>Aster</name>
            <uri>https://amplifi.casa/@/Aster/</uri>
        </author>
        <link href="https://amplifi.casa/~/Asterismos/eu-também-ignorei-essas-coisas-no-começo/" rel="alternate"/>
        <content type="html" src="https://amplifi.casa/~/Asterismos/eu-também-ignorei-essas-coisas-no-começo/">REMOVED</content>
    </entry>
</feed>

As you can see:

  • id is empty
  • updated is empty
  • published is missing

THere are probably a few more fields that are available in the spec you may want to include, like summary, rights or category (to indicate what blog the entry is coming from?)

Based on my research, entries included the Atom feed generated by Plume doesn't include any `atom:id` and `atom:published` elements. While `published` is optional, `atom:id` looks mandatory in the [specification](https://tools.ietf.org/html/rfc4287#section-4.2.9) and its absence is likely to confuse feed readers. In a personal projects of mine, I am aggregating multiple Plume feeds, and the absence of the `published` value means it's impossible to order the entries by date after aggregation. Example from https://plume.social/@/Aster@amplifi.casa: ```xml <feed xmlns="http://www.w3.org/2005/Atom"> <title>Aster</title> <id>https://plume.social/@/Aster@amplifi.casa/atom.xml</id> <updated></updated> <entry> <title><![CDATA[Eu também ignorei essas coisas no começo]]></title> <id></id> <updated></updated> <author> <name>Aster</name> <uri>https://amplifi.casa/@/Aster/</uri> </author> <link href="https://amplifi.casa/~/Asterismos/eu-também-ignorei-essas-coisas-no-começo/" rel="alternate"/> <content type="html" src="https://amplifi.casa/~/Asterismos/eu-também-ignorei-essas-coisas-no-começo/">REMOVED</content> </entry> </feed> ``` As you can see: - `id` is empty - `updated` is empty - `published` is missing THere are probably a few more fields that are available [in the spec](https://tools.ietf.org/html/rfc4287) you may want to include, like `summary`, `rights` or `category` (to indicate what blog the entry is coming from?)
papey commented 2019-11-25 15:28:18 +00:00 (Migrated from github.com)

Hi everyone, i want to work on this issue. Is this function the good place to start ? Thanks !

Hi everyone, i want to work on this issue. Is [this function](https://github.com/Plume-org/Plume/blob/52d860d402e320b11f0da2700ef50e27b01f85d2/src/routes/user.rs#L605) the good place to start ? Thanks !
elegaanz commented 2019-11-29 18:36:42 +00:00 (Migrated from github.com)

(sorry, for the delay) Yes it is, and there is a similar one in src/routes/blogs.rs IIRC.

(sorry, for the delay) Yes it is, and there is a similar one in src/routes/blogs.rs IIRC.
Kekun commented 2019-12-10 11:56:35 +00:00 (Migrated from github.com)

This is very likely why I can't have my new fediverse.blog blog on Planet GNOME: https://gitlab.gnome.org/Infrastructure/planet-web/merge_requests/32.

This is very likely why I can't have my new fediverse.blog blog on Planet GNOME: https://gitlab.gnome.org/Infrastructure/planet-web/merge_requests/32.
papey commented 2020-01-14 10:14:29 +00:00 (Migrated from github.com)

The issue is partially fixed by the now merged PR #720.

Currently, there is no data structure to fetch updated status for a blog post. This issue is, for now, blocked by #722.

The issue is partially fixed by the now merged PR #720. Currently, there is no data structure to fetch updated status for a blog post. This issue is, for now, blocked by #722.
EliotBerriot commented 2020-01-14 11:28:59 +00:00 (Migrated from github.com)

thank you for your work on this @papey, I'm going to try it soon on https://blog.funkwhale.audio!

thank you for your work on this @papey, I'm going to try it soon on https://blog.funkwhale.audio!
papey commented 2020-05-22 20:09:32 +00:00 (Migrated from github.com)

@KitaitiMakoto after your work on #764, do you think there is something more to do to resolve this issue ?

@KitaitiMakoto after your work on #764, do you think there is something more to do to resolve this issue ?
KitaitiMakoto commented 2020-05-23 06:09:05 +00:00 (Migrated from github.com)

@papey Thank you for mension.
No, there's nothing to work with this issue although still some validation errors remains.

@papey Thank you for mension. No, there's nothing to work with this issue although still some validation errors remains.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#673
No description provided.