231–240 of 241 posts
The way trademarks work is that if you don't actively defend them you weaken your rights. So Anthropic needs to defend their ownership of "Claude". I'm guessing they reached out to Peter Steinberger and asked nicely that he rename Clawdbot.
Earlier quoted context omitted.
If you want iMessage you still need an always-on Mac, whether that's the main moltbot gateway, or the MacOS app running in 'node mode' to allow a moltbot gateway to use it to send/receive iMessages.
I noticed when I was reading Federico Viticci's post about it that he was using telegram, which has much better support for "markdown"-y rendering, which looks a lot nicer than iMessage. And then I thought to myself, why would iMessage actually matter? The only other use-case would be interacting with texts, but almost anyone can tell when someone is using an LLM to text - I feel like our texting styles are so person…
Earlier quoted context omitted.
This is a dilution not abandonment issue. Courts will look at the level of systematic tolerance. If you have a history of vigorous enforcement, it will be harder to argue in the future that a borderline dilution should be allowed. If you allow borderline dilution, the court is going to consider what you have let other people get away with in the past. It’s a bit of a catch 22
I would still be interested in a real case where a trademark owner ignored a borderline case and this later resulted in an adverse ruling when a more concrete interest was at stake.
Earlier quoted context omitted.
The silly part is buying a $50 raspberry pi, then storage and memory and so on, when a $200 used M1 Mac mini is plug-and-play.
The silly part is buying a $200 used M1 Mac mini, when a $5 Arduino clone can be used to blink an LED. Oh wait—that’s the silly part
"You turn this LED on or off"
Earlier quoted context omitted.
If you have to mitigate the security issues but still use the product, how and what would you do about it ? to prevent prompt injection attacks and trifecta attacks. How to prevent gmail and iMessage leaks, if we cut off outbound access then it becomes useless , also it will spin up a reverse proxy like ngrok and send the data as long as it has inbound access. Once it has internet access its hard to prevent untrusted…
The only solution I can think of at the moment is a human in the loop, authorising every sensitive action. Of course it has the classic tradeoff between convenience and security, but it would work. For it to work properly, the human needs to take a minute or so reviewing the content associated with request before authorising the action. For most actions that don't have much content, this could work well as a simple p…
While researching ways to reduce that complexity, I came across PAIO. What stood out to me wasn’t just the convenience, but the architecture choices. The integration was basically one-click compared to the multi-step setup I had before, but the bigger win was BYOK and the privacy-first approach.
With self-hosted assistants, the tooling is powerful but the security model is often an afterthought, and it’s easy to accidentally expose something (as people in this thread pointed out with Shodan results). A managed layer that still keeps keys and data under your control feels like a reasonable middle ground between full DIY and full SaaS.
I still like self-hosting for learning and control, but for day-to-day reliability and security, having a platform that bakes in isolation and privacy primitives saves a lot of operational burden.
Earlier quoted context omitted.
The only solution I can think of at the moment is a human in the loop, authorising every sensitive action. Of course it has the classic tradeoff between convenience and security, but it would work. For it to work properly, the human needs to take a minute or so reviewing the content associated with request before authorising the action. For most actions that don't have much content, this could work well as a simple p…
You might be okaying actions hundreds or thousands of times before you encounter an injection attack, at which point you probably aren't reading things before you approve.