unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org, tomas@tuxteam.de
Subject: Re: Diversification [ branched from Re: conflicts in the gnu project now affect guile]
Date: Sat, 26 Oct 2019 15:02:57 +0200	[thread overview]
Message-ID: <e3358675-9525-86ea-4de9-af41e044f7a5@posteo.de> (raw)
In-Reply-To: <20191026112621.GC22804@tuxteam.de>

On 10/26/19 1:26 PM, tomas@tuxteam.de wrote:
> On Sat, Oct 26, 2019 at 11:03:12AM +0200, pelzflorian (Florian Pelz) wrote:
>> On Sat, Oct 26, 2019 at 10:14:22AM +0200, tomas@tuxteam.de wrote:
> [...]
>
>>> only become aware of that when you try to live at the rift.
>> Yes, this is something we should keep in mind.  IMHO the medium should
>> remain a mailing list and this should be clear.  Top posting is
>> useless and undesirable with both e-mail and forums though, I believe.
>>
>> Since I use mutt too, I think plain text compatibility is important.
> See? There lies the problem. I'm firmly in your "camp", and still I
> learnt to realise that the other "cultures" do have as difficult a
> time to adapt to "our" camp as the other way around.
>
> That's why I believe that we need serious thinking (beyond the "easy"
> technical things) and lots of tolerance.
>
> To me, Wikipedia is a wonderful inspirational example for a web site
> which succeds in bridging an astonishly broad swath of those "cultures"
> (and still doesn't cover all of them, it has a distinct academic and
> "liberal", in the broadest sense, "smell" to it).
>
>> As for the formatting, I think for plain text e-mail compatibility,
>> when there are stars around a word, it should *not* be highlighted as
>> italic.
> Uh -- isn't the star reserved for *strong*? ;-)
>
> Cheers
> -- tomás

Hi!

Well, I hope that such tolerance does not lead us to accept usage of
mini-uglyfied proprietary JavaScript or other bad things, just to please
people, who in the majority most likely …

(1) … would never consider switching away from _their_ medium of choice,
because most people use it, so it must be right
(2) … have never even thought about the consequences of their choice of
technology (examples here are the web engine monoculture threat and
human interaction via Whatsapp and FB messenger, Skype)

I just want to point that out. While I find it to be a good idea to be
open to alternatives, I do not find it acceptable to not stay true to
our principles as a community of free software developers.

I also often see a very heavy imbalance between the amount of thought
some people in the free software world have put into their choice of
technology and the amount of thought the mainstream user has put into
their choice (usually zero, besides an "Oh it works!" or "It does not
cost me money!"). So we should not give up our principles, in order to
win some people over, because then we are actually the ones "won over"
(or lost) to the proprietary non-free world. It would not be a
diversification, but a disintegration of our community.

That said, I am open to trying out any community communication
technology, that follows the principles of free software and is run in
an ethically acceptable way.

I am highly skeptical of discourse, because:

* https://www.discourse.org/ tries to load Google Analytics and
fontawesome, 2 tools to spy on users. They already do not seem to care
about privacy.
* It is very JavaScript heavy.
* In my experience slow and sluggish.
* WYSIWYG-Editor – These tend to not produce plain text well readable
documents. Just give me some simple editor, Markdown maybe, not mandatory.

That is, why I like the idea of having a good old (newly written in
Guile) forum software. I would like and welcome such a forum software,
because some of my best memories of community interaction happened in
such a good old forum with a great community. It is also a great
structured long term memory. Whether the "other cultures" would use it
is on a different sheet of paper.

One more thing we should very much look out for, when choosing some
technology or when making our own software is:

* Can we actually get all our content out of that software if needed?
Can we export it to some JSON or other useful format?

Otherwise we will lock ourselves in.

Best regards,

Zelphir




  reply	other threads:[~2019-10-26 13:02 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20  6:10 Diversification [ branched from Re: conflicts in the gnu project now affect guile] Todor Kondić
2019-10-20  6:14 ` John Cowan
2019-10-21  6:35   ` Arne Babenhauserheide
2019-10-21 13:45     ` Amirouche Boubekki
2019-10-23  6:16   ` Amirouche Boubekki
2019-10-23  6:27     ` Nala Ginrut
2019-10-23  6:48     ` pelzflorian (Florian Pelz)
2019-10-23 10:37       ` Chris Vine
2019-10-23 11:25         ` pelzflorian (Florian Pelz)
2019-10-23 12:33           ` pelzflorian (Florian Pelz)
2019-10-23 13:47             ` tomas
2019-10-23 14:10               ` pelzflorian (Florian Pelz)
2019-10-23 19:09                 ` Mikael Djurfeldt
2019-10-23 19:26                   ` pelzflorian (Florian Pelz)
2019-10-23 19:19             ` Zelphir Kaltstahl
2019-10-24  1:01               ` Nala Ginrut
2019-10-24  9:19                 ` pelzflorian (Florian Pelz)
2019-10-24  9:35                 ` mailmam, web bridge, forum, p2p (was: Diversification) Amirouche Boubekki
2019-10-24 12:30                   ` pelzflorian (Florian Pelz)
2019-10-24 14:15                     ` Nala Ginrut
2019-10-24 16:39                       ` Zelphir Kaltstahl
2019-10-24 23:42                         ` Nala Ginrut
2019-10-25  1:39                     ` mailmam, web bridge, forum, p2p Mike Gerwitz
2019-10-26  7:48                       ` tomas
2019-10-26 10:35                         ` Nala Ginrut
2019-10-26 11:34                           ` tomas
2019-10-27  4:50                         ` Mike Gerwitz
2019-10-27  5:32                           ` Mike Gerwitz
2019-10-27  8:50                             ` tomas
2019-10-27  8:36                           ` tomas
2019-10-27 14:26                           ` Keith Wright
2019-10-27 19:28                             ` Zelphir Kaltstahl
2019-10-25  6:08                     ` mailmam, web bridge, forum, p2p (was: Diversification) pelzflorian (Florian Pelz)
2019-10-25  6:23                       ` Nala Ginrut
2019-10-26  4:31                       ` mailmam, web bridge, forum, p2p Mike Gerwitz
2019-10-26  9:35                         ` pelzflorian (Florian Pelz)
2019-10-26 11:31                           ` tomas
2019-10-24 13:32                   ` mailmam, web bridge, forum, p2p (was: Diversification) tomas
2019-10-24 15:03                     ` Nala Ginrut
2019-10-24 15:12                       ` tomas
2019-10-24 16:35                         ` Zelphir Kaltstahl
2019-10-26  8:04                           ` tomas
2019-10-26  9:42                             ` pelzflorian (Florian Pelz)
2019-10-26 11:31                               ` tomas
2019-10-25 11:30                       ` Mikael Djurfeldt
2019-10-25 12:53                         ` Nala Ginrut
2020-09-05  6:15               ` Diversification [ branched from Re: conflicts in the gnu project now affect guile] Joshua Branson via General Guile related discussions
2020-09-05 11:50                 ` Web development Zelphir Kaltstahl
2020-09-05 13:09                   ` Ricardo Wurmus
2019-10-28 11:04             ` mailman web interface (was: Diversification) pelzflorian (Florian Pelz)
2020-07-08 12:32               ` pelzflorian (Florian Pelz)
2020-09-05  6:21                 ` mailman web interface Joshua Branson via General Guile related discussions
2020-09-05  7:53                   ` pelzflorian (Florian Pelz)
2020-09-05 13:32                     ` Joshua Branson
2019-10-23 13:43         ` Diversification [ branched from Re: conflicts in the gnu project now affect guile] tomas
2019-10-23 17:39           ` Chris Vine
2019-10-23 19:58             ` Mailman web interface [was: Re: Diversification] pelzflorian (Florian Pelz)
2019-10-23 20:02           ` Diversification [ branched from Re: conflicts in the gnu project now affect guile] pelzflorian (Florian Pelz)
2019-10-26  8:14             ` tomas
2019-10-26  9:03               ` pelzflorian (Florian Pelz)
2019-10-26 11:26                 ` tomas
2019-10-26 13:02                   ` Zelphir Kaltstahl [this message]
2019-10-26 15:23                     ` tomas
2019-10-26 16:47                     ` pelzflorian (Florian Pelz)
2019-10-26 17:09                       ` pelzflorian (Florian Pelz)
     [not found]                         ` <874kzslwq0.fsf@elephly.net>
2019-10-28 15:41                           ` pelzflorian (Florian Pelz)
2019-10-23 13:45       ` tomas
2019-10-20  8:07 ` pelzflorian (Florian Pelz)
2019-10-20  8:08   ` pelzflorian (Florian Pelz)
2019-10-22 18:47 ` Mark H Weaver
2019-10-22 19:23   ` Zelphir Kaltstahl
2019-10-22 20:51     ` Arne Babenhauserheide
2019-10-22 23:24     ` Chris Vine
2019-10-23  0:57       ` Zelphir Kaltstahl
2019-10-23  6:44         ` pelzflorian (Florian Pelz)

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3358675-9525-86ea-4de9-af41e044f7a5@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@gnu.org \
    --cc=tomas@tuxteam.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).