Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: [email protected]
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
No you shouldn't. Google has enough data already. If it is not self hosted it can't be trusted.
The idea that you should fly with exclusively self-hosted approaches is equally absurd to the idea that you should just blindly trust everyone.
Plus, if they have, as you say, "enough" data already, then surely giving them more doesn't actually hurt you in any way, shape or form?
yeah, self hosted may be a bit too much for everyone, but they should at least make its training database open as ai is biased on whatever data it is trained on
eg. like how some smart taps won't work for black people as the company just didn't trained the sensors to work with dark skin
imo, nextcloud took the best approach here, allowing users to utilize chatgpt 4 if needed, while still making a totally in-house FLOSS option available
why not?
what is so absurd about code running in an users own device?
Because it's just unnecessary. Due to their nature, you want a few services reachable from anywhere, anyways. There's no reason for the average consumer to acquire hardware for this purpose. Just rent the service or the hardware elsewhere, which also reduces upfront cost which is ideal in situations where you cannot know whether you'll stick with the service.
Again, it's either extreme that's absurd. You don't need your own video streaming platform for example. In rare cases, sure. For the vast majority of people, Netflix is a much service however.
hard disagree on that one, the opposite is true. we end up with companies centralizing it on huge datacenters and not even being able to profit from it (services like youtube are unprofitable). best solution would be a federated service. I digress though because video platforms are a completely different beast.
something as personal like ai assistants should utilize the processing power i already have available, wasteful not to.
also its a BAD idea to hand out data for something so personal to google yet again. lets not keep repeating that mistake if we can avoid it.
I would love to self-host something like that. But I do not have a good enough GPU to do something like that
Newer Pixels are having hardware chips dedicated to AI in them, which could be able to run these locally. Apple is planning on doing local LLMs too. There's been a lot of development on "small LLMs", which have a ton of benefits, like being able to study LLMs easier, run them on lower specs, and saving power on LLM usage.
Smaller LLMs have huge performance tradeoffs, most notably in their abilities to obey prompts. Bard has billions of parameters, so mobile chips wouldn't be able to run it.
That's right now, small LLMs have been the focus of development just very recently. And judging how fast LLMs have been improving, I can see that changing very soon.
Ridiculous take.
There's a vast difference between using a cloud service that definitely spies on you, and a self-hosted solution that you can ensure doesn't.
The ridiculous take is the joke:
In this case it's less about "spying" and more about data being used for training.
Being self-hosted in no way, shape, or form ensures that it doesn't spy on you. You're still putting trust in a third-party to keep their promises. The average user lacks the know-how to audit code. Hell, the average user wouldn't be able to figure out self-hosting in the first place.
You don't have to audit code to ensure it doesn't call home.
Okay, what can the average user do to ensure this, then?
We're talking about a service that intrinsically requires an internet connection, though.
A self-hosted service requires local network, not internet
You don't want the service to create arbitrary outbound connections, but you want your device to be able to communicate with the service.
It's been a while since I've done network stuff, but it sounds like a pretty simple textbook problem.
You can block a service from establishing outbound connections while allowing it to respond to inbound connections. It's pretty common to do this because server software generally has no business calling out unprompted.
It's actually quite easy to see if an app is phoning home. Also easy to prevent.
Did you write the driver for the keyboard you wrote that on? Silly and completely unrealistic take. The world relies on trust to operate. It's not black and white.