From: Paul Sutton via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Solutions to help organisations mirror their antisocial media posts to mastodon?
Date: Thu, 23 Nov 2023 07:16:43 +0000 [thread overview]
Message-ID: <44c3d731-616a-47f1-8383-0cf74badd119@disroot.org> (raw)
In-Reply-To: <40dd1a27-eccb-7a28-0bc7-5fd3bd451e1f@noisytoot.org>
One of the nice things about posting to Mastodon is the fact people
interact and comment on posts. This is a two way process.
If you sell a product or offer a service and I ask about this on
Facebook then surely someone would reply, as a Mastodon user I would
expect the same or similar level of interaction with posts, and yes,l
this does require someone to be there to answer questions or comments on
posts Or in some cases if a user posted an offensive comment have this
removed
I think this is one of the reasons people on Mastodon prefer this over
mainstream social media, quality of social interaction rather than
quantity too
Paul
On 22/11/2023 01:22, Ron Nazarov via libreplanet-discuss wrote:
> On 20/11/2023 12:55, Yuchen Pei wrote:
>> Hello librenauts,
>>
>> Often when talking to people running organisations, they tend to cite
>> reach when asked why they only post on twitter, fecebook etc. However,
>> if they could automate mirroring their posts to mastodon they wouldn't
>> mind doing that. Some of these orgs even have a mastodon account, but
>> with barely any posts. Some of these people even despise twitter and
>> don't have a twitter account themselves.
>>
>> So I wonder if there is a tool that automates toot for tweet
>> replication?
>
> The FSF uses this script: https://vcs.fsf.org/?p=pdt.git;a=summary
>
> FSF account names are hard-coded but the README says that a patch that
> makes them configurable would be accepted.
>
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2023-11-27 13:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 12:55 Solutions to help organisations mirror their antisocial media posts to mastodon? Yuchen Pei
2023-11-22 1:22 ` Ron Nazarov via libreplanet-discuss
2023-11-22 1:30 ` Yuchen Pei
2023-11-22 1:44 ` Ron Nazarov via libreplanet-discuss
2023-11-23 7:16 ` Paul Sutton via libreplanet-discuss [this message]
2023-11-22 1:44 ` Alexandre Oliva
2023-11-22 2:07 ` Yuchen Pei
2023-12-05 1:10 ` Alexandre Oliva
2023-12-25 1:06 ` Yuchen Pei
2023-12-25 8:15 ` Paul Sutton via libreplanet-discuss
2023-12-26 21:54 ` Yuchen Pei
2023-12-26 23:16 ` Abe Indoria
2023-12-27 8:22 ` Paul Sutton via libreplanet-discuss
2023-12-26 23:47 ` Anti-social media: book Akira Urushibata
2023-12-26 18:23 ` Solutions to help organisations mirror their antisocial media posts to mastodon? Alexandre Oliva
2023-11-22 2:35 ` Yuchen Pei
2023-11-22 2:43 ` Kurtis Hanna
2023-11-23 11:36 ` Yuchen Pei
2023-11-27 18:04 ` Fischers Fritz
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=44c3d731-616a-47f1-8383-0cf74badd119@disroot.org \
--to=libreplanet-discuss@libreplanet.org \
--cc=paulsutton@disroot.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
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).