[Linux-aus] FOSS social media

[Kathy Reid]

That's correct.

If an account replied to a post by the LinuxAustralia at fosstodon.org 
account, from a different instance, and the LA account was *not 
following the account that was replying* - for argument's sake, 
example at othermastodon.org - then yes, the LinuxAustralia at fosstodon.org 
account would _not_ see the reply.

However, we post critical information through multiple channels - such 
as via this email list that we're corresponding on right now - so I 
don't see it as a major issue. If someone wishes to engage with Linux 
Australia there are other channels, like the website contact form, 
emailing council at linux.org.au etc.

There are two actions hinted at here - and while I don't want to speak 
for Linux Australia, I do have a fairly good idea of how much time it 
takes to host a Mastodon instance, because I have hosted one for over 
two years. Both of them are time and resource intensive, and I would 
advise against them.

1. Move the Linux Australia Mastodon account to an instance that is not 
invite only (not sure of others, fosstodon.org is generally the go-to 
one for FOSS accounts). This requires not only moving the Mastodon 
account [0], but then updating all the things that point to that account 
on the website. That's a good couple hours' work right there. Doable, 
but a pain.

2. Linux Australia hosts our own Mastodon and gives LA members access to 
it. AFAIK there is no bridge from our Membership DB running on the 
website to Mastodon at all - this would require dev work on top of 
setting up the Mastodon instance. Back of the napkin estimate, a few 
days to a few weeks rather than a few hours.

If people really really want to engage with Linux Australia's Mastodon 
and really really really want their replies to be seen, I can offer to 
"follow" your account from the LinuxAustralia at fosstodon.org as a 
workaround. Would that address the issue?

Kathy Reid


[0] https://docs.joinmastodon.org/user/moving/


On 31/1/25 21:02, Marcus Herstik via linux-aus wrote:
> but there’s no guarantee that we will be heard / seen as it relies on 
> processors, timelines etc.