Yeah that's a fair way to look at it

You're welcome, feel free to ask any questions once you get there

You can dislike the statement all you want, but they literally do not have a way to know things. They provide a convincing illusion of knowledge through statistical likelihood of the next token occurring, but they have no internal mechanism for looking up information.

They have no fact repositories to rely on.

They do not possess the ability to know what is and is not correct.

They cannot check documentation or verify that a function or library or API endpoint exists, even though they will confidently create calls to them.

They are statistical models, calculating how likely the next token is based on transformations in a many-dimensional space in which the relationships between existing tokens are treated as vectors in a process for determining the next token.

They have their uses, but relying on them for factual information (which includes knowledge of apis and libraries) is a bad idea. They are just as likely to provide realistic answers as they are to make up fake answers and present them as real.

They are good for inspiration or a jumping off point, but should always be fact checked and validated.

They're fantastic at transforming data from one format to another, or extracting data from natural language written information. I'm even using one in a project to guess at filling in a form based on an incoming customer email.

Indeed. I stopped using it altogether a couple months ago.

I can't tell if you're agreeing with me, disagreeing with me, or suggesting some alternative

Ok, sure. I recognize that not everyone has a computer. And sure, an F-droid release would be really helpful for those people, if "build it yourself" was the only way to get the app.

But ... It's not like the app is inaccessible. It's on the play store. You can install it.

My main frustration is the outright demand for the project creator to "Just release it on F-Droid" - Something that requires the creator to get familiar with F-droid and do the extra leg-work to release it there. But ... It's an open source app, created for free by someone who wanted to create it. They owe you nothing. Not even "good distribution".

It's almost certainly a file permission error; Composer's auto loader (the require statement) just scans the vendor library directories and populates the namespace, it doesn't have a list to check answer l against and doesn't load the classes up front. As such, if the file for a class isn't accessible by the permissions, it will not be loaded into the namespace by the auto loader.

PHP also doesn't validate its usestatements, as they are basically just aliases that are resolved at the moment the import is used.

Then, when it comes time to attempt to instantiate the class, PHP discovers there's no class by that name and errors out.

You just need to make sure the Zabbix user can access all the files in vendor, probably by deleting it and running the composer install as that user.

Supabase is more than just managed databases; It looks like it's a bunch of ancillary services around databases as well

I run my NAS on TrueNAS, and it just has a built-in solution for taking ZFS snapshots, encrypting them, and shipping them to an S3-compatible storage.

However, for unraid, I think your easiest thing will be to use the rclone plugin

Well, it's terrible at factual things and counting, and even when it comes to writing code it will often hallucinate APIs and libraries that don't exist - But when given very limited-scope, specific-domain problems with enough detail and direction, I've found it to be fairly competent as a rubber ducky for programming.

So far I've found ChatGPT to be most useful for:

1. Writing SQL. Seriously, it's fantastic at writing SQL if you tell it the relevant schema and what you're trying to achieve.
2. Brainstorming feature flow - Tell it the different parts of a feature, ask for thoughts on how the user should be guided through the process, and it does a decent job of suggesting ideas.
3. Generating alternative names/labels for buttons and such. "In X feature, I have a button that does Y when the user has Z. Currently I have that button labelled 'Start Y', but it feels robotic and impersonal. List 10 suggestions for what such a button could say to be more personal and friendly." and the like. My favorite was a button that was labelled "Map Incoming Data to Job Details". Wound up renaming the whole process to just "Job Ingestion" because it sounded so good.
4. Reformatting data. Give it a data structure and tell it you want that data in some other data structure, and it is really accurate at reformatting it. I don't think I'd trust it with a huge amount of data that way, but for an unimportant one-off it was a nice time savings.

The good old scunthorpe problem

Excellent!