the architecture of Bluesky is supposed to be more open than X
Cons of going to Bluesky:
Yet another account to manage
Pros of leaving Twitter/X:
The platform and its moderation are more and more criticized and politically charged, and people and organization a moving to alternatives.
Cons of leaving Twitter
Twitter still has quit a lot of users, even considering the current wave of people leaving the platform
Our 428 followers won’t get notified this way
Please vote for the following options:
Agree to create a bluesky account
Agree to stop using Twitter
Voting for 1 and not for 2 means updating our release process to publish new releases on Bluesky in addition to Twitter and Mastodon, which is a bit more work.
Thanks!
PS:
Bluesky can produce a handle based on a domain name, so our Bluesky handle could be @xwiki.org
I kept out of scope other improvements such as improving the short and generic message we currently post on social medias
I’m still mixed about using bluesky and having another account, while we have mastodon. But I’m not against giving it a try if that’s not too much work.
I’m wondering if it wouldn’t be worth to just bridge our existing Fediverse account to Bluesky so we don’t have to maintain a separate account there. Apparently it is even possible to advise the bridge to use our domain as name. @mleduc Do you know if there is any advantage of having a separate account on Bluesky vs. the bridge?
I agree that it’s good to show up there, but it’s an annoying thing to do. So IMO we should really do that with tooling, and ideally a tool that automatically bridge https://www.xwiki.org/xwiki/bin/view/Blog/ to both Mastodon and Bluesky (one less step in the release plan and more content for Mastodon and Bluesky than what we currently post).
we have a general agreement to stop using Twitter/X
There is more discussion regarding Bluesky.
Regarding Twitter/X
Remove the Twitter step from the release plan
Announce our move to Bluesky and Mastodon
Remove the account.
I’m +1 for 1.
We did not do 2 when creating a Mastodon account, I’m not sure if we need to do it now.
Regarding 3, I’m fine with keeping the account, as it avoid identity theft and could be useful later (who knows)
Regarding Bluesky
I think the following plan can find an agreement
find a way to bind the bridge to our xwiki.org domain
If everything goes ok, this should be enough and what we publish on mastodon would also be published on Bluesky, avoiding adding another step in the release place.
Then, the automation proposed by @tmortagne, could only interact with Mastodon’s APIs.
Can we check how many people read our tweets? I don’t think it takes much time to do it and if we’re able to touch more people then why not do it? OTOH if it’s not used much or at all, then why not.
EDIT: We have 436 Followers and around 9-50 views for each RN announcement.
EDIT2: On older versions we have more views, for ex 433 for the 15.7 release.
Are you suggesting that we’ll actively monitor replies on Bluesky if we go with a dedicated account? And if we do the posting manually, there can also easily be a delay of several minutes as the committer needs to find the login details for Bluesky first, so I’m not sure that it will be faster (and I don’t see why it would matter). I’m +1 to go with a dedicated account if we have a volunteer who actively takes care of that account. Otherwise, I would prefer the bridge.
+1 to leaving twitter, for obvious reasons
+1 to start using bluesky alongside mastodon.
From what I’ve seen online, from tests done by people with much larger followings, bluesky seems to have a more active/engaged community. People seem to interact more with posts on that platform.
