So its all perplexed situation to make any conclusions.

Within minutes of talk and creating imaginary scenario, any one is able to jail break an AI model and get recipes to make dangerous stuff. The question is why would this companies train the LLM on such dangerous data altogether? And to whom are they providing such extra services , clearly if you have trained it and is already serving it ?

Selecting the dataset was clearly their job and all terrible outcomes can simply be avoided at the training itself.

Comments URL: https://news.ycombinator.com/item?id=39775004

Points: 1

# Comments: 1

Suppose we had this AI at the dawn of internet, we would have google using this tech to search internet back then. We would have saved countless hours of search to fix a bug.

AI is having an Einstein in our pocket. Any one who had to develop/research on any topic, he has an Einstein level assistance ready to help you out. We are just at the dawn of the sci-fi era we always have imagined for. And AI will be our companion in this fast changing world: "Jarvis explain me how that thing works" , and you get somewhat of an idea about any new or complex subject, which otherwise would have taken days to comprehend.

Get ready to experience the power of a seamless document and attachment management system, just like CouchDB, but with the added convenience of being accessible through a familiar REST API.

Imagine effortlessly retrieving your docs and attachments with a simple URL:

But that's not all! This library takes things to the next level with its cutting-edge partial content streaming capabilities. Lazy Cloud Attachments ensure that your browser only downloads the attachments you need, when you need them, optimizing performance and efficiency.

Built from the ground up using pure, vanilla JavaScript, this library is a testament to my commitment to simplicity and robustness.

Don't just take my word for it – head over to the GitHub repo and explore the usage examples and working demos for yourself! Get ready to revolutionize your web development experience.

Comments URL: https://news.ycombinator.com/item?id=39651344

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=39519643

Points: 1

# Comments: 0

government should release there own open source safety sdk, which others can simply include in there code, to adhere to minimum requirements.

otherwise this seems to me like Innovation killer bill, by eliminating small players out of equation.

DB should only contain key value pairs. Don't store big blobs as values in them. Store meta info(like network path, size, name...) for these blobs in values. Blobs sould be on some Network drives.

This way you can scale these two things independently. The client can locally store this meta info and won't need it again and again.

You can have some sort of analytics on these blob access and than replicate more copies accordingly of often accessed blobs, to get more read through out.

Use of "range" http headers to stream data can also be helpfull.

Zero copy is another concept to get the best through put. Familiarize yourself with it.

The easy and best solution is to store these blobs on some properity media server solution. As they do handle most of these optimization. Your database must only deliver meta data, which do contains cloud path to these blobs. it then becomes headache for these media server to scale your big blobs.

Introducing `bloc-them`,a tiny (but mighty) JS UI library. Its based on `Business Logic Components` design pattern and hence the name 'bloc-them`.

A moderate JS developer can learn it in very short span of time: I belive it should be in 15 Minutes up and running.

Ther are only two Classes in whole framework: `Bloc` and `ListenerWidget`.

`Bloc` publishes new states and `ListenerWidget` react to such states. The complete 15 Minute tutorial is on the GitHub readMe.

Comments URL: https://news.ycombinator.com/item?id=36940678

Points: 2

# Comments: 0