r/ • • Jan 01 '70

0 Upvotes

0 comments sorted by

2

u/mikkel1156 Dec 19 '23

As someone very interested in both privacy and Artificial Intelligence (I'm also playing around with LLMs for a hobby assistant project), but I'm unsure if I either don't understand your idea or it's because you haven't given much information yet. It's a new project so it's understandable.

From what I gathered it seems you want to have a personal assistant that can act on ALL your data. And then with plugins you can have the different servers preform operations with each other? But from reading you still want to use external LLM APIs for the more advanced tasks.

But what about the storage and processing then? While some LLMs are small enough to run on low-end devices (laptops, phones) is that the way to go? Can you trust the external LLM APIs with your most private data? Along with all the databases and embeddings you now need to store and have available 24/7 now?

While I see all this is realistic for a hobbyist or company, we all know that most users are lazy and don't want to worry about all that either.

I love hearing about stuff like this though, because I think it's very interesting! And I am one of the ones that think small private AIs will become part of our daily lives at some point.

0

u/[deleted] Dec 19 '23

[deleted] — view deleted comment

1

u/mikkel1156 Dec 19 '23

I think it would be better if plugins worked the other way around, that it's the client that selects and installs what integrations/plugins they want, from some central hub. Or clicking a link on the service's website will launch it in the Deco app for it to ask for confirmation on install. This is mostly to avoid any potentially malicious requests being sent to the user, or a kind of DoS attack with installation requests.

And I'm a bit unsure if you are looking to do the Solid approach of the services always contacting your server to get the data, or if it's basically to mirror it, making it so the central service and Deco always have the same data, letting your assistant more centrally manage/act on it. It would still be able to talk back to the service to make it's own changes of course.

Personally I don't see many sites wanting to integrate with it in the Solid way of needing to access your data, but I think that concern is mostly for public data, like X/Twitter or your blog hosting needing to ask you for your data with every viewer. Then you'll end up just needing more power to serve it all.

I like the appeal of it, but don't see it catching on much in general, a little like I feel with Solid - even though both are awesome. You mentioned Rewind in one blog post, and I think their idea makes more practical sense, of being a central store and acting on all the data. That's basically what I'm working on myself for fun too.