Open agateblue opened 4 years ago
Hi everyone, i want to work on this issue. Is this function the good place to start ? Thanks !
(sorry, for the delay) Yes it is, and there is a similar one in src/routes/blogs.rs IIRC.
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.
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.
thank you for your work on this @papey, I'm going to try it soon on https://blog.funkwhale.audio!
@KitaitiMakoto after your work on #764, do you think there is something more to do to resolve this issue ?
@papey Thank you for mension. No, there's nothing to work with this issue although still some validation errors remains.
Based on my research, entries included the Atom feed generated by Plume doesn't include any
atom:id
andatom: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:
As you can see:
id
is emptyupdated
is emptypublished
is missingTHere are probably a few more fields that are available in the spec you may want to include, like
summary
,rights
orcategory
(to indicate what blog the entry is coming from?)