![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/c47230a8-134c-4dc9-89e8-75c6ea875d36.png)
Yeah, but you do understand, that nuking can’t be a solution?
Yeah, but you do understand, that nuking can’t be a solution?
Tell me you know nothing about nuclear warfare without saying you don’t know nothing about nuclear warfare.
Either that or you really want to see the whole earth in ashes.
The funny thing is, if you point out its mistakes, it often does better on subsequent attempts.
Or it get stuck in an endless loop of two different but wrong solutions.
Me: This is my system, version x. I want to achieve this.
ChatGpt: Here’s the solution.
Me: But this only works with Version y of given system, not x
ChatGpt: <Apology> Try this.
Me: This is using a method that never existed in the framework.
ChatGpt: <Apology> <Gives first solution again>
and no fail safes monitor for example the battery drain on the pump itself… hey this pump is using more battery than it should
Yeah, that was a failure. But wishing a company to be “sued into oblivion” is a tiny little bit overreacting, isn’t it?
Next time it will inject too much or too little insulin and then?
How about to just move on and get yourself a model from a different company, if you don’t trust them anymore instead of assuming stuff.
I hope not.
First: You can’t avoid bugs. You simply can not.
Second: There aren’t that many producers of good insulin pumps and the t:slim is a great device.
You are right. We should name every one of them.
What bothers me is that so many people didn’t see this happening.
Every party that is involved in dismanteling democracy and weakening the EU is on their payroll.
We knew this before.
Ah Pokémon Go, aka we are selling shinies for cash.
It would have print if it was previously declared as function.
Also, js is as dirty as you want it to be. Keywords are indeed not necessary for declaring variables.
Can someone please view the video for me, as I can’t be arsed to watch it. Who won, who lost?
You have to find an extension, that blocks specific javascript functionalities, like accessing the history.
This could achieve it (not tested yet):
https://github.com/polcak/jsrestrictor
BUT: If a site totally relies on it, it could prevent you from accessing some if not all of their content.
Same could be achieved by blocking js per site (via browser settings or an extension). Here it would come down to the same scenario if they don’t provide any non-js fallback.
Also APIs: Those things are just interfaces to interact with programs or (web) services. Say you wrote yourself a nice little program and want to open it up so that other programs would be able to interact with it: You would write an interface for it - to be more specific, an application programming interface (hence API). That’s what is enabling Apps like Sync to readout the lemmy servers or write to it, when you submit a post.
Some of those APIs are open, some restricted (like X or this other site we don’t talk about.).
The thing is, at first I actually, responded with “you are right”. See, humans make errors. Also, this isn’t a competence competition. (At least I hope so.)
Shoot, you are right wrong. They are processes.
Yeah, also each query request was a human beeing. Such an unrealistic comic.
LOL, a little over dramatic, aren’t you?
I dont see the line “3rd party cookie blocking”
I was all hyped until it said the wiki is in fucking discord.