I moved from oh-my-zsh to grml ~10 years ago, and I've enjoyed it - it's got good defaults, is extensible (I've added custom stuff to handle how I manage directories for work things) and the single-file nature of the defaults makes it super straightforward to put it onto a new machine (ie a server) without then necessarily needing to do any extra tweaking
Before I joined Mend to work on Renovate, I wrote https://news.ycombinator.com/item?id=40011111 which goes into some ways I found Renovate better than Dependabot, and it still very much holds true (although I'm a little more biased now!)
Re costs / why giving things away for free - @rarkins (Rhys Arkins, who created Renovate) has worked very hard over the years to give as much good stuff away to the community, and make it more straightforward for folks to run Renovate
The core (Mend Renovate CLI (AGPL-3.0-only)) is free to use and run as you want, and many folks do - it's very flexible and scales well as-is
But if you want things like real-time webhook processing of "rebase this PR" (and/or a few other features) then Mend Renovate Self-Hosted Community (commercial-but-free) Edition is a nice packaging and layer on top of the CLI for that
Running the CLI itself on a schedule against your repos is also absolutely viable as a solution, and we have many users who do that and are super happy with it
I've been doing this for years with my site, and it's brought me a lot of joy that I can go back and search my site for various posts I've made over the last decade across all the platforms I use - I have a more high friction setup, but that's because of my own terrible choices
Have you looked at https://posseparty.com/ as a possible option? Supports integrations with those platforms and more, and "all" it needs is an Atom feed!
Ooh I hadn't seen that. I'm still hung up on character limits - I want to make sure the summary I include isn't truncated with ... and is instead the right length for that particular platform.
I created POSSE Party because I had similar concerns. Truncation and spacing are highly customizable. You can add a posse:post sidecar element containing JSON that formats exact presentation for each platform exactly as you want it. The built-in truncation can be configured at the account level. And how you count characters, naturally, differs by platform, which the app handles pretty well.
my fear is people are going to post issue reports, sometimes good ones that we need to act upon, they get autoclosed, and the submitter either never bothers to re-post or they are so annoyed that they don't re-post.
it would be way better if there was only one way for them to get their content in, in the first place
In our case, we've fortunately not found that's happened - we do end up looking at Issues that are closed in this way, and the majority of cases it's someone who's raised a Discussion and want to bypass the triage so create a new Issue from their comment
(I'm thinking of getting some data and words together to look at how this has helped us over the last ~18 months)
We've been doing this on the Renovate project for years, and it's been hugely useful - we get a lot of reports that users feel to be a bug, but are often misunderstanding or expectations about behaviour that isn't necessarily true.
There are absolutely bugs that get reported - either in functionality or documentation - but by requiring a level of triage in Discussions before promoting them up to Issues is a great way to keep things more actionable for folks wanting to come in and contribute fixes that the maintainers do agree are needing a fix
reply