Privacy

709 readers
185 users here now

Protect your privacy in the digital world

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

~PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!~

  1. Be nice, civil and no bigotry/prejudice.
  2. No tankies/alt-right fascists. The former can be tolerated but the latter are banned.
  3. Stay on topic.
  4. Don't promote proprietary software.
  5. No crypto, blockchain, etc.
  6. No Xitter links. (only allowed when can't fact check any other way, use xcancel)
  7. If you post news exclusive to a country please name it. ~(This isn't a bannable rule, just a recommendation!)~
  8. If in doubt, read rule 1

Related communities:

founded 3 months ago
MODERATORS
26
 
 

cross-posted from: https://lemmy.dbzer0.com/post/36841328

Hello, everyone! I wanted to share my experience of successfully running LLaMA on an Android device. The model that performed the best for me was llama3.2:1b on a mid-range phone with around 8 GB of RAM. I was also able to get it up and running on a lower-end phone with 4 GB RAM. However, I also tested several other models that worked quite well, including qwen2.5:0.5b , qwen2.5:1.5b , qwen2.5:3b , smallthinker , tinyllama , deepseek-r1:1.5b , and gemma2:2b. I hope this helps anyone looking to experiment with these models on mobile devices!


Step 1: Install Termux

  1. Download and install Termux from the Google Play Store or F-Droid

Step 2: Set Up proot-distro and Install Debian

  1. Open Termux and update the package list:

    pkg update && pkg upgrade
    
  2. Install proot-distro

    pkg install proot-distro
    
  3. Install Debian using proot-distro:

    proot-distro install debian
    
  4. Log in to the Debian environment:

    proot-distro login debian
    

    You will need to log-in every time you want to run Ollama. You will need to repeat this step and all the steps below every time you want to run a model (excluding step 3 and the first half of step 4).


Step 3: Install Dependencies

  1. Update the package list in Debian:

    apt update && apt upgrade
    
  2. Install curl:

    apt install curl
    

Step 4: Install Ollama

  1. Run the following command to download and install Ollama:

    curl -fsSL https://ollama.com/install.sh | sh
    
  2. Start the Ollama server:

    ollama serve &
    

    After you run this command, do ctrl + c and the server will continue to run in the background.


Step 5: Download and run the Llama3.2:1B Model

  1. Use the following command to download the Llama3.2:1B model:
    ollama run llama3.2:1b
    
    This step fetches and runs the lightweight 1-billion-parameter version of the Llama 3.2 model .

Running LLaMA and other similar models on Android devices is definitely achievable, even with mid-range hardware. The performance varies depending on the model size and your device's specifications, but with some experimentation, you can find a setup that works well for your needs. I’ll make sure to keep this post updated if there are any new developments or additional tips that could help improve the experience. If you have any questions or suggestions, feel free to share them below!

– llama

27
 
 

As a follow-up to a recent post about mail privacy, I thought it would be interesting to see what mail setup you have.

Your recommendations may also help people newer to this trend to make a switch.

Interesting information:
  • Mail provider
  • Multiple emails? Aliases?
  • Password manager?
  • All eggs in one basket or decentralized?
  • Self host?

If anyone has a good recommendation outside of the typical ones, we'll work on adding it to the upcoming wiki.

28
29
30
 
 

As for this community to comply with the latest instance rule, Xitter (X/Twitter) links won't be allowed. (This has been effective since 26-27th depending on your timezone.)

Link to the original post here

To summarize:

  • No X/Twitter links, shortened X/Twitter links or similar allowed. Screenshots from X/Twitter are still allowed but better avoided if possible.

  • Exception: in rare cases, https://xcancel.com/ versions of a link may be allowed, but this will be exclusive to some hard to fact check sources that DO require a link to an X/Twitter post.

No other frontend links or loopholes will be allowed.

Thank you for your time and understanding. Stay private!

31
32
33
 
 

I'm looking for some recommendations for digital debit/credit cards.

It feels like every other day there's 'the largest data breach in history' and at this point, I really don't trust any entity to safely and securely store PII.

That said, I like buying things on the internet, I'm not into crypto and would rather not include my real card information during checkout.

Any recs would be appreciated, thanks yall!

34
35
36
37
 
 

Hi my fellow Lemmings and friends!

I need to get a second number, and I would prefer not to use Google Voice. I have an Android phone and it needs to be a USA (+1) number.

What are the reputable, privacy friendly apps for this? It would be amazing if it was free but I will not hold my breath on that.

😸

38
39
 
 

cross-posted from: https://newsie.social/users/TheConversationUS/statuses/113909551624831355

Philadelphia's $800K police drone program highlights the challenge of balancing public safety and #privacy. Criminologists explain how lessons from stop-and-frisk can guide responsible drone use in law enforcement. https://buff.ly/4anJYJ7

40
 
 

cross-posted from: https://lemmy.zip/post/30920964

With Signal on Desktop and iPad, you can link your primary Android or iOS account with another device, letting you check and respond to messages in both places or conduct video meetings and calls from the comfort of a bigger screen.

41
 
 

So, I was reading the privacy notice and the terms of use and I did read some sketchy stuff about it (data used in advertising, getting keystroke). How bad is it? Is it like chatgpt or worse? Anything I can do about it?

42
 
 
43
44
45
46
47
 
 

From an author:

I wanted to share crypt.fyi - a free, open-source tool I built for securely sharing sensitive data/files. It uses client-side encryption and zero-knowledge architecture.

Key features:

- Zero-knowledge architecture
- End-to-end encryption using AES-256-GCM (actively investigating post-quantum encryption options)
- Self-hostable
- Suite of configurations (password, burn after read, max read count, ip/cidr-allow list, webhooks)
- Strict rate-limiting
- Strict CSP to mitigate supply chain attacks
- Web, cli, and chrome-extension clients
- Fully open source (Github)

The problems I aimed to solve: Many people share sensitive info (passwords, keys, etc.) through email, Slack, or SMS - which often leaves plaintext copies in multiple places. Existing solutions either require accounts, aren't open source, or have security/privacy/ui/ux/feature/config gaps/limitations.

crypt.fyi is built with privacy-first principles:

- No logging of sensitive data
- No analytics or tracking
- Separation of web and api servers
- All encryption/decryption happens client-side using shared cross-platform cryptography primitives from noble cryptography
- TLS encryption for all traffic
- Encrypted data is automatically destroyed after being read with strong guarantees around once-only reads

The entire codebase is open source and available for review. I'd love to get feedback from the privacy community on how to make it even better!

48
 
 

From driving licence to local air quality, app offers myriad of features and has been rolled out to little opposition

49
 
 

App and wallet would allow people to carry digital versions of key documents such as driving licence on their phones

50
view more: ‹ prev next ›