siwatanejo
siwatanejo on Hacker News
Did Omarchy patch it? Anyone knows? (Not that I'm using it now, but I'm interested.)
It seems it's not a convertible anymore? Which means it shouldn't be called a Roadster.
Of course? I never ever upgrade any software unless I'm facing a bug or I want a new feature from the new release. Otherwise it's just taking risk for almost nothing in return.
> Many humans and animals are pretty dumb, yet they are sentient. AI is intelligent, but non-sentient (hopefully!).
Are you claiming that GPT6 is smarter than my dog? Last I checked, at least my dog can play with a ball, I haven't seen any AI playing and enjoying itself.
> Just last weekend I used it to do PDF editing which previously would have required me to download really shady software online to do.
Agreed on the shady software (or shitty online website that asks you for a payment after you're done editing), however, wouldn't the best PDF edition approaches involve WYSIWYG style edition? I'm guessing you didn't get that with Pi.
You seem to not have understood my previous message at all.
You said I'm anti-crypto, then I linked you to a msg I wrote in the past advocating for L402 (which is a Lightning-based protocol).
I was just telling you that you're wrong. I'm a big believer that Lightning is the only way to solve micropayments.
Now get your conspiracy theories somewhere else please.
> spec expressly forbids relays from forwarding messages to each other.
And how do you exactly envision enforcement? Ohhhh, you copied some bits, you going to jail!!
> no lighting payments
Nah, you didn't understand it. Lightning is a layer-2 protocol on top of bitcoin. Nostr is the so-called layer-3. Good luck trying to build Nostr without Lightning.
For me the reason why this is a big deal is because, before there was any Motorola upcoming Graphene-compatible model, most people that might be installing Graphene would not trust Google with their phone software, to then go ahead and install Graphene in Google's hardware! A bit of a contradiction there.
They never had a bitcoin payment rail, and the "crypto" one only accept(ed) USDC because Stripe accepts USDC.
So, are you saying that skills are not such a good tool for agents to learn, they still need tool-trial-and-error dance after injecting them? (I'm assuming each tool comes with its own skill.)
Yeah and it's fucking ugly and unreadable, it shouldn't be allowed.
> You aren't really contributing anything except funding to Anthropic/oai/MS/etc if you're sending genAI content.
Why people keep saying that I'm advocating for AI use? I'm not happy with the decision of Ladybird maintainers, but that doesn't mean I'm willing to spam them with AI slop.
I know, but opensource was not just about freedoms, it was about community.
But opensource has always been about community. This way it becomes "source-open", even if you could make changes to it and run those changes yourself, the latter doesn't sound "opensourcy" to me.
Exactly! It's not opensource anymore: it's fork-or-transparent source.
Don't put words in my ~mouth~ (keyboard) that I didn't ~say~ (type), I'm not saying I want my contributions to be accepted on equal footing even if they are generated by AI. What I'm saying is that solving this problem this way is going to make opensource much worse. We need a better way, and I'm not sure which is the better way, sorry.
I don't know about you, but as for me, when I contribute to opensource it's because I find some improvement that makes the project better because it probably polishes some rough edge around a kind-of particular use case (that maybe few people face, but still, it makes the project better for them; it amplifies the range of usecases that it can span to). If everybody does the same with their small improvements, the project becomes better for everyone, but none of the contributors of these small changes would have time to embark on maintaining a fork. Mantaining a fork is hard work, not only because software breaks over time (dependencies going obsolete or insecure, builds stop working because of old toolkits), but also because not pulling the latest changes from master would mean that your fork gets stagnated (and thus not worth to run it).
what rewrite? I thought it would switch to Rust but I still see it to be C++
While I understand the motivation for this change, I have to highlight something: GitHub's slogan 'social coding' is becoming more and more true these days. Now opensource will become a thing that only "influential" people can contribute to. We're back to nepotism, not meritocracy. Down hill we go.
IMO OCaml is mind-bending (e.g. go figure out the 'in' keyword, I still don't understand it), F# is much easier/simpler.
Haha, it is actually my least favorite statically typed lang for this very reason.