Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mastodon account #294

Closed
ploum opened this issue Apr 25, 2020 · 16 comments
Closed

Mastodon account #294

ploum opened this issue Apr 25, 2020 · 16 comments
Assignees
Labels
low-hanging-fruit "Easy picks" suitable for new contributors to tackle

Comments

@ploum
Copy link
Contributor

ploum commented Apr 25, 2020

I've seen the shiny new Twitter account. I think GTG should also have a Mastodon account.
I've spotted two FLOSS specific instances :
https://floss.social/about (where GNOME masto account is) and https://fosstodon.org.

It can also be synced thanks to https://crossposter.masto.donte.com.br/

@ploum ploum added the low-hanging-fruit "Easy picks" suitable for new contributors to tackle label Apr 25, 2020
@ploum ploum added this to the 0.4 "Work of love" milestone Apr 25, 2020
@nekohayo
Copy link
Member

Thank you for doing the research and proposal with the specific suggestions on where to have it. That solves one of my issues with Mastodon, which is "which $%%&ing instance am I supposed to pick?"

The other issues I have is needing to log on yet-another website, but that's OK. The biggest apprehension I had is I heard it (at least the web UI, I guess) doesn't have such a thing as scheduled postings (which Twitter's Tweetdeck has), and I don't know if it has such a thing as team permissions. Do you know if those exist in the main implementation?

@ploum
Copy link
Contributor Author

ploum commented Apr 27, 2020

Not that I'm aware of.
But, in the meantime, you could simply use the bridge to crosspost with twitter. Remove a lot of burden.

@ploum
Copy link
Contributor Author

ploum commented Apr 27, 2020

asked Mastodon : https://mamot.fr/@ploum/104072741918695113

@ploum
Copy link
Contributor Author

ploum commented Apr 27, 2020

For the record, a lot of GNOME developers are also on Mastodon. You should quickly feel at home ;-)

@ploum
Copy link
Contributor Author

ploum commented Apr 27, 2020

For scheduling: https://fedilab.app/

@nekohayo
Copy link
Member

I have now created https://fosstodon.org/@GettingThingsGNOME ; as it does not handle teams, I guess I will be the single point of failure for this...

@ploum
Copy link
Contributor Author

ploum commented Apr 28, 2020 via email

@nekohayo
Copy link
Member

nekohayo commented Apr 29, 2020

Why not "gtg" ?

Dunno, thought it was better to be explicit and to avoid potential clashes/confusion with whoever else might use that sort of nickname

I just learned that fosstodon is blocked by the bridge so floss.social might be a better choice now that it's easy to change (no followers to migrate).

Oh f*** me, how do I do that then? I have no idea.

For what it's worth, so far I'm finding the (decentralization) experience a bit painful, particularly compared to Twitter's Tweetdeck:

  • Not being able to configure the columns / add more columns in the "advanced" official web UI
  • No search columns to be able to monitor various topics
  • No visible toot scheduling feature (I saw Scheduled Toots mastodon/mastodon#340 where it is supposedly implemented but couldn't find anything in the official "advanced" UI for this)
  • No teams and no multi-account support (and multi-account support in a single web UI, now that I think of it, seems to be where the decentralized/federation concept will fall flat on its face)

...all papercuts that make me feel terribly improductive/handicapped in it. I'd like to see these features as part of the default/official web interface offering, I'm not going to go chasing down a gazillion clients to install (I particularly don't want to use mobile apps) that may have XYZ feature or bugs and may or may not be maintained in a few years... I guess I'm just old :)

@ploum
Copy link
Contributor Author

ploum commented Apr 29, 2020 via email

@nekohayo
Copy link
Member

So, regarding renaming the account username: I can't find a way to do that in the web UI/account settings...

@ploum
Copy link
Contributor Author

ploum commented Apr 30, 2020 via email

@nekohayo
Copy link
Member

nekohayo commented Apr 30, 2020

If I understand correctly then, I have to create a whole new account as @gtg@floss.social (and not fosstodon) and hope that instance doesn't get blocked/delisted/deprecated in the future, and then set a redirect, and ideally also tell people to migrate their subscription to the new account (because I'm not going to keep the old one around, no sir)...? This feels like the 90's. I have to admit I am rapidly losing patience for this kind of hoop jumping particularly if it relies on me being the "single point of failure" for that account. I don't like a piece of infrastructure being tied to me. I am pondering whether it is truly worth it.

@ploum
Copy link
Contributor Author

ploum commented Apr 30, 2020 via email

@nekohayo
Copy link
Member

nekohayo commented May 1, 2020

Hmm, where did you read that fosstodon was blocked from the federation, vs floss.social? I can't seem to find something about this. But then I can't seem to find a sensible, understandable summary list of the best instances to be on without going insane, either.

I'm going through the extra mile to be researching topics such as:

And it is not fun.
So far the time spent researching how to sustainably deal with the complexity, papercuts and caveats is just making me unhappy and unproductive, and I'd very much rather be focusing on other aspects of GTG (and my life).

I see four ways forward (a.k.a. pointing out the mammoth in the room):

  • A: Keep using the existing username and instance, if it's not a dead end? a.k.a. "the path of least resistance"
  • B: Create a new "gtg" account on floss.social and delete the old account (if at all possible), and maybe screw "doing things properly". If I can get some assurance that this is the be-all-end-all "correct" instance to be on. I don't want to have to change instances again.
  • C (also compatible with A and B): I hand over the account to someone else who is trustworthy, cares enough and has the patience for this kind of stuff... assuming I can easily change the email address associated with the account and there aren't more such surprises. But then this doesn't solve "bus_factor==1". It could go rogue just like the old website.
  • D (if "none of the above" are good enough): Give up on this experiment and delete the account entirely (if even possible) instead of advertising a half-hearted attempt like "scenario A" would be, and just focus on Twitter (and probably no other social networks) because it doesn't require a Ph.D from a German university to manage.

I hold no grudge towards Mastodon or anything like that, it's just that it is putting me before a choice where the costs—in terms of life complexity—are making it an increasingly hard sell for me personally every time I stumble on "Oh it doesn't do that?" and "Oh so doing this is not the 'correct' way?"…

@ploum
Copy link
Contributor Author

ploum commented May 1, 2020

I would say A. I'm not worried too much about using Fosstodon (official Debian account migrated away but some other projects still use it). I just find a bit sad to not have gtg (which is the de-facto name for the project, even the debian package has it) but, it's pure bicycle shedding so just forget about it and use https://moa.party for the bridge

@nekohayo
Copy link
Member

nekohayo commented Jun 3, 2020

I guess I'll consider this fixed / "good-enough", since we never know if, due to https://discourse.gnome.org/t/official-proposal-how-we-define-gnome-software/3371/15, we might (or might not) be forced to change the whole project name someday anyway (which is a whole other bikeshed to paint, and I don't have spontaneous ideas of alternative names nor do we have time for this branding exercise when we're simply trying to revive the project first and foremost anyway)

@nekohayo nekohayo closed this as completed Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-hanging-fruit "Easy picks" suitable for new contributors to tackle
Projects
None yet
Development

No branches or pull requests

2 participants