@prologic@twtxt.net Consider making feeds.twtxt.net support pleroma/akkoma instances too.
I don’t think that you can get a rss feed from them, so it might be a
little more work. Sorry, I know it might be difficult so if it’s outside
of the project’s scope it’s not needed but it’d be nice.
(I think it’s completly out of scope so no need really, I don’t know if
I should host another feeds instance for myself as I don’t know if I
should really setup my rss from newsboat to jenny (getting emails
made by jenny in a directory in my home directory)
I fell like I want to do the oposite, have twtxt feeds available as rss.
(I should probably write a script or something that runs jenny (on
cron), and then parses the mail folder for mail, and makes every email
be a entry in the rss feed)
@prologic@twtxt.net Yeah, they are. I’m running Pleroma at social.nfld.uk, for example.
@jmjl@tilde.green Ahh you are right about client discovery! This us a thing 😆 However:
Is there any protocol to not need to go to each yarn instance and tell
them that a twtxt feed X exists?
Why would you want to do this?
@jmjl@tilde.green I’m not sure what you mean by:
Because yarn doesn’t seem to work properly with client discovery
Can you elaborate on what you mean?
As for parsing NGINX logs, I recommend using this tool
@jmjl@tilde.green Sorry I’m a little confused 😢
@jmjl@tilde.green It absolutely does! It supports both single-user and multi-user agents as described here:
@jmjl@tilde.green It did but we don’t surface it to users very well unfortunately 😢 Something to improve 🤞