Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 679
    • Issues 679
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1615

Closed
Open
Opened Jul 31, 2019 by Pratiwir@Pratiwir
  • Report abuse
  • New issue
Report abuse New issue

Upgrade process like apt and use torrents

I would like to suggest doing a more modular upgrade process the same way that is used in termux where apt is used to fetch code. Thus Briar could be upgraded piecewise using a cut down version of apt.

I also propose using torrents software within Briar, as an additional way to fetch and verify any upgrade files, so that play store could become superfluous once the initial install is made. The torrents component could be activated as needed and used to voluntarily help distribute system files to other users.

I am suggesting this because other apps have this problem of constantly having to uograde. To do this anonymously needs f-droid or yalp store over tor, but the downloads are slow and have a high failure rate, needing to keep restart the download when secure communications apps are being fetched.

It is imho key to have anonymous downloads and easy software distribution not subject to packet injection and blocking.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1615