From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: RE: Stormux is born.
Date: Fri, 13 Mar 2020 13:44:35 -0400 [thread overview]
Message-ID: <alpine.NEB.2.21.2003131343530.23185@panix1.panix.com> (raw)
In-Reply-To: <Pine.LNX.4.64.2003131317210.19101@server2.shellworld.net>
email lists appeal to a smaller audience than any of the other social
platforms which is why social platforms are used these days.
On Fri, 13 Mar 2020, Linux for blind general discussion wrote:
> Date: Fri, 13 Mar 2020 13:19:29
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: RE: Stormux is born.
>
> why not create the discussion list somewhere more open like groups.io?
> After all, I imagine you desire reaching individuals who have been
> dissatisfied with other Linux experiences, so they can discover that your
> product works for them?
>
>
>
> On Fri, 13 Mar 2020, Linux for blind general discussion wrote:
>
> > Hi,
> > The stormux chat is not opening
> >
> > -----Original Message-----
> > From: blinux-list-bounces@redhat.com <blinux-list-bounces@redhat.com> On
> > Behalf Of Linux for blind general discussion
> > Sent: Friday, March 13, 2020 2:17 PM
> > To: blinux-list@redhat.com
> > Subject: Stormux is born.
> >
> > I'm very happy to see this project continued, and I have already started
> > working on the social media aspect and marketing and promotion. Stormux now
> > has a Telegram channel that will announce news and release notes,
> > https://t.me/stormux as well as a linked general discussion group at
> > https://t.me/stormux_discussion Stormux will also soon be available on most
> > of the usual social media channels including Facebook and Twitter. I'm happy
> > to work with this project, and will do my best to keep everyone interested
> > updated regarding its status and features.
> > ~Kyle
> >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.21.2003131343530.23185@panix1.panix.com \
--to=blinux-list@redhat.com \
/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).