Christine Lemmer-Webber2d ago

If you wanted to make high-impact fediverse software, I would recommend making a simple daemon that does the following:

- Consumes RSS/Atom feeds
- Posts them as subscribable feeds over activitypub
- So dead easy you can host it yourself as a simple daemon on your server
- Optionally: collects replies as a comment section with a way to render them inline, a-la disqus, with some simple moderation tools. Simplest way to reduce spam would be to make it approve-only to show up on the feed.

You could extend this to allow posting on other servers etc. But, in other words, let more people use the static site generator they already have

Show threadjadedctrl  
@cwebber I wrote this little guy a while back, not sure if it fits your description: https://kod.ujo.moe/jadedctrl/sfeed_mastodon
Testante homecon! — Robot-check!

Apr 12 at 12:56amWeb
Show threadRusty Shackleford1d ago

@jadedctrl
@cwebber

On one hand, love that we can build curated feeds like this.

On the other, it can turn into nothing more than bridging personal news feeds into the fedi, generating redundant noise. I’d likely unfollow someone autoposting everything from their RSS. Just depends on source & how selective.

Logically, makes sense. But if everyone did it indiscriminately, the network would get messy, & the 'subscribe to everything' model starts to seem more like a firehose than a conversation.

Show threadRusty Shackleford1d ago

@jadedctrl
@cwebber

For example: imagine a Mastodon instance that bridges a climate research blog feed. If every single paper gets autoposted, it can flood timelines. But if it only republishes key findings with researcher summaries, it sparks actual discussion.

Signal vs. noise.

Show threadRusty Shackleford1d ago

@jadedctrl
@cwebber

I think I misconstrued things *rubs temples

I need more sleep