Tag: open-source
Open-source MLOps vendor aims to give users a ‘sneak peak’ into AI deployments
An open-source ChatGPT rival was just launched by the Stable Diffusion team
Stability AI announces new open-source large language model
Stability AI, the company behind the AI-powered Stable Diffusion image generator, has released a suite of open-source large language models (LLMs) collectively called StableLM. In a post shared on Wednesday, the company announced that its models are now available for developers to use and adapt on GitHub.
Like its ChatGPT rival, StableLM is designed to efficiently generate text and code. It’s trained on a larger version of the open-source dataset known as the Pile, which encompasses information from a range of sources, including Wikipedia, Stack Exchange, and PubMed. Stability AI says StableLM models are currently available between 3 billion and 7 billion parameters, with 15 to 65 billion parameter models arriving later.
Report finds 82% of open-source software components ‘inherently risky’
With a wave of new LLMs, open-source AI is having a moment — and a red-hot debate
Anthropic quietly expands access to Claude ‘Private Alpha’ at open-source event in San Francisco
Hugging Face hosts ‘Woodstock of AI,’ emerges as leading voice for open-source AI development
Twitter takes its algorithm ‘open-source,’ as Elon Musk promised
Twitter has released the code that chooses which tweets show up on your timeline to GitHub and has put out a blog post explaining the decision. It breaks down what the algorithm looks at when determining which tweets to feature in the For You timeline and how it ranks and filters them.
According to Twitter’s blog post, “the recommendation pipeline is made up of three main stages.” First, it gathers “the best Tweets from different recommendation sources,” then it ranks those tweets with “a machine learning model.” Lastly, it filters out tweets from people you’ve blocked, tweets you’ve already seen, or tweets that are not safe for work, before putting them on your timeline.
The post also further explains each step of the process. For…
OpenAI Admits ChatGPT Leaked Some Payment Data, Blames Open-Source Bug
“Upon deeper investigation, we also discovered that the same bug may have caused the unintentional visibility of payment-related information of 1.2% of the ChatGPT Plus subscribers who were active during a specific nine-hour window.”
In the hours before we took ChatGPT offline on Monday, it was possible for some users to see another active user’s first and last name, email address, payment address, the last four digits (only) of a credit card number, and credit card expiration date. Full credit card numbers were not exposed at any time.
We believe the number of users whose data was actually revealed to someone else is extremely low. To access this information, a ChatGPT Plus subscriber would have needed to do one of the following:
– Open a subscription confirmation email sent on Monday, March 20, between 1 a.m. and 10 a.m. Pacific time. Due to the bug, some subscription confirmation emails generated during that window were sent to the wrong users. These emails contained the last four digits of another user’s credit card number, but full credit card numbers did not appear. It’s possible that a small number of subscription confirmation emails might have been incorrectly addressed prior to March 20, although we have not confirmed any instances of this.
– In ChatGPT, click on “My account,” then “Manage my subscription” between 1 a.m. and 10 a.m. Pacific time on Monday, March 20. During this window, another active ChatGPT Plus user’s first and last name, email address, payment address, the last four digits (only) of a credit card number, and credit card expiration date might have been visible. It’s possible that this also could have occurred prior to March 20, although we have not confirmed any instances of this.
We have reached out to notify affected users that their payment information may have been exposed. We are confident that there is no ongoing risk to users’ data. Everyone at OpenAI is committed to protecting our users’ privacy and keeping their data safe. It’s a responsibility we take incredibly seriously. Unfortunately, this week we fell short of that commitment, and of our users’ expectations. We apologize again to our users and to the entire ChatGPT community and will work diligently to rebuild trust.
The bug was discovered in the Redis client open-source library, redis-py. As soon as we identified the bug, we reached out to the Redis maintainers with a patch to resolve the issue.
“The bug is now patched. We were able to restore both the ChatGPT service and, later, its chat history feature, with the exception of a few hours of history.”
Read more of this story at Slashdot.