faserx

OK I see your point, the problem is more being off-topic rather than the LLM programming itself. And that's correct, we are strict people, after all.

/r/horsecarriage bans all discussion of cars

/r/assembly bans all discussion of 4GL

LLM programming isn't going away by not talking about it. It's time to move on, and eventually considering farming.

Starting from the original codebase I'm working on a RUST version, just for fun.

Unless it is a different subscription, I've never seen such information in the worldcheck database.

so what's the big deal? (barely) every bank in the world has access to the world check database and there is no "secret data" in it. Just a collection of public records...

The cloud services of the Smart Home/Care products must therefore be discontinued as of 29 March 2024. Continuation is not possible under insolvency law. As a result, the apps for the Smart Home/Care products and the networked sensors and devices will no longer be usable. If you have booked camera service packages, these will also end on 29 March 2024 at the latest. With regard to any existing contractual relationships, non-fulfilment is selected.

...

Unfortunately, it is not possible to return the devices. Instead, we recommend that you dispose of the devices in an environmentally friendly manner at a recycling centre near you.

You could do better with the joins, imho less readable than the equivalent in sql.

what a scam! if you regenerate without changing anyhting it does not rezz anything but a blurry nothing...

NFT only exists inside a specific smart contract operated by someone within some specific rules implemented in the contract. If the smart contract is seriously built, in order to "control" the NFT cloned as an "exact" copy of it, the copier has to control an exact "copy" of the smart contract where the NFT resides. The only way I see to achieve this is to know the private key of the owner of the original smartcontract or of someone who has the power to operate it. It follows that if they control the "exact" copy of the smart contract in an "cloned" blockchain (forked or crafted) they also control the smart contract in the original one. At that point the problem wouldn't be the "copies" but the "original" NFT. If they instead craft a copy without crafting the original smart contract, that would be easily spotted. Your nyan cat besides being unique, has also an "origin", the smart contract, and that can be easily being verified. The same applies if someone creates "another" nyan cat inside the same blockchain. That would reside on some other smart contract and easily spotted as a copy.