I think the whole point of this was to see if the "agents" could act like a real human and real humans use Gmail much more frequently than sendmail. Sage even commented that they had update their prompt to tell the agents to not send email and not just remove the Gmail component for fear that the agent would just open it's own Gmail (or Y! mail, etc.) account and send mail on it's own.
> Are there really many unsupervised LLMs running around outside of experiments like AI Village?
How would we know? Isn't this like trying to prove a negative? The rise of AI "bots" seems to be a common experience on the Internet. I think we can agree that this is a problem on many social media sites and it seems to be getting worse.
As for being under "human supervision", at what point does the abstraction remove the human from the equation? Sure, when a human runs "exploit.exe" the human is in complete control. When a human tells Alexa to "open the garage door" they are still in control, but it is lessened somewhat through the indirection. When a human schedules a process that runs a problem which tells an agent to "perform random acts of kindness" the human has very little knowledge of what's going on. In the future I can see the human being less and less directly involved and I think that's where the problem lies.
I can equate this to a CEO being ultimately responsible for what their company does. This is the whole reason behind to the Sarbanes-Oxley law(s); you can't declare that you aren't responsible because you didn't know what was going on. Maybe we need something similar for AI "agents".
AWS just renamed their Security Hub service to Security Hub CSPM and then created a new service named Security Hub that is related but completely different than the original service.
And there's AWS S3, and there's AWS Glacier. And there's AWS S3, Glacier storage tier, which isn't Glacier. Which is OK, because Glacier is going away, and you should use S3, Glacier tier. Unless you're already using it, in which case you can still use it. So you still have to know Glacier and Glacier, while both storing your data, aren't technically the same thing.
But if you think that's bad, you haven't seen the name change shenanigans Microsoft pulls in Azure.
I'm pretty excited about this because it's one of the cornerstones of why BambuLabs printers are so easy to use. One of the main issues in the past has been tuning your printer to use a certain type of filament; it has more options than a 1999 JVM. With BL printers and filaments you can just slap it on and the printer is automatically configured to optimal print you object.
Now, I can see why BL would not be excited about this. One reason I purchase so much BL filament is because it's so easy to use. Every time I've gone "off-script" and gotten a reel from another maker I have to do the work of configuring it to get the most out of the filament. It's not super hard, it's just really inconvenient. So, of course BL would like me to continue purchasing their filament and would not want to join this movement.
However, BL doesn't produce all types filaments in all necessary colors for everyone. Once (if) everyone else moves to this standard then BL is out in the dark, getting left behind. Orca slicer can be configured to use this new standard and is also compatible with my A1. I'm planning on my next printer being a BL H2? but if that day comes and all the other printers are supporting the new standard my plans will probably change. I think that it would be in BL's best interest to support the new standard, now and in the future.
BTW: one handy way to use up the remnants of an almost empty roll is to make the printer think that it's a different color. Start printing some utility object (where the color doesn't matter) with the almost empty roll and then have the printer automatically switch to the new roll of the correct color. This works pretty well, but it involves you forceably ripping the RFID tags out of the old roll, which is not super fun. It would be great if we could you reprogram the old roll to match the new roll and get on with printing.
Indeed this looks expensive and I'm not sure if it's certified by any safety agency (SNELL, DOT, ECE, etc.) but it sure does look nice. The built in lights that are linked to the bike seem like it would be a great addition to any helmet. I also like the audio features, though I wonder how useful they would really be. Would they block out too much information about what's going on around you?
I really liked Google Circles, a feature of Google+ social media. It allowed you to target content to specific groups of users. You could have a "family" circle or a "work" circle and not have to worry about cross posting something accidentally. It was a small thing but it made it really easy to manage your posts.
Yes, this was the ideal system for a social network imho, but it should've been integrated into an already existing network, G+ was in an odd spot between Twitter and Facebook.
Years later they briefly added Circles to Twitter and I thought that was great, not as useful as G+ Circles (since you could only have a single "private" circle to share to) but I very much used it and my mutuals as well... just to have Musk remove the only useful feature they had in years.
I think we are definitely losing our blue collar skills. This video[0] about building a grill scrubber in America really highlighted the problem for me.
We're in the same boat; HIPAA compliant Enterprise license. Slack came to us with a 2 day notice; pay more now or pay a lot more later. We asked if we could reduce the number of users and they said no, if you change anything then you have to take the new pricing for double the current price.
The whole thing was super sleazy. We told them that we were moving to MS Teams (arrrgghhh!) and they said "Bye!".
reply