I’m not quite sure how it’s going to work but while you’re at it, could you make an offshoot that posts releases? We could make a community just for those. Here are some:
If you could just put all feeds in a config and individually point them at communities, that would be amazing!
That’s how I’m building it. So you’ll be able to call a config that logs in, checks multiple RSS feeds for updates, posts the updates each in their specified community. You can have multiple configs that each have a different login and post different things. You’ll call the script and pass it a config file path from a cron job, and you can have as many of those as you like and as many different configs as you like on your VPS.
I’m going to build you a config that does the usual Monero newsletters plus CCS, you’ll have to input login info for it in the config. You can use that as a template to make any number of them that post any number of RSS feeds from any accounts you want to create. You should probably create a monero news bot account for it, and I’d do separate bots for lemmy updates, monero releases, etc. The accounts dont have to be mod or admin, they just have to be able to post.
You’re about to see some testing going on later today from this account. That’s me testing this thing.
Do you happen to know the API endpoint for logging in? I can’t for the life of me find it. The docs say https://instance.TLD/api/v3/user/login?username_or_email=<username>&password=<password> but /login goes nowhere, at least for monero.town.
I’m also about to post after I get login working so if you know the format of that query string you can toss that in too, save me some time fumbling with the lemmy docs.
From someone on matrix:
It’s a POST endpoint
The response is a jwt and a few flags.
Well you have to post and the body is json with the attribute rather than GET request params
Awesome, I’ll be looking forward to it! There’s no need for you to rush though :)
Do you happen to have an RSS/atom feed URL for the CCS site? I can’t find one at ccs.getmonero.org
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests.atom?state=opened
I’m not quite sure how it’s going to work but while you’re at it, could you make an offshoot that posts releases? We could make a community just for those. Here are some:
And perhaps a non-monero news one:
If you could just put all feeds in a config and individually point them at communities, that would be amazing!
I also just found this bot, not sure if that helps you with anything.
That’s how I’m building it. So you’ll be able to call a config that logs in, checks multiple RSS feeds for updates, posts the updates each in their specified community. You can have multiple configs that each have a different login and post different things. You’ll call the script and pass it a config file path from a cron job, and you can have as many of those as you like and as many different configs as you like on your VPS.
I’m going to build you a config that does the usual Monero newsletters plus CCS, you’ll have to input login info for it in the config. You can use that as a template to make any number of them that post any number of RSS feeds from any accounts you want to create. You should probably create a monero news bot account for it, and I’d do separate bots for lemmy updates, monero releases, etc. The accounts dont have to be mod or admin, they just have to be able to post.
You’re about to see some testing going on later today from this account. That’s me testing this thing.
Got it, very cool. Thanks for working on this :)
Do you happen to know the API endpoint for logging in? I can’t for the life of me find it. The docs say
https://instance.TLD/api/v3/user/login?username_or_email=<username>&password=<password>but/logingoes nowhere, at least for monero.town.I’m also about to post after I get login working so if you know the format of that query string you can toss that in too, save me some time fumbling with the lemmy docs.
From someone on matrix: It’s a POST endpoint The response is a jwt and a few flags. Well you have to post and the body is json with the attribute rather than GET request params