• 2 Posts
  • 26 Comments
Joined 1 month ago
cake
Cake day: June 2nd, 2026

help-circle





  • 45o3b@lemmy.mltoPrivacy@lemmy.mlWhat should I change?
    link
    fedilink
    arrow-up
    19
    arrow-down
    1
    ·
    11 days ago

    My answer to this is to use a custom domain with an email aliasing service.

    I’ve gone through about half of the 400 accounts in my password manager and moved them over. I’ll migrate the rest over the next week or so.

    So, I’m switching from Gmail to Proton for now, but if Proton starts to get worse or Tuta catches up on functionality or there’s a better provider that emerges or I decide to try to self-host, it’s one easy change at the alias provider to redirect all of my mail to a new email provider.


  • I like your logic here. Torrent index -> alternative platforms -> YT proper.

    Assuming the torrent index becomes decentralized, there are really two categories where it makes sense to build this in:

    1. The YouTube frontends, as you mention

    2. The self-hosted downloaders that already exist, like Tube Archivist

    I think the second category is where you get all the seeding traction. Sure, it would be great if the Android frontends also participate, but there are thousands of NAS devices that are already downloading YouTube videos for a single user. If there was an addon that allowed all of these users to share content automatically, I think there would be a lot of buy in / seeding.



  • No. It’s for IPTV channels that already exist. It lets you organize them and then make them available in Plex or Jellyfin.

    If you’re looking to make your own channel from content you already downloaded, that’s what ErsatzTV and dizqueTV do.

    If you’re looking to stream torrents without downloading them first, I’m pretty sure that can be done with Streamio and plugins, but I haven’t tried it.



  • 45o3b@lemmy.mlOPtoPrivacy@lemmy.mlThe Privacy Wiki
    link
    fedilink
    arrow-up
    1
    ·
    21 days ago

    It will be, once there’s code to share. I made this a couple hours ago, and as the name implies, I intended to turn it into an interactive wiki that could be community maintained.

    I don’t know how else to explain to you that it’s a static site. The “source”, as it currently exists, is being served to you as soon as you browse to the website.

    How does this not relate to your question? Literally click “view source” in your browser or use the command that I already gave you. Feel free to download all of it. You have full access, right this moment.

    I was just collecting resources for myself and thought it would be helpful to share for others and maybe turn it into a wiki that everyone could use.







  • Thanks. Here’s a comparison, for anyone else who might be interested:

    Feature matrix

    AppVerifier (soupslurpr) Verified Apps (Privacy Guides) AppVerifier BG (RoundSalmon4)
    Relationship Original / upstream Fork (stripped) Fork (extended)
    Internal database ✅ (PG crowdsourced) ✅ (original + PG)
    Peer-to-peer / clipboard sharing ❌ (removed)
    Personal user database
    DB import/export (JSON/text/YAML)
    Combined internal + user DB view
    Auto-submit mismatches to issue tracker
    GrapheneOS community hashes ✅ (opt-in)
    .apks split-APK support
    Debug-cert flagging
    Rich app list (sort/search/filter) basic basic
    SLSA build attestation partial (DB only)
    License ISC MIT ISC
    Distribution Accrescent, GitHub GitHub, Obtainium, F-Droid GitHub, Obtainium, F-Droid
    Latest release 13 — Apr 2025 26.6.7 — Jun 2026 v0.3.0 — Jun 2026
    Stars ~977 ~8 ~7

    Repos: AppVerifier · Verified Apps · AppVerifier BG. From each README as of June 2026; stars/releases change over time.