You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can lead to a lot of visual noise if you're following a "micro blog" or activity pub type feed that don't have titles.
I'm happy to provide a PR or keep this in a fork but my idea would be to use item.content. This would of course look terrible for most feeds, therefore I think this should be a setting like Auto Refresh, e.g. Use content as title.
The text was updated successfully, but these errors were encountered:
One thing to note is that the /api/items endpoint doesn't return content field of the articles. The reasoning is because some feeds' content is large, and was omitted from the results to make API loads faster.
With that in mind, title either needs to be populated during writing (storing to the db) or during read (fetching via API) in the backend.
Still thinking about this. A few interesting display rules from micro.blog.
If the post has no title and is 300 characters or less, the text is shown directly in the Micro.blog timeline.
If the post has no title and is over 300 characters, the text is truncated with a link back to the full post on your site.
If there’s a title and it looks like a date or number, Micro.blog ignores it, as if there were no title. It then tries to show the text in the timeline.
The current implementation uses
item.title
in the list of feeds and ifitem.title
is empty it will displayUntitled
.yarr/src/assets/index.html
Line 285 in b13cd85
This can lead to a lot of visual noise if you're following a "micro blog" or activity pub type feed that don't have titles.
I'm happy to provide a PR or keep this in a fork but my idea would be to use
item.content
. This would of course look terrible for most feeds, therefore I think this should be a setting likeAuto Refresh
, e.g.Use content as title
.The text was updated successfully, but these errors were encountered: