I believe it’s 1% for access to the “entire post-open ecosystem”, rather than 1% per project which would be unreasonable. So you could use one or thousands of projects under the Post-open banner, but still pay 1%.
It will take years to develop the post-open ecosystem to be something worth spending that much on.
This really got me, thank you!
I’ve not built anything beyond simple scripts in rust but I’m looking at some of the cosmic codebase to see what I can do.
Literally just bought what I believe to be last generation’s X13 on ebay for half the price of the new one. It’s been great so far, especially with the power efficiency of Ryzen CPUs. My one complaint is the soldered RAM, which judging by the new lineup is getting phased out, thankfully.
I’ve been programming for too long, my brain just autocorrected the typo so initially didn’t get the joke…
Again, this existed before AI. Typo squatting, supply chain attacks, automated package uploads, CI pipeline infection, they’re all known attack vectors. That’s not to say this isn’t a concern, just that it’s a known risk and the addition of “AI” doesn’t, to my eyes, increase that risk. If your SSH keys don’t require a password, you have taken the decision to make those keys less secure but more convenient to use. That’s pretty much always the tradeoff in security.
The risk here is slightly overblown or misrepresented. Just because a fork exists doesn’t mean that anyone has even read it, let alone run it on their system. For this to be a real threat they would have to publish packages with identical or similar names (ie typo-squatting) to public package repositories which this article didn’t have any information on but which is a known problem long before AI. The level of obfuscation and number of repos affected is impressive but ultimately unlikely to have widespread impact to anyone besides GitHub.
Personally I rename them to something meaningful and they get merged if there are no other references. PayPal is especially bad for completely meaningless rubbish in the payee field and they tend to be ad-hoc purchases so I don’t fiddle with them much. The category is the most relevant bit for me.
I think for most people it’s whatever you got used to first. I agree the hatred the GUIs get is overblown. I would always recommend people learn the command line but if you want to use a GUI, go for it, doesn’t affect me unless your commits are bad, in which case the CLI wouldn’t have helped anyway.
I like it and have been using it for something like 6 months. I had an issue where I really liked the application and how simple it was but I didn’t really want to “budget”, just keep an eye on where my money was going. That was fine, just keep zero-ing the numbers every month, slightly tedious though. Now they’ve got a “report” style behind an experimental flag and that’s made it pretty perfect for me.
I set up some family members with the electron app after they had spent 3 days to do in a spreadsheet what I had done in 3 hours in actual. There was resistance initially due to sunk cost fallacy but now they’re loving it.
Other options like ynab and firefly were just too bloated and complex for our simple use case.
The self-contained electron app works better for most people I think.