From: Vagrant Cascadian <vagrant@debian.org>
To: Bone Baboon <bone.baboon@disroot.org>, jbranso@dismail.de
Cc: help-guix@gnu.org
Subject: Re: Making a DIY smart or dumb phone
Date: Sat, 24 Jul 2021 08:27:33 -0700 [thread overview]
Message-ID: <871r7nwx3u.fsf@yucca> (raw)
In-Reply-To: <87y29vsvlx.fsf@disroot.org>
On 2021-07-24, Bone Baboon wrote:
> jbranso--- via writes:
>> and unfortunately it needs to support SMS and traditional calls, so there might be some binary blobs for the modem.
I've been using for SMS and voice calls:
https://jmp.chat
It runs on all free software and provides a pretty rich SMS experience
using an XMPP client, and you can use a SIP (or maybe even XMPP) client
for voice calls.
live well,
vagrant
next prev parent reply other threads:[~2021-07-24 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 15:47 Making a DIY smart or dumb phone jbranso--- via
2021-07-24 13:13 ` Bone Baboon
2021-07-24 15:27 ` Vagrant Cascadian [this message]
2021-07-24 17:01 ` Joshua Branson
2021-07-24 16:56 ` Joshua Branson
2021-07-24 17:45 ` Jonathan McHugh
2021-07-25 0:11 ` jbranso
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r7nwx3u.fsf@yucca \
--to=vagrant@debian.org \
--cc=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).