keybase / keybase/client

Binary deliverable is huge - modularize?

Open
#9,012 8 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

I just did apt-get upgrade and Keybase took 28 minutes to download, and I have a nice 40MB line here.

I imagine your apt repo host could use some bandwidth upgrade (have you considered dumping it on an S3 bucket?), but there's also the question of how it reaches nearly 73Mb in size. that's almost twice the size of the Firefox deb, and updates more often.

Any way of either downsizing it, or breaking it up to modules with dependencies so update deltas are more sensible in size?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by examining how the apt repository packages and distributes the binary, including the proposed S3 hosting and modular dependency options; done means reducing download size or defining a workable modular delivery approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.