G'day all! Just thought I'd chuck up this random thread for a bit of a yarn. You know, sometimes it's nice to have a chinwag about anything and everything – could be your latest DIY project, a recipe you're stoked about, or even just how your day's been. It's all about sharing the good vibes and having a fair dinkum chat. So, what's the goss? Jump on in and let's have a good old chit-chat, like a bunch of mates sitting 'round the table. Cheers!
There's an extra step with login now
lemmyClient.setHeaders({ Authorization: Bearer ${loginRes.jwt!} }); need to set this 'Bearer' header with the login token. I'll see if I can come up with a patch for the bot code used by Brisbane, Sydney and Canberra to work with 0.19.x. It's annoying because the lemmy-js-client documentation doesn't point this out the in the example. I found the solution by looking at lemmy-bot
Thanks! For what it's worth I added a new issue to the lemmy-post-bot repo to request an update for Lemmy >=0.19. I'm not expecting an update though as @[email protected] hasn't been active for a while either here or there (afaik). If you're able to get a patch out do you think you'd be up for creating and maintaining a fork?
I'll have a look into it later today. My hope is that a pull request should get their attention if they are active on GitHub (or email) and have the time to review, merge and update the version they're running.
We're back!
How?
There's an extra step with login now
lemmyClient.setHeaders({ Authorization:
Bearer ${loginRes.jwt!}});
need to set this 'Bearer' header with the login token. I'll see if I can come up with a patch for the bot code used by Brisbane, Sydney and Canberra to work with 0.19.x. It's annoying because the lemmy-js-client documentation doesn't point this out the in the example. I found the solution by looking at lemmy-botThanks! For what it's worth I added a new issue to the lemmy-post-bot repo to request an update for Lemmy >=0.19. I'm not expecting an update though as @[email protected] hasn't been active for a while either here or there (afaik). If you're able to get a patch out do you think you'd be up for creating and maintaining a fork?
Sorry for the delay (had a few things going on at this end). I've updated the version and added a release. Cheers for the PR.
Woah @[email protected] is back! Thanks for merging @[email protected]'s pr. Hope everything is well in your part of the world.
Just on an intense project implementing a kubernetes hosted application at scale... and had some health issues come up. All sorted now.
I'm going to add some unit tests to this project and some alerts.... and possibly a second maintainer so this doesn't happen again.
Sorry for the delay!
Done. Waiting on the pr, otherwise can use fork:
I'll have a look into it later today. My hope is that a pull request should get their attention if they are active on GitHub (or email) and have the time to review, merge and update the version they're running.