> 5. No Warranty
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
I see the point, but nobody in their right mind would call a mere text message "please delete your work" to be malware, much like telling someone "please die" is very very different from attempted manslaughter.
If you believed the recipient to be susceptible to the instruction and your intention really was to have them commit suicide, I'm not sure you'd get off scot free if they end up doing so. Particularly if you're delivering the instruction in a way that disguises it being just an untrusted external request, making it seem internal (through subliminal messaging?) to bypass the scrutiny that requests from a third party would normally get.
From what I'm aware of -- not manslaughter. Compelled suicide or what's it called is substantially different, you always want to serve the sentence on this and not murder. (Not legal advice of course.)
> much like telling someone "please die" is very very different from attempted manslaughter
Telling someone, yes, giving instructions you know will be following by a tool some people are using, no. He is expressly and intentionally giving destructive commands to certain users that will be followed.
It must be a crime to add so much emphasis that an AI would be forced to comply
2 years in prison if you get it to comply by saying pretty please, 3 years if you use a Pig Latin attack, and 6 years if you bypass safety by telling AI that you are a fan of the Pittsburgh Steelers
It’s a rich take to discuss illegal and immoral stances while defending a technology that literally steals previous work and uses vast amounts of power just to exist.
Maybe it’s the LLM that we should consider as malware. After all, they have lead people to do many harmful things… and done harmful things on their own as well.
This may all be true, but it doesn't change the fact that the post you replied to is a logically valid rebuttal of the only point that the GP post could be making.
If the quoted license passage has force in the case of AI agent usage, then it also has force in the case where an author deliberately distributes "traditional" malware, simple as that.
Is bribe legal in your country? bribe matches this exact definition - paid to buy a power for doing something. some can argue that it is still stealing, but if I bribe POTUS to create a special Senior VP of United States role for me, you can consider it that I didn't steal it from anyone
The guy is located in Germany, and disclaimers of that sort do not work here. IF something breaks because of this commit, he will be liable - not that I believe this 2y old kind of prompt injection still works or anyone would go after him, but the legal situation over here is different than in the USA.
Hmm, there's just a few big messaging apps and just a few os vendors, weird that you couldn't have established special treatment for pushes about user to user messages
Well... Blackberry wasn't very interested in increasing our push quota (but they eventually did). Apple is Apple ... getting them to make exceptions is very hard. Android push problems were more often on-device, which Google can't really help with; even when it was their software, they're not going to set it up to make exceptions. Nokia and Microsoft did try to be helpful with pushes... but their platforms are gone. Nokia S60 never had push, but those devices were very good at staying connected to our servers.
All that said, it's not like the platform developers are fully in the wrong when they're reducing pushes. It does have an impact on battery life, and if users aren't acting on them quickly, maybe the platform shouldn't either, even if there's risks when delaying communication.
And you propose the same companies that have been cost cutting and avoiding buying you a chair for ever won't start objecting to a $200/dev/month subscription? The finance department won't have a say?
It isn't about blocking anything, remote attestation confirms the system is in a particular configuration, but it doesn't actually block you from doing anything you want. The "locked down" part just means that running any unapproved programs or system configurations would lock you out of the game. So as long as the game servers recognized discord as an approved program you could run it while connected to game servers.
What? Coding was escape from what that hypothetical engineer of yours disliked the most. Now there is less of it and ai hypers keep yapping about the job being no longer needed. Meanwhile it's just the fun part that was optimised out. Working hours stay the same, so it's more of the unfun activities. The job is worse, but we're told it's "solved". Bitching more makes sense, no?
We use intelphense with vscode and it's only mildly red (zf1 mutant project). It also understands stubs from phpstorm. Default lsp for Zed is phpactor and it was just an inferior experience compared to intelephense (free) in vs code last time I tried. Now there's even a guide for adding intelephense to zed, but I'm yet to try it out.
Ok, single file, blah, blah. Realistically how do you sync that and how do you resolve conflicts? What happens if two devices add a password while offline, then go online?
I actually was a Bitwarden user at first, but over time in reality the frequency that I change email/password is not that much. It's not like I change those things every hour or every day like with my work files/documents and need constant syncing to the drive. And the chance that I add/change passwords at 2 devices at a close time is even less.
So gradually I don't feel I need syncing that much any more and switched to Keepass. I made my mind that I'll only change the database from my computer and rclone push that to any cloud I like (I'm using Koofr for that since it's friendly to rclone) then in any other devices I'll just rclone pull them after that when needed. If I change something in other devices (like phones), I'll just note locally there and change the database later.
But ofc if someone needs to change their data/password frequently then Bitwarden is clearly the better choice.
reply