From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: Re: Thoughts on search-based imap mailboxes Date: Sat, 3 Oct 2020 19:40:01 +0000 Message-ID: <20201003194001.GA8174@dcvr> (raw) In-Reply-To: <email@example.com> Konstantin Ryabitsev <firstname.lastname@example.org> wrote: > On Fri, Oct 02, 2020 at 08:08:30PM +0000, Eric Wong wrote: > > A client-side tool is likely required anyways, I'm thinking > > having saved search functionality in a local tool writing to > > Maildir/mbox might be the best way forward as w.r.t. scalability > > and offline access (and reading + saving flags from the > > Maildir/mbox). > > > > External/detached index I'm working on for global search will > > also be appropriate for client-side tooling, I think, as it's > > being designed with non-public-inbox data sources in mind, too. > > Instead of a "client-side" can it just be an intermediary tool that can > run either on the client, or on any other piece of infrastructure? The > main reason I'm interested in that is because several people I know use > very thin clients for their work (chromebooks) and I would like to offer > them this service as a perk of kernel.org instead of forcing them to set > it up and maintain on their own. What are the limitations of chromebooks? Small eMMC storage? Can they run curl, perl and git? I could probably work with that; maybe just curl + POSIX sh. I get Xapian might be stretching it, but they probably have SQLite already (though not the Perl bindings) CPU and RAM on Chromebooks seem to be as good or more powerful than the ancient Thinkpads I use.
prev parent reply other threads:[~2020-10-03 19:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-02 14:34 Konstantin Ryabitsev 2020-10-02 20:08 ` Eric Wong 2020-10-03 14:50 ` Konstantin Ryabitsev 2020-10-03 19:40 ` Eric Wong [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201003194001.GA8174@dcvr \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
unofficial mirror of email@example.com This inbox may be cloned and mirrored by anyone: git clone --mirror https://yhetil.org/meta # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 meta meta/ https://yhetil.org/meta \ firstname.lastname@example.org public-inbox-index meta Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.mail.public-inbox.meta nntp://news.public-inbox.org/inbox.mail.public-inbox.meta nntp://news.gmane.io/gmane.mail.public-inbox.general AGPL code for this site: git clone https://public-inbox.org/public-inbox.git