> I do think the law should update and grant some protections to people who produce models
This is what every reasonable person thinks, and because legislators and lawyers generally aren't that great at or keen on designing new frameworks for IP protection, the most likely outcome would be extending the concept of copyrights to models.
They did it for photography, for software programs, and they will do it for AI models.
The issue has since been fixed somehow (after being outstanding for 6 years).
The Django docs gaslights the developer into thinking it's of some SQLite limitations:
"SQLite is meant to be a lightweight database, and thus can’t support a high level of concurrency. OperationalError: database is locked errors indicate that your application is experiencing more concurrency than sqlite can handle in default configuration."
But that's not true, the issue could be reproduced with just two "concurrent" connections given unfortunate timing.
Since I was stubborn enough to not switch to another database (for production loads) and I knew sqlite could handle loads of a couple requests per sec, I'm still salty that Django basically introduced random errors to a service I maintain just because they didn't want to fix the problem (and lied to me in the docs).
Interesting history on that ticket. Closed as "invalid" 7 years ago, reopened 10 months ago, and 6 months ago added as non-default option to git (but not released yet?).
I wonder what the downsides would be in enabling this by default. Would lit engthen the period of the write lock on the DB so this change could be a compatibility problem for existing systems?
If it's write heavy, and you need to use transactions for writes, you're screwed either way. (i.e. don't use sqlite)
If it's not write heavy, but you enabled `ATOMIC_REQUESTS = True` then all your requests will be serialized (which is obviously bad)
If your site does not write often and your reads don't require transactions, using BEGIN IMMEDIATE TRANSACTION is probably fine. Your transactional writes will still be serialized but if they don't happen often it's probably fine for a low/medium-low traffic site.
"If it's write heavy, and you need to use transactions for writes, you're screwed either way. (i.e. don't use sqlite)"
That depends on your definition of "write heavy". Given SQLite's performance I would expect anything below 1,000 writes a second to work just fine even with write locks, given moderately capable hardware.
Just to clear up a possible misunderstanding, the word church in the bible is derived from a word that simply meant assembly, as in an assembly of people. The above poster was referring to the institution of the church, which wasn't formalized till long after the death of the Christ figure.
All you have to do is read Eusebius to find that the church existed long before Constantine, and as a formal structure. You can also read the Early Church Fathers to find that the Bishop of Rome was respected as the leader even before Christianity was legalized.
TBH it might not matter in a normal life for the individual. But (as long as the claims have some truth too it) statistically, it definitely matters.
The "scares" are overwhelming only because you live in a society where things are (slightly) toxic by default, because those things are cheaper and can be engineered to barely pass safety standards.
We can and should change this situation. Hopefully not on the individual level, but at least public awareness is useful.
The "scares" are also overwhelming because some people are extreme in everything, for example the person who swears never to drink from a plastic cup. But it doesn't mean the opposite stance (i.e. drinking from plastic cups is good for you) is true. You can believe plastics are slightly bad for you without overreacting, and acknowledge that if it's feasible it's better to avoid them. Reacting emotionally to extremists isn't what a rational person would be doing.
Right, because hacking into the matrix and tweaking the code there to make security breaches physically impossible is obviously the more robust solution...
Ensuring government employees are following best security practices and not being negligent, and thus not passing the buck to citizens is maybe a little bit more realistic.
I think the problem here is that government departments are not the only entities consuming the data. Private companies also deal with company names too. So at this point it's either:
- somehow ensure all software is bug free (at least when processing company names)
- outlawing things
- just let it happen
The first option isn't that far away from hacking the matrix and making buggy software physically impossible. The second option seems to be better than the third.
This is what every reasonable person thinks, and because legislators and lawyers generally aren't that great at or keen on designing new frameworks for IP protection, the most likely outcome would be extending the concept of copyrights to models.
They did it for photography, for software programs, and they will do it for AI models.
reply