![Ben Young Profile](https://pbs.twimg.com/profile_images/1862949648253538304/nLm2Cai9_x96.jpg)
Ben Young
@benyoungnz
Followers
812
Following
2K
Statuses
4K
Field CTO, APJ @Veeam, obsessed with showcasing the art of the possible with tech. #Veeam Vanguard x5
Christchurch, New Zealand
Joined July 2010
Not sure we have a choice at this point. Mega dissatisfaction @seeedstudio I’ve purchased from you before and you were great. To list something as preorder with a shipping date of 7th of Jan only to find out after no communication for weeks that it’s going to be the best part of a 4 month wait is not acceptable
0
0
0
@anthonyspiteri @seeedstudio I have also posted in your discord @seeedstudio and logged a support ticket but no responses. Cmon.
0
0
1
On the DeepSeek data exposure. This incident prompts a deeper reflection on the delicate balance between innovation and security. While we can't definitively pinpoint the cause of DeepSeek's database exposure, it's plausible that the rush to demonstrate the capabilities of their groundbreaking AI models may have inadvertently led to security oversights. Perhaps in the excitement of showcasing their technology, certain security measures were bypassed or postponed in pursuit of a quick and impactful Proof of Concept (POC). This is not to diminish DeepSeek's achievement or to cast blame. Rather, it's an opportunity to examine the potential pitfalls of prioritising speed over security, especially in the context of emerging technologies. The pressure to innovate and capture market share can sometimes overshadow the crucial need for robust security practices. DeepSeek's experience serves as a valuable lesson for the entire technology community, emphasising the importance of integrating security considerations into every stage of development, even in the early phases of POCs. It's a call to ensure that the pursuit of groundbreaking technology doesn't come at the expense of safeguarding sensitive data and maintaining user trust.
0
0
1