DelightOne

Why is ChatGPT allowed to do it and not Google?

5 commands that when you forget them or when they go wrong you have to manually fix. And where when you automate them you realize on your laptop that something went wrong and you have to go back and fix it, possibly losing hours depending on where your other computers are.

Who would want that, possibly over many repos? Git isn't even working well with large files to be synced. Think about git submodules. So much can and does go wrong because Git is not designed to sync that way. Not worth the hassle for most people.

Why can't UBlock Origin do that?

Of course it would be nice if every app can load up its own untrusted eBPF code and for the kernel to not be compromised. But why such high standards, where else is that the standard to go for? Seems perfect is the enemy of good.

> to be secure against actively hostile code

Was that a requirement for the predecessor of eBPF: Custom kernel modules?

~~Doesn't support Safari.~~

edit: Nevermind Safari works. 1Blocker blocks comments with the "Block Comments" ruleset. Usually it is supposed to hide comments where they are not the primary focus. So some rule should probably be adapted for Lemmy instances to work.

edit2: Reported it to 1Blocker.

How can that happen and how do you avoid that happen without ones' own knowledge?

Lemmy comments are broken on Safari - they do not render.

Is there a Meta Review for Glassdoor like for Amazon? Something that records how many reviews were removed.

A browser with features not broken by design? Scary.

The body detecting and removing them would be cooler. I wonder whether any mutation anywhere exists that does that.

How is it supposed to cool anyway when there's less and less ice storing the chill? I mean.. where is the coldness supposed to come from.

And some much better.

But.. what if it asks to allow tracking based on your internet provider? Then the provider delivers who you are automatically instead of anything you control.

Why don't they just ask songs some of you once heard before using ur song history?

I usually add a line with a plain "todo" to break the build and afterwards a three-line comment describing what is supposed to change. At the end of the change I remove the todo-line and move the three-line comment to the now-better location as documentation for why that code there is the way it is.

When I don't have such comments, its usually back to the collection of design documents thinking through the next feature.

> From the script it appears that GPT4 is fully 'aware' that the FTP server is not real

Is "this word fits here" now synonymous to "fully aware"?

How do you know it doesn't use 2023 data just because you tell it to pretend its 2021?

When I do not know how to program something, I get a couple of options. Often better than Google.

Something like that. Especially when the Chatbot then corrects the small usual mistakes it already knows by itself (as ChatGPT can).

Those can be answered by ChatGPT. Only question is where to integrate it into peoples' workflows. Maybe into the post-creation interface? Maybe into the SO question-creation dialog.

Right, I am talking about Chrome. You seem to be talking about something else.

When that walled garden relies on 3rd-party tools and does not give them enough power to do their job well.

Except that not being able to block all ads potentially containing viruses makes THAT walled garden unsafe by design.

Universities still require students to go through their own, potentially worse, material.

To clarify: I am proposing to use the old archival method for already-existing releases, for example by passing in the necessary arguments to git archive forever. Releases without previous archival or created after some point in time in the future call git archive with the new arguments. No substantially more storage should be necessary.

Once the accompanying gzip-version is sufficiently old or unsafe, breaking very old releases does not matter anymore, making it a seamless transition.

Can't Github just keep the old archive as it is for the already-existing releases and use the new format for new releases? Over time old releases phase out and the advantage of the new format is completely in effect. You can even use a time-based cut-off date if you somehow want to get it in sync.

That's what you would expect from the App Store as well, since why change a dynamic library when the code-controlling developer can just build a new version with his own code when the developer wants to update the app.

Injecting new (the nature of not being available on app-submission) framework versions on the developers' behalf would be scary, since these versions weren't tested with the app because the versions did not exist before. As you said, ABI compat is impossible when no one cares about that much.

I am talking about apps on the iPhone where Apple does not have access to developers' source code, right? We might be talking about different situations.

So.. how do you rebuild apps without having access to their source code?