Those rights are only with the original purchaser of the coin. (at least in countries like the US and England)

If the seller of the rights reneges and a purchaser in the secondary market sues the seller will simply demur claiming that there is no contract between the seller and the owner of the coin and that therefore the owner of the coin has no standing to sue. This is covered in This video on the problems with NFTs

Hmm, just thinking about this, AI could do some investigative reporting.

Feed an AI bot much of the video feeds of London and have it describe anomalies.

I don't know what percentage of London's surveillance state cameras have their feed accessible, but it could probably report car accidents and street crimes. It might even be able to do public interest stories about new food trucks and businesses.

It would be interesting to see if it could verify quarterly reports of publicly traded companies. An AI could probably do a lot of the summarization of anomalies of quarterly filings at the minimum and also generate the vapid fluff that the financial press puts out about how the market is reacting to an earnings report.

Based on how Ronald Reagan announced Baseball games an AI could probably do the same in real time from the stat sheet as he was announcing the games from just what was coming over the wire service, which was mostly just the stats.

Unfortunately, the spammers slowly realized that dmoz was an excellent place to place spam.

The IRS already has all of your W2s and all transactions for the past year of over $10,000.

They could ask for the social security numbers of your dependents and then fill everything out for you to review.

In this early version, your options could be either clicking the file button or rejecting and filing the traditional way.

Millions could file their taxes in under a minute

• Create lots of useful open source libraries/wordpress plugins/other free things that the next version is automatically pushed to the users.
• Provide excellent support and gather lots of users.
• Burn out and sell your code, repos, and everything else to malware authors.
• Count profits.
• Give interviews and possibly sell your story.

This is much more profitable than trying to just ship malware.

With Python a requirements.txt file that has pinned versions at least has the outdated libraries that were built with the exact version that the developer used.

This is trading one set of problems for another set of problems.

A bigger problem that impacts more people is that pinned dependencies mean that the code statistically, is almost certainly going to depend on a library with a known vulnerability that has been patched, and if you don't have a method for rebuilding the app with current dependencies you'll wind up trying to find out where you have copies of the vulnerable library and how you are going to update it and retest the application and which other dependencies you are going to have to update and how you are going to have to modify the code to work with the newer non-vulnerable libraries.

The most basic of test suites in an environment with basic anomaly detection would prevent this code from making out of the QA process (which if you have millions of people running your crypto miner during their QA job that is flagged, could still be profitable if short runs of the miner are useful)

Most simple solutions fail when dealing with the reality of modern software development. I've been responsible for dozens of software projects that had over a thousand dependencies. There are solutions, but none of them are magical.

Amazon runs at a scale that they have problems that other places don't have.

Take replacing dead drives in servers. For most companies, this is a relatively rare event that you just deal with as a drive fails. You take a cart and a new drive, go to the computer, pull out the old drive, and swap in the new drive.

At Amazon, there are so many computers, that they have an expected value of drives failing this hour that is far greater than 10. At this point, you start having the problem of what is the most efficient way to swap dead drives with new drives so that: a there are as few dead drives as possible in production at any given time, and b that people swapping drives spend as much time swapping drives and as little time as possible traveling between computers to swap drives.

You get to work on problems and equipment at a scale that you just aren't going to see outside of one of the FAANG companies.

That said, working at a company that does stack ranking seems like a great way to have a huge amount of things that nobody really knows how they work and that every new project is a bit of a gamble. Plus, Amazon's business practices turn many people off.

Although I'm unclear what about this patent is different from what was done 20 years earlier.

I'm not real clear that this isn't a black eye for Apple's legal team.

not randomly firing people.

And it was clear that a chatbot was the better move.

I haven't looked at the code in years, but the last time I did, storing the codes meant that the merchant was responsible for any fraudulent charges in the event of a data breach. I've mercifully not had to store credit card data for a few years now. Back then it wasn't strictly prohibited, just a really bad idea from a risk management perspective.