>For example, to build shared threads like OpenAI’s, you might end up creating a new collection, a caching layer, or an index just to connect messages that logically belong together.
Which messages belongs together depends on the context and when you discover that the fancy thread store you built your app around can't return a list of MY messages without a full sequential scan of every single thread you'll wish you could solve it with an index.
Hi - dont know how to answer you directly - but yes the store has an index already, at a timed sequence for example. And a key called thread:thread_meta.
This statement is in no way saying you dont need an index, its simply saying, this is the variety of ways people might end up choosing.
Which is just 1 example of the type of work - a thread model & compatible store can fix and fix more efficiently.
In no way fancy too - this is just redis with a disc and some steps imo.
Parkytowers is site about repurposing thin clients of various kinds, it's a goldmine for finding out power consumption, Linux compatibility, possible hardware mods, etc: https://www.parkytowers.me.uk/thin/hware/hardware.shtml
Around 20 years ago when I was trying to decide on what database to use my requirement were that it should store data reliably. I learned that MySQL in contrast to PostgreSQL:
1. wasn't ACID
2. didn't have foreign key constraints
3. could loose/corrupt committed data (no WAL)
Despite me not knowing much about databases it seemed like an obvious choice.
Hell, 10 years ago (in a multi database project) I got bit by MySQL not supporting check constraints, but returning successfully when I ran the create check constraint statements.
It finally supports them, which is nice. It doesn't support deferred checks to the commit, like postgres, but are otherwise good. I've appreciated using it to enforce json schema at the db level
My problem with blockchains is that they AREN'T decentralized. If controlling a blockchain becomes valuable enough then it's a matter of time before someone will figure out how to profit from it and invest the required resources.
Decentralized in my mind means there is not one single source of truth.
Do you need all of that for a software run on a Raspberry Pi (as article suggests) or similar embedded devices? I think just one application binary should be enough.
The main reason I thought Russia's invasion of Ukraine wouldn't cross the line of being a convincing threat was how little off ramps it left everyone involved. It's going to be hard to come up with an off ramp for Putin that is also remotely acceptable to the Ukrainian people.
>President Volodymyr Zelensky might be prepared to formally renounce his pursuit of NATO membership
If Ukrainians feel they have convincingly defended themselves against Russia that might be possible. However, in 1994 Russia signed a Treaty promising not to use military force or economic coercion against Ukraine as a condition for Ukraine giving up it's nukes. With that and the last decade in mind Ukraine is unlikely to consider a signed paper sufficient safety. Outside of NATO's nuclear umbrella they'll need a military defense strong enough to defend against Russia on it's own.
>The difficulty comes with compromises that are not fair. Why should Ukraine not seek EU or NATO membership?
Ukrainians were divided between wanting to align more with EU or more with Russia but by trying to force Ukraine not to join EU through indiscriminate bombing Putin turned a bureaucratic process into an act of defiance against tyranny. Staying out of NATO is one thing but I don't think it's going to be politically possible to tell Ukraine they can't join EU.
It's not, the editor banning words is what's lazy. Banning certain words is a symbolic action that makes it harder to use precise language.
If their journalists are lazy how would banning words fix that? If they stop telling journalists what words they can and can't use then maybe they could attract better talent.
I think any new journalist would appreciate a list of things that editors will find unacceptable complete with an explanation why it's unacceptable. It's better than getting your article's returned to you for being too vague.
They aren't addressing laziness, they're explaining what the standards are. And I don't think getting rid of those standards will attract better talent.
Yes you can build more wind and solar but people need power also during the dark and sometimes windless winter months. Storing enough power isn't currently feasible so it's basically either coal, gas or nuclear.
Which messages belongs together depends on the context and when you discover that the fancy thread store you built your app around can't return a list of MY messages without a full sequential scan of every single thread you'll wish you could solve it with an index.