LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Joseph Turner via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: "Paul D. Fernhout" <pdfernhout@kurtz-fernhout.com>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Are websites closing down en masse? (distributed free standards and tools)
Date: Sat, 16 Dec 2023 16:25:39 -0500	[thread overview]
Message-ID: <874jghu9ba.fsf@ushin.org> (raw)
In-Reply-To: <230d1eb8-af36-43b0-bac0-9abfc7cc529f@kurtz-fernhout.com>

Hi Paul!

"Paul D. Fernhout" <pdfernhout@kurtz-fernhout.com> writes:

> On your question "What kinds of responses have you received to your
> talk from the FSF or other groups/individuals?", I have not received
> any responses I can recall. Beyond other factors limiting
> communications, perhaps shaping standards is just not on most people's
> radar screens?

I think you may be right about that.

[...]

> A lot of "standards" in the past have been proprietary, where
> organizations that promoted standards sometimes charged a huge amount
> of money just to obtain copyrighted versions of the standards
> documents (perhaps with a license fee on top of that for actually
> using the standard). That situation seems to have been improving
> though as far as availability of standards documents.

I agree with you about the importance of open standards.

> But on the other hand, Software as a (proprietary) Service has made
> other things worse. As I discuss in this 2016 essay:
> https://pdfernhout.net/reasons-not-to-use-slack-for-free-software-development.html
> "I recently turned down a job interview with Automattic, that I had
> literally waited months for them to schedule, because they insisted I
> use Slack for the interview and have switched WordPress.org
> development over to using Slack. Automattic used to use IRC and Skype
> for such prospective employee chats and for WordPress.org developer
> chats. I had hoped to add a real-time component to WordPress via
> Node.js and Automattic's socket.io to help make WordPress into a
> premier platform for real-time communications, decision support, and
> sensemaking, and said that in my application. To me, using Slack to
> interview with Automattic felt like it would have been significantly
> inconsistent with my stated goals for my work there. Readily agreeing
> to use Slack at Automattic just for an interview would also indicate
> tacit approval of Automattic's move to use Slack for WordPress.org as
> if there are not significant consequences for the WordPress community
> (a community which I am part of as a WordPress plugin developer and as
> a WordPress.org Trac participant helping identify and fix a
> significant WordPress core bug). ..."
>
> Ironically, the places I worked instead of Automattic eventually
> started using Slack and I was forced to use it to keep my job
> (although I was not working on communications tools).

In your blog post, you suggest Matrix as an alternative.  Why not XMPP?

Thank you!

Joseph

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

      reply	other threads:[~2023-12-18 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  3:53 Are websites closing down en masse? Akira Urushibata
2023-12-04 19:00 ` Paul Sutton via libreplanet-discuss
2023-12-08  6:29 ` Joseph Turner via libreplanet-discuss
2023-12-13 14:11 ` Are websites closing down en masse? (distributed free standards and tools) Paul D. Fernhout
2023-12-13 15:46   ` Joseph Turner via libreplanet-discuss
2023-12-15  2:47     ` Paul D. Fernhout
2023-12-16 21:25       ` Joseph Turner via libreplanet-discuss [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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=874jghu9ba.fsf@ushin.org \
    --to=libreplanet-discuss@libreplanet.org \
    --cc=joseph@ushin.org \
    --cc=pdfernhout@kurtz-fernhout.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).