What do you think about my Mastodon extension?

[simon-pipe]

Hello everyone, I tried my hand at my first extension. It's an extension that can read a Mastodon feed and then turn it into blog posts. You can also filter it with a specific hashtag.

If you want to try out the extension, you can find it here: https://codeberg.org/simonpipe/yellow-mastodonrss

Addendum from August 13, 2025:
Meanwhile, I had to realize that the way via RSS feed was a bad decision. So I wrote a new plugin that now uses the Mastodon API and works for Mastodon as well as GoToSocial (which I use myself).

Here is the link to the new plugin: https://codeberg.org/simonpipe/yellow-mastodonapi

[schulle4u]

Cool! That looks like a quite interesting approach, and definitely a good first extension. 👍 I'll try out the extension when I have the chance. Now it would be perfect if you could also follow your own Yellow blog via Mastodon someday. 🙂

[simon-pipe]

That would indeed be great. 👏
But someone would have to take care of it who can really program. That would exceed my abilities and my time budget.

[markseuffert]

Good work, please don't forget to add the topic datenstrom-yellow to your repository. I have seen you mentioned something about a cron job in the documentation. There's a daily event in the API that you could use in your extension. There used to be an hourly event too, strange, I must have deleted it because nobody used it. For source code example see function onUpdate() in the bundle extension or edit extension. Hope it helps and thank you for working with us.

[simon-pipe]

I added the topic datenstrom-yellow. But the plugin is on Codeberg.org (https://codeberg.org/simonpipe/yellow-mastodonapi).

I implemented the tip with function onUpdate(). Thank you for that.

[markseuffert]

You are ahead of us. We started to mirror or move some repositories to Codeberg. By the way, this year we put some requirements on new extensions. It would be unfair to enforce this for already announced extensions, but it would be nice if you could have a look. Make yourself familiar with our style guide as suggested in the self-review checklist. For example version numbers should begin with the release number, e.g. 0.9.1 or 0.9.2, then users know if an extension is compatible.

[simon-pipe]

I have gone through the rather strict style guide and checklist, adapted the version and marked the plugin as experimental to test it a bit longer.

Thanks for the quick response.

[markseuffert]

I removed all requirements for experimental extensions, but maybe you find some suggestions on the checklist useful.