Open
Description
In the initial discussions of adding to the blog list, (#1 ) we also came into discussing adding other types of content like videos etc.
We have a basic starting point with blogs, and we can build upon that as we go, when/if we decide on adding other types of content too.
Metadata
Metadata
Assignees
Labels
No labels
Activity
cosimameyer commentedon Apr 11, 2023
I like the idea! I also thought of promoting YouTube videos (and chapter meetings' recordings?) with the Mastodon bot.
drmowinckels commentedon Apr 11, 2023
I think we can easily expand to youtube channels at least.
cosimameyer commentedon Jul 15, 2023
A quick update:☺️ ☺️
I added the functionality to the bot to process YouTube content and also added a new description how to add it to the Awesome repo. It comes with a new entry
rss_feed_youtube
. It assumes that people not necessarily have to have a blog/website, however but that a vlog (although it's not really a vlog - but it's content produced in a video format) is also okIf you think it's a good idea, I'm happy to set up a PR with changes for this repo here as well
drmowinckels commentedon Jul 15, 2023
I love love love this! Thank you so much for the initiative!
I was wondering, does it have to have a
rss_feed_youtube
entry, or can it just be in therss_feed
section, but could be obvious if its a vlog through the entry category? I think it depends on how we want to handle this.I think my initial idea would be that if a person has a blog and a vlog, they would get two entires. Since the content/cards are structured around content rather than authors (since we have multi-author options). So the data is for the content source, not the content author. Does that make sense?
In my case for instance, I'd have
drmowinckels.io.json
andyoutube.com.drmowinckels.json
(foryoutube.com/@drmowinckels
, skipping slashes and @ for neater file names).I'm not married to this idea, but to me it makes more sense that each card is a single feed source, rather than author-centric.